finds.dev

seanmonstar/warp

A super-easy, composable, web server framework for warp speeds.

View on GitHubHomepage ↗

★ 10,384RustMITupdated Jul 2026

// the take

warp is a Rust HTTP server framework built on hyper, where routes and request handling are expressed as composable Filters. It's aimed at Rust developers who want a functional, type-driven way to build web services rather than a traditional router/middleware/controller setup.

Building on hyper gives it HTTP/1 and HTTP/2 for free, plus solid async performance. The Filter composition model is genuinely elegant for expressing cross-cutting concerns (auth, logging, body parsing) without inheritance or macros taking over. Batteries included out of the box: static file serving, websockets, multipart, compression (gzip/deflate/brotli) — you don't need to bolt on half a dozen crates to get a real service running.

The Filter trait's type signatures get genuinely hard to read once you compose more than a few of them — error messages for mismatched filters are notoriously opaque, and it's a real onboarding cost compared to axum's extractor-based model. Development has slowed noticeably compared to axum, which has become the de facto choice in the Tokio ecosystem and gets more attention from the hyper/tokio maintainers themselves. Custom rejection handling (turning your own error types into HTTP responses) is clunky and not well documented, so people end up reinventing it per project. If you're starting fresh today, you're choosing a framework with a shrinking relative share of new crates and examples versus the alternative most of the ecosystem has converged on.

We read the README, the directory tree and a key source file in November 2026. Nobody pays to be listed. How we judge →

search the same ground:

// at a glance

Stars
10,384
Forks
746
Language
Rust
License
MIT
Last commit
28 Jul 2026

// nearby

If warp isn't quite it.

All repos →