Stavemark turns a single-tenant application into something your customers can extend. They ship their own handlers, keep their own data, and publish their own endpoints on our edge—while your team never opens a cluster console.
Every tenant's logic runs in a private Stave—metered, capped, and walled off from the services you already operate.
Provision a Stave, a Croze database, a Bung namespace, a Rick bucket and a custom hostname from one API call.
No pools to reserve and no warm-up penalty. The invoice follows the CPU milliseconds your tenants actually burn.
Every primitive on this page carries Stavemark's production traffic—about 412 billion requests a month across 1.8 million tenants. You are building on the parts we already depend on.
Four shapes of product our customers ship on the runtime today
Let third parties add behaviour without handing them your codebase
Give each published site its own handlers, data and hostname
One deploy target for every client build, isolated by default
Run model-driven automation inside the tenant's own boundary
Everything needed to build, ship and meter a multi-tenant product on Stavemark's edge.
An isolated compute runtime where each customer's code executes as part of your own application.
Route requests to tenant Staves, cap what each one may reach, and meter every call for billing.
Stateful primitives for baskets, rooms or per-store configuration—pinned within 40 ms of the people using them.
Hand a tenant a Croze database, a Bung namespace or a Rick bucket without ever handing over a credential.
Dormant code bills $0 and a cold path answers in single-digit milliseconds. Teams report about 68% off duration-based pricing.
Your customer's domain, your latency—certificates and routing are issued and renewed automatically.
Per-tenant usage lands in a ledger you can push into any billing system, for runtime, storage or premium tiers.
Each tenant runs inside its own Stave, with resource ceilings and a security boundary applied before their first deploy lands.
Cellars is built on Staves, so tenant routing, placement and worldwide distribution arrive with the runtime rather than after it.
npm create stavemark@latest my-cellar
Your platform answers from 340+ locations, with Croze databases, Bung storage and Rick object storage available per tenant.
Ship platform code and tenant code side by side—from route handlers down to scheduled jobs, isolated automatically.
Usage counters, invoice hooks and rate ceilings are wired in, so you can charge for the platform from the first week.
Rivenwood
“Stavemark took the piece we kept postponing—safe extensibility—off our roadmap entirely. Our people work on the merchant experience now, not on sandbox plumbing.”
Built into products you already use—and a few thousand you have not met.
Built on the network carrying 10.7% of the open web.
Join the teams who stopped operating clusters and started shipping tenant features. Free tier, no card, no sales call.