One model, two players
The same Ring VM in the browser and on the server, speaking the same call — so a fullstack application is written once, and a separate declaration decides where each piece runs. The whole idea in three code blocks.
The ideaBlog
Everything worth reading rather than doing. Two pages that explain the whole idea, and the posts — writing from the work itself, no filler. Losses are published with the wins; that is the house style.
Start with these two
The idea behind RingServ, and the answers to what people actually ask.
Questions & answers
Including the awkward ones: why not Node, is it fast enough, does it do HTTPS, what does 0.9 mean, and what it refuses to do. Each answer opens with its verdict, so the page reads in a minute.
Honest answersVision & direction
Why RingServ exists, and where it stands among its neighbours.
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-22For app programmers
Hands-on, every listing runnable.
From a function to a record nobody can edit
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.
Inside the one binary
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.