swerver

A bare-metal HTTP/1.1 + HTTP/2 + HTTP/3 server and application framework written in pure Zig. No garbage collector, no hidden allocations, no per-request heap churn: fixed-size buffer pools and stack-allocated parsing on every hot path.

HTTP/1.1 ──┐
HTTP/2   ──┼──► swerver ──► kqueue / epoll / io_uring ──► your handlers
HTTP/3   ──┘      │
                  └── QUIC (RFC 9000-9002)

Alpha

The public API in src/lib.zig may change between alpha versions while it's iterated on; breaking changes are noted in release notes. See Limitations & roadmap for what's in and out of scope today.

A minimal server

const std = @import("std");
const swerver = @import("swerver");

fn hello(ctx: *swerver.router.HandlerContext) swerver.response.Response {
    return ctx.text(200, "hello, galaxy");
}

fn item(ctx: *swerver.router.HandlerContext) swerver.response.Response {
    // Return a struct: swerver serializes it with std.json.
    return ctx.jsonValue(200, .{ .id = ctx.getParam("id"), .active = true });
}

pub fn main() !void {
    var gpa: std.heap.DebugAllocator(.{}) = .init;
    defer _ = gpa.deinit();

    var router = swerver.router.Router.init(.{});
    try router.get("/hello", hello);
    try router.get("/items/:id", item);

    const server = try swerver.ServerBuilder
        .configDefault()
        .router(router)
        .build(gpa.allocator());
    defer { server.deinit(); gpa.allocator().destroy(server); }

    try server.run(null); // listens on 0.0.0.0:8080
}

Where to next

• Getting started: install, write your first server, run from a config file.
• Guide: routing, handlers & responses, middleware, configuration, protocols, proxy, PostgreSQL.
• Operations: deployment, observability, the admin API.
• Reference: CLI flags, build options, the full config schema.