Every multiplier traces to a mechanism
Not adjectives — line items. Each claim below names the machinery that produces it.
Scale to billions
Every person gets their own instance with its own database. A crash, a leak, or a runaway query takes down one person's process — the next request restarts it, and nobody else notices. Growing means adding boxes to the fleet, not architecture to your app.
receipt: per-person instances · blast radius of one · add boxes, not architecture
Build 100× faster
AI is the factory. Extravagant machines are spent at build time — at length, under tests that fail the build — to produce one lean artifact. The compute is spent once, at the factory; what ships stays small forever.
receipt: extravagant machines in · one lean artifact out
1000× faster performing
There is no network hop to a database. SQLite is compiled into the process, so a query is a function call and your data lives next to your compute — microseconds where a round trip costs milliseconds. Even a sleeping instance wakes in milliseconds.
receipt: a query is a function call, not a round trip
30× cheaper and more efficient
Most software is used a few hours a week and billed for all 168. On CARLOS, an idle app hibernates to object storage — a few objects in a bucket, no process, no memory, costing nothing — and wakes on the next request.
receipt: pay for the hours used, not all 168
From branch to stable without a rebuild
One artifact, three pointers. What you tested is what ships, because it is the same bytes.
A live URL for every branch
Push a branch, get a canary URL in seconds — a real deployment on the real platform, not a localhost preview. Send it to a teammate before the code review starts.
Promote bytes, not hopes
Promotion points a wider channel at the same immutable, content-addressed artifact: canary → beta → stable. Nothing is ever rebuilt on the way to production.
Rollback is a pointer move
Point the channel back at the previous release and the bleed stops. Immediate, no rebuild, no waiting — going backwards is never new code.
Static sites ride the same pipeline
A static site is a content-addressed file tree on the same channels: canary URL per branch, same promotion, same rollback. This page ships that way.
Safe to deploy, safe to be deployed to
The scary step in any pipeline is the pointer that says “this is stable now.” The platform makes it boring.
A bake window between a publisher and your fleet
A new release must sit on its channel for 72 hours before stable instances adopt it — so a compromised publisher can't rush a poisoned build across your fleet. The blast radius stays with the people who opted in early.
Rollback skips the bake: pointing back at a hash that already served traffic takes effect immediately.
Residency, enforced below your code
Declare where your data lives — per app, or per customer instance — and a host outside that region will never claim it. There is no “just this once during a failover” code path: no eligible host means the wake fails loudly instead of quietly relocating.
Sleeping data rests in region-scoped buckets too. Residency covers rest as well as execution — enforced by the platform, not promised in a policy PDF.
The whole platform is
That is the complete dependency list. The platform is open and self-hostable: no proprietary control plane, no license server, no essential piece that only exists in someone else's account. Run it on our cloud because it's convenient — and if you ever want to leave, copy the binary, take your bucket, point your DNS, and walk away with everything still running.
In production today
Real companies, real traffic
The first production tenants are live: an event-ticketing company and a training platform run on CARLOS deployments today. Their apps live at <sqid>.oncarlos.com — an address that never encodes region or host, so placement stays invisible — with custom domains riding on top as aliases.
Ship something this afternoon
A canary URL is seconds away.