Why we built a server for Ring
The evening you never get back, five things assembling a stack does not give you, RingServ's position beside Ring's other backends — and the honest list of when you should not listen to us.
Position · 2026-08-22Writing from the work itself — no filler. Three kinds of posts: where this project is going and why, how to build things with it, and what the engineering actually cost. Losses are published with the wins; that is the house style.
Vision & direction
Why RingServ exists, and where it stands among its neighbours.
The evening you never get back, five things assembling a stack does not give you, RingServ's position beside Ring's other backends — and the honest list of when you should not listen to us.
Position · 2026-08-22For app programmers
Hands-on, every listing runnable.
Serve a bare function, grow it into a declared service with a table and a contract, then give it a journal — a sales record that survives a crash and refuses to be quietly altered. About twenty minutes.
Tutorial · 2026-08-22Deep technical
What the engineering actually cost, with the numbers.
How Zig compiles the Ring VM, http.zig, SQLite and QuickJS-ng into one file; N worker VMs and one writer; and the ~970 programs that verify it against native Ring on every change.
Technical · 2026-08-22More lands here as the public plan advances — the JavaScript module story, the family handshake, the phone. Articles arrive when the work they describe is real, not before.