TESIGN
SAVED

EN · KO

Auto-generated — not yet edited · only the numbers are verified

  1. TESIGN / RADAR
  2. REPOSITORY CARD
  3. denoland/celld

denoland/celld

self-hosted, distributed Durable Objects

★ 4.6kDaily star increases over 14 days. Hollow bars mean no data. The last day may be partial.2026-09-03 no data2026-09-04 +42026-09-05 +82026-09-06 +22026-09-07 +22026-09-08 no data2026-09-09 no data2026-09-10 no data2026-09-11 no data2026-09-12 no data2026-09-13 no data2026-09-14 no data2026-09-15 no data2026-09-16 no datalargest one-day increase in the 14 days+8last 14 days · stars per dayhollow = no data

RANKS DATA #19

AT A GLANCE

LANGUAGE
Rust
LICENSE
Apache-2.0
USAGE
Commercial use, redistribution OK. Keep notices; mark changes.
ACTIVITY
last commit 11 days ago ()
HOMEPAGE
https://celld.dev
REPOSITORY
GitHub ↗
CATEGORY
DATA

A summary, not legal advice.

README EXCERPT

celld Self-hosted, distributed Durable Objects . celld is an open-source daemon that runs a Cloudflare Workers application on your own machines: Workers, Durable Objects, KV, Queues, D1, R2, Workflows, Cron Triggers, and static assets, deployed from the wrangler.json that you already have. Each object is a cell: a named server with its own SQLite database. celld stores the long-term state in a bucket that you own — S3-compatible, Google Cloud Storage, or Azure Blob Storage — and needs no serving control plane and no consensus service. A cell that nothing is serving costs almost nothing. Learn more at celld.dev or read the documentation. How it works A node is one celld process, and you run one on each machine. Every node embeds V8 and executes Wrangler bundles. The nodes that share one bucket are a fleet, and that bucket holds the deployments, the cell state, and small ownership records. A conditional bucket write gives a node the ownership of a cell, so exactly one node owns a cell at a time — no membership protocol, no failure detector, no consensus service. Signed peer HTTP provides routing and replicated-log transport. celld captures each committed SQLite write as LTX data, the…

The opening of the GitHub README as stored, at most 1,200 characters. Markdown is not rendered.

TIMELINE

  1. Repository created
  2. Last push
  3. FIRST SEEN BY TESIGN ◌ BACK CATALOG

AI chooses the lists under the owner’s delegation. No human review is running in September 2026. Total stars, increases, cross-source signals, last updates and licences are shown as evidence. How ranks work →

If this repository gets editorial text (why, build, who, start, caveat) it becomes an edited entry. Until then the page shows only stored GitHub metadata and numbers.