a request, served
Zero
A batteries-included web framework: REST, SQL, pub/sub, auth, GraphQL, metrics and tracing — compiled into one static binary and configured through .env, not glue code. One binary, tens of thousands of req/s, no GC pausing.
the dot is online — zero, and everything after it
zerolabz gathers foundational tools that push the zig language forward — a framework, a workflow engine, a data engine, an agent runtime and a book. Nothing clever to hide behind. Just code that compiles.
the works
Each engraving below animates the one thing its module is for. They all compile against zig 0.16.0 — the version zero is pinned to.
a request, served
A batteries-included web framework: REST, SQL, pub/sub, auth, GraphQL, metrics and tracing — compiled into one static binary and configured through .env, not glue code. One binary, tens of thousands of req/s, no GC pausing.
a run's history, kept
Durable, Temporal-style workflows in a single zig binary. Every step is an event in SQL, so a run resumes exactly where it left off — after a crash, a deploy, or a wait of months. Workers decide how; the loom decides when.
the flip keeps the value
One uniform pipeline — Source → Transform → Sink — across every zero backend. Subscribe pub/sub into time series, pull SQL into events, capture websockets into SQLite. The data never changes; coin only flips it.
the agent loop, always answering
A single-binary AI agent runtime in zig. Connect any LLM to any chat channel — workspace-scoped tools, hybrid SQLite memory, cron-scheduled tasks, and a circuit breaker that survives model outages. ~7 MB, no runtime deps.
an open source book, page by page
An open-source book for learning zig — where the docs are the code. Prose never hides runnable logic: every snippet compiles, runs and diffs in CI against a pinned toolchain, targeting zig 0.17, the future first.
coda
No committee, no rewrite, no roadmap bigger than the next commit. Small tools that compile fast and outlive trends — that is the whole bet, and it keeps paying.