dvarapalaRoadmap
Every feature starts as an RFC (rfc/, see CLAUDE.md). A release lists
the RFCs it implements. Versions stay 0.x (alpha) until a 1.0 is decided.
| RFC | Feature | Status | Target |
|---|---|---|---|
| 0001 | Foundation: engine, L7 rate limit, reverse proxy | implemented | v0.1.0 |
| 0002 | Adaptive detection: heavy hitters, baseline, entropy, optional tree model | implemented | v0.2.0 |
| 0003 | TLS termination with ALPN, HTTPS upstreams, bounded handshakes | implemented | v0.3.0 |
| 0004 | HTTP/2 upstreams, trailers, gRPC-shaped errors, HTTP/2 flood limits | implemented | v0.4.0 |
| 0005 | WebSocket upgrade pass-through with tunnel limits | implemented | v0.4.0 |
| 0006 | Optional HTTP/3 over QUIC with Retry under load | accepted | unplanned |
| 0007 | Forward proxy with per-destination egress rate shaping | accepted | v0.5.0 |
| 0008 | SDKs for Go, Python and JavaScript over a C ABI | accepted | unplanned |
| 0009 | L4 connection limits per client and in total, accept rate, header, idle and body timeouts | accepted | unplanned |