celld: Run Cloudflare-Style Stateful Edge Workers on Your Own Hardware

The Deno team released celld this week, an open-source daemon that runs Cloudflare-style stateful edge workers on hardware the operator owns. Instead of a control plane and a consensus service, celld uses ordinary S3-style object storage to coordinate which node owns which small per-user database at any moment. The bucket is the durable source of truth; the nodes are replaceable.

celld is an open-source daemon from the Deno team that executes Cloudflare Workers and Durable Objects on user-controlled machines rather than on Cloudflare's network, according to the project's README at github.com/denoland/celld. Each Durable Object in the model is its own SQLite database, addressed by name and replicated to an S3-compatible bucket the operator runs. Nodes coordinate through that bucket alone, with no separate membership protocol, no failure detector, and no leader election.

Ownership flips with a single compare-and-swap call. celld enforces single ownership with object-storage compare-and-swap, so exactly one node holds a given cell at a time without a consensus service, the project site explains. When a cell moves or wakes up, the new owner restores the cell's SQLite database from the bucket and resumes execution. Idle cells hibernate to nearly nothing. Because every object is its own small database, applications shard by construction, and contention or blast-radius failures of one shared database are designed out rather than managed.

Every celld node embeds V8 and runs Wrangler bundles, the docs note, so existing Workers projects can redeploy onto self-hosted nodes with celld deploy (with esbuild on PATH). Distribution ships as a signed curl-installable binary, verifiable with gh attestation verify, and a Docker image at ghcr.io/denoland/celld for Linux x86-64 and ARM64. State lives in a Docker volume and the standard AWS credential chain. A testing guide and a live docs site are part of the launch surface.

celld inherits whatever durability and availability the operator's bucket provides; you trade Cloudflare's proprietary control plane for an operator's S3 contract, and the project says so. The bet is replacing a control plane and consensus with compare-and-swap on a bucket, and the same-day Hacker News thread is the first-cycle reception signal, not a benchmark.

Cloudflare's Durable Objects model has also pushed a generation of teams onto a proprietary control plane, and celld's escape hatch is the constructive reason the project is worth covering. The Deno team's project landing page is the public surface, and the first deployment story is the one the project tells. Independent benchmarks, customer migrations, and operational data points are not yet visible in the source material.