// the find
cloudflare/quiche
🥧 Savoury implementation of the QUIC transport protocol and HTTP/3
Cloudflare's production QUIC and HTTP/3 implementation in Rust, used at Cloudflare's edge, in Android's DNS resolver, and optionally in curl. It's a low-level API — you own the socket, the event loop, and the timers; quiche just handles the protocol state machine.
Battle-tested at Cloudflare's edge scale, so the protocol correctness and performance aren't theoretical. The bring-your-own-I/O design means it fits into any async runtime or event loop without fighting the library. The C FFI layer is a first-class output (not an afterthought), making it usable from non-Rust codebases including curl. Fuzz corpus is substantial and ships with the repo, which is more than most protocol libraries bother with.
The bring-your-own-I/O model that makes it flexible also means getting a working server running requires writing a non-trivial amount of glue code — the example apps are explicitly marked not-for-production. Depends on BoringSSL via boring-sys, which requires cmake at build time and NASM on Windows; this regularly breaks in CI environments that don't expect it. No async-native Rust API — you're polling send/recv in a loop yourself, which feels out of place in a modern async Rust codebase. Windows build friction is real and underserved in the docs.