quiche is a Rust implementation of QUIC and HTTP/3 that gives applications a low-level API for handling packets, connection state, and network timing.
quiche is an implementation of the QUIC transport protocol and HTTP/3 aligned with IETF specifications. The repository is centered on a low-level networking library, and it also includes command-line examples in the quiche-apps crate for trying the client and server flows. The README makes clear that the library is intended to be embedded into applications rather than used as a fully managed networking stack.
It addresses the need for software to speak QUIC and HTTP/3 without having to build those protocol behaviors from scratch. The README emphasizes that applications need a way to process incoming QUIC packets, manage connection state, handle timers, and provide their own I/O loop, and quiche supplies the protocol-side pieces for that job.
At a conceptual level, an application creates a configuration object, sets protocol and connection parameters that are relevant to its use case, and then establishes a client or server connection. The application feeds received network packets into the connection, asks the connection to produce outgoing packets, and reacts to timer expiration by calling the timeout handler and sending more data if needed. The README also notes that pacing hints are exposed for outgoing traffic, and that TLS configuration is part of the configuration model.
The repository appears to be getting attention because it sits at the intersection of Rust, QUIC, and HTTP/3, all of which are active topics for modern network programming. The README also shows concrete adoption signals: Cloudflare uses it for edge HTTP/3 support, Android uses it for DNS over HTTP/3, and curl can integrate it for HTTP/3 support. Its command-line tools and public test site add practical visibility for experimentation.
The README points to curl’s HTTP/3 integration as one adjacent approach, and it also mentions Cloudflare’s own HTTP/3 support and Android’s DNS over HTTP/3 usage as real deployments. Beyond that, the repository itself does not list direct competing libraries, so the safest comparison is that quiche is one way to add QUIC and HTTP/3 support to applications that need a low-level API.
AI-explained · grounded in each repo's README