swerver

Experimental · Zig · tuned configuration · completeness 3/4

Experimental Zig web framework built directly on swerver's Router, HandlerContext, middleware, response, and static-file APIs. No pre-computed response bodies (pre-encoded registry off); JSON is serialized per request through ctx.jsonValue; unary gRPC is decoded and encoded per request over h2c and TLS h2; async-db and fortunes use the native async PostgreSQL client (pipelining, prepared-statement cache, park/resume). Single-threaded event loop per worker, SO_REUSEPORT fork fan-out, one multi-listener process for HTTP/1.1, HTTP/2, HTTP/3 (QUIC), kqueue, epoll, and io_uring backends.

• Official repository
• Benchmark implementation
• All Zig entries, compared
• Open the leaderboard

Achievements

🥇 14 Gold · 🥈 2 Silver. Top three of a field, taken in this entry's own league: the family composite, the same composite among entries written in the same language, and each test profile it is scored on. Every field is the one the badges publish, so a medal and a badge always say the same thing. How medals are awarded.

Composite rank

Each profile of a family is worth 100 to the entry that leads it, and the composite is the sum over the family, less 2.5% for each of routing, middleware, request and response the entry does not do for you - its completeness factor, which the WebSocket and gRPC families do not carry. The field is this entry's own league: engines and reverse proxies are scored apart from frameworks. How it works.

Every result

Alpha Round, 28 runs. Requests per second is the best of three; latency, CPU and memory come from that run.

Compared with

The Zig entries around swerver on the HTTP/1.1 composite, and the one leading them. The last column shows every profile side by side.

Compare swerver with any Zig entry · Compare swerver with any entry, in any language · Every Zig entry, ranked

Results updated 2026-09-25 · How the benchmark is run · The machine · Add or fix an entry