celld matters because stateful serverless primitives—Durable Objects—are useful for real-time coordination and per-user state, but relying on a single provider or shared database creates contention and operational coupling. celld replaces that central dependency with a simple, object-per-database model that makes sharding, isolation, and replacement of nodes natural rather than an operational burden.
What Sets It Apart
- Object-per-database architecture: every Durable Object is a separate SQLite database that is continuously replicated to an S3-compatible bucket, so contention is localized and failures affect only the objects involved.
- No membership protocol or consensus: ownership is negotiated with object-storage compare-and-swap leases in the bucket, which avoids running a separate control plane, membership service, or consensus system.
- Practical hibernation and lifecycle: idle cells hibernate to minimal resource use and can be reacquired and restored by another node, supporting large fleets with low idle cost.
- Secure, minimal peer surface: peer HTTP traffic is HMAC-authenticated and clock-bounded; operators are expected to run peers on private or encrypted networks (WireGuard, Tailscale) rather than exposing peer ports publicly.
How It Works (short)
Nodes embed V8 and run Wrangler bundles. The fleet shares an S3-compatible bucket that holds deployments, per-cell SQLite payloads, and small ownership records. A node owning a cell restores the SQLite file and resumes execution; when it sheds or moves a cell, that cell’s database is durably replicated and published as unowned for other nodes to acquire.
Who It's For (and trade-offs)
Great fit if you need self-hosted, strongly isolated stateful serverless units (e.g., per-user Durable Objects for real-time apps, agent backends, or multiplayer rooms) and you can operate a private network plus secure access to an S3-compatible bucket. Look elsewhere if you require a fully managed global control plane, built-in multi-master consensus, or need a drop-in replacement for Cloudflare’s global managed Durable Objects with identical operational guarantees—celld trades provider-managed global control for simplicity and replaceability.
Where It Fits
Positioned as an on-prem / self-hosted runtime for applications that benefit from object-local state and predictable failure domains. It complements systems that prefer per-tenant or per-session data isolation and want to avoid a monolithic database bottleneck.
