# denoland/celld

self-hosted, distributed Durable Objects

Repository: https://github.com/denoland/celld
Canonical: https://ross.abutalabs.com/products/celld
Homepage: https://celld.dev
Language: Rust
License: Apache-2.0
License Family: permissive
Last push: 2026-08-25T22:38:18+00:00

## Health v2 (maintenance only)
Score: 86/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 99, release rhythm 98, longevity 35
- inputs: {"age_days": 495, "days_push": 8, "days_rel": 13, "gap_med": 1, "n_releases_24m": 6}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 4272, forks 144 (observed 2026-08-28T04:08:40.714815+00:00)

## What it is
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
- artifact type: service
- maturity: experimental
- function: http-server, websocket, database, rpc, scheduling, self-hosted, deployment
- domain: microservices, backend, cloud-computing, self-hosted, web-development, developer-tools
- platform: self-hosted, rust, cli
- tags: durable-objects, cloudflare-workers, serverless, sqlite, object-storage, edge-runtime, v8, stateful-serverless, linux, docker

## Member repositories
- denoland/celld (main) score 86

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:08:40.714815+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-29T18:22:00.907605+00:00, confidence not recorded.
  - readme: https://github.com/denoland/celld (fetched 2026-08-28T04:08:40.714815+00:00, sha 28474a99f7b5)
  - homepage: https://celld.dev (fetched 2026-08-29T09:11:31.388217+00:00, sha ec32f7e98c65)
  - site_page: https://celld.dev/docs/cloudflare-compat (fetched 2026-08-29T09:11:31.397420+00:00, sha 8e38d2b6d045)
  - site_page: https://celld.dev/docs (fetched 2026-08-29T09:11:31.399397+00:00, sha 2322f1d402b7)
  - site_page: https://celld.dev/docs/testing (fetched 2026-08-29T09:11:31.403754+00:00, sha db73a31d9937)
  - site_page: https://celld.dev/docs/security (fetched 2026-08-29T09:11:31.405691+00:00, sha ee09d0f3b50b)
- Data as of 2026-08-30T08:39:29.467469+00:00.