EDGE Signal 460
Celld runs Durable Objects on your own fleet, using S3 as the coordinator and SQLite for state
↗
Celld provides a self-hosted Durable Objects model where an S3 bucket acts as the coordinator and SQLite state is replicated via LTX segments.
This matters because it moves Durable Objects off a shared vendor scheduler onto infrastructure you control, making failure domains explicit and inspectable. Engineers can debug cell failures with sqlite3 and grep instead of a status page, and they avoid coupling to another customer's workload.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
Celld uses an S3 bucket as the coordinator, claiming cell ownership with a single atomic write and no consensus.
A built-in replicator continuously ships each cell's SQLite state to the bucket as LTX segments.
Self-hosting makes the failure domain explicit and inspectable, with ownership records, SQLite and LTX files, and logs on your disk.
THE CLUSTER