About Celld
Celld is a self-hosted, distributed Durable Objects runtime that runs on your own VM and stores state in your S3 bucket. It serves teams who want Durable Objects-like primitives with full control over placement, state, and failure domains, rather than relying on a managed cloud.
Key Features
Seen in practice, Celld coordinates object ownership through your bucket and ships per-cell SQLite state as LTX segments, so you can run many isolated cells without a shared scheduler:
Lease-based ownership
A cell’s identity is a lease in your bucket, granted by compare-and-swap; if a node fails, another instance takes over and restores the cell in seconds.
Isolated tenancy
There’s no shared Durable Objects scheduler between tenants; your fleet, bucket provider, and network choices determine placement and failure domains.
Per-cell SQLite with LTX replication
Each cell is a separate SQLite database; its state is replicated to the bucket as LTX segments for durability and offline access.
Local diagnostics and provenance
Ownership records, SQLite/LTX files, and logs live on disk, so you can inspect exactly what happened with standard tools.
Summary
Best for platform teams, backend engineers prototyping stateful distributed apps, and SREs who want explicit control over placement and failure domains.
