denoland/celld
self-hosted, distributed Durable Objects observed · 2026-08-28
Health v2 · maintenance only
86/100
- Activity 99
- Release rhythm 98
- Longevity 35
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: 1
- age_days: 495
- days_rel: 13
- days_push: 8
- n_releases_24m: 6
Adoption not part of the score
4272 stars · 144 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded
celld is a self-hosted daemon that runs Cloudflare Workers and Durable Objects on your own machines, with each object backed by its own SQLite database replicated to an object-storage bucket you own. Nodes coordinate solely through the bucket using compare-and-swap, requiring no control plane or consensus, and code written for Cloudflare's platform runs largely unchanged.
Use cases
- self-host Cloudflare Workers and Durable Objects on my own servers
- run stateful serverless apps without a control plane or consensus service
- cut Cloudflare Durable Objects costs at scale
- run a distributed chat or collaborative app with per-user stateful objects
- deploy Workers code to my own fleet with S3-backed durability
- shard application state into per-object SQLite databases
When to choose
- you want Cloudflare Workers/Durable Objects semantics on infrastructure you control
- you need many small stateful objects (chat rooms, documents, agents) with strong single-writer durability
- cost at high resident-cell counts matters more than Cloudflare's managed convenience
- you already have S3-compatible, GCS, or Azure Blob storage to use as the coordination and durability layer
When to avoid
- you need full Cloudflare platform parity - Workers AI, Vectorize, Hyperdrive, Email Workers and more are unsupported and several APIs are only partial
- you need hostile multi-tenant isolation - celld explicitly trusts application code and is not safe for mutually distrusting tenants
- you need managed TLS, custom domains, or a mature production-hardened system - it is an alpha with security fixes only on the latest release
- you require WebSockets that survive object migration between nodes
Facets
service · maturity experimental
http-server websocket database rpc scheduling self-hosted deployment microservices backend cloud-computing self-hosted web-development developer-tools self-hosted rust cli durable-objects cloudflare-workers serverless sqlite object-storage edge-runtime v8 stateful-serverless linux docker
6 sources
- readme: https://github.com/denoland/celld · fetched 2026-08-28 · 28474a99f7b5
- homepage: https://celld.dev · fetched 2026-08-29 · ec32f7e98c65
- site_page: https://celld.dev/docs/cloudflare-compat · fetched 2026-08-29 · 8e38d2b6d045
- site_page: https://celld.dev/docs · fetched 2026-08-29 · 2322f1d402b7
- site_page: https://celld.dev/docs/testing · fetched 2026-08-29 · db73a31d9937
- site_page: https://celld.dev/docs/security · fetched 2026-08-29 · ee09d0f3b50b
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| denoland/celld | main | 86 |
For agents
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem