self-hosted, distributed Durable Objects
- Your Workers and Durable Objects codification runs unchanged (supported APIs →)
- Your information lives successful a bucket you own
- Orders of magnitude cheaper astatine scale
Install the 58 MB fixed executable
Or tally the docker container
Or conscionable show your agent
❯ create a distributed chat app pinch vite, usage celld.dev and exe.dev, 2 VMs
Key characteristics
Durability
Writers per compartment (epoch-fenced)1
Acknowledged writes mislaid connected kill0RPO=0
Durable constitute latency (region-local)~90ms
Failover aft node loss, 0 lost~20s
Speed (warm)
Stateless petition p50 / p990.2 / 0.3ms
Stateless throughput / worker thread~94kreq/s
Wake a hibernated cell~4ms
Density & cost
RAM per resident cell0.47MB
Resident cells / 8 GB node2,500cells
Inactive compartment cost~0bucket ops
$ / resident cell-month~$0.02
Compatibility
Supported Workers/DO APIsdocs →
Monthly costs vs resident fleet size
0.11101001k10k100k$1$10$100$1k$10k$100k$1M◄ DO free / cheaper10 resident cells — DO $42/mo · celld $49/mo100 resident cells — DO $415/mo · celld $49/mo1,000 resident cells — DO $4,150/mo · celld $49/mo10,000 resident cells — DO $41,500/mo · celld $195/mo100,000 resident cells — DO $415,000/mo · celld $1,949/mo100 resident cells — $49/mo1,000 resident cells — $49/mo10,000 resident cells — $195/mo100,000 resident cells — $1,949/mo1.2 resident cells — DO's included long runs outUnder 1 resident compartment — paid scheme assumed; the free scheme covers this astatine $0DURABLE OBJECTSCELLDRESIDENT CELLSMONTHLY COST
How it works
The bucket is the coordinator — nary rank protocol, nary nonaccomplishment detector, nary consensus. Ownership is simply a grounds successful your bucket, claimed pinch 1 atomic write. celld's built-in replicator continuously ships each cell's SQLite authorities to that bucket arsenic LTX segments.
YOUR INFRASTRUCTUREYOUR S3 BUCKETSQLite / LTX10,000s of inactive cellscelld connected its ain VMcelld connected its ain VMcelld connected its ain VMeach compartment is 1 sqlite databaseLTXrequests / responsesYOUR INFRASTRUCTURErequestsresponsescelld connected its ain VMeach compartment is 1 sqlite databaseLTXYOUR S3 BUCKETSQLite / LTX10,000s of inactive cells
Reliability
Durable Objects is simply a beardown programming model. celld keeps that exemplary while moving placement, state, and operational grounds into infrastructure you choose.
What changes erstwhile you tally the exemplary yourself.
PLACEMENT
No shared instrumentality to lose
A cell's personality isn't fused to a instrumentality — ownership is simply a lease successful your bucket, granted by compare-and-swap. Lose a node and different acquires the lease and restores the compartment successful seconds: your fleet reference your storage, not a vendor restoring a placement you can't see.
BLAST RADIUS
A nonaccomplishment domain you choose
Your fleet still depends connected its machines, network, and bucket provider. What changes is tenancy: nary shared Durable Objects scheduler aliases placement furniture tin mates your exertion to different customer's workload.
LEGIBILITY
A nonaccomplishment you tin read
When a compartment misbehaves the grounds is connected your disk — the ownership record, the SQLite and LTX files, and the logs. You reply “what happened to my cell” pinch sqlite3 and grep, not a position page that declines to say.
Self-hosting is not automatically much reliable. It makes the nonaccomplishment domain definitive and inspectable: your nodes, your bucket provider, and your operational choices.
And to beryllium clear astir the tone: we emotion Cloudflare — this very page is served by a Cloudflare Worker. The Durable Objects exemplary — a single-threaded entity pinch its ain storage, addressed by sanction — is 1 of the champion primitives distributed systems has been handed successful years, and that creation is Kenton Varda's and the Cloudflare Workers team's. celld is simply a emotion missive to their idea; a primitive this bully deserves to tally anywhere.
a stateful distributed strategy that rests wholly connected S3
LTX is Litestream's replica format, from Ben Johnson
English (US) · 
Indonesian (ID) ·