Skip to content

Latest commit

 

History

History
43 lines (32 loc) · 1.62 KB

README.md

File metadata and controls

43 lines (32 loc) · 1.62 KB

Cello

Self-hosted, distributed Durable Objects.

Cello 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 you already have. Each object is a cell: a named server with its own SQLite database. Cello stores the long-term state in your S3-compatible, Google Cloud Storage, or Azure Blob Storage bucket. It needs no serving control plane or consensus service, and an inactive cell costs almost nothing. One 8 GB node holds about 1,000 resident cells, about $0.05 each per month.

Install

curl -fsSL https://cello.ryuz.eu/install.sh | sh

Then run the Quickstart: a Worker with a Durable Object on cello dev, then a two-node fleet that shares one bucket. Takes about 15 minutes.

Docs

https://cello.ryuz.eu — Install · Quickstart · Run a fleet · Services · Changelog

Based on celld

Cello is a renamed continuation of celld by Deno Land Inc. — what Cello adds over upstream documents every improvement. Cello reads celld-written data; stop all celld nodes first (a mixed fleet is unsupported), rename CELLD_* variables to CELLO_*, and start Cello. See Upgrading to 0.2.0.

License

Apache-2.0; see NOTICE.