Skip to content

As of

OpenOrange is built for production. celld was an experiment.

Both run Cloudflare Workers and Durable Objects on your own servers. OpenOrange runs on Rivet, which keeps shipping. celld went quiet after Cloudflare acquired its developer.

OpenOrange

Your Cloudflare project in production, on your own cloud. The Workers API runs on Node.js. Rivet places every Durable Object across your machines, and WarpDrive stores its data on S3 behind an SSD tier. Cloudflare locks your data in. OpenOrange opens it up and live-migrates it, with zero downtime for Durable Objects.

celld

No release since Oct 21, 2026

Self-hosted Workers and Durable Objects, built by Deno. It runs its own Workers runtime on V8 and keeps each active cell’s SQLite file on local disk, replicated to a bucket. Cloudflare acquired Deno in October 2026.

Why OpenOrange

Six reasons to run your Durable Objects on OpenOrange instead of celld.

  1. Rivet ships faster

    Rivet ships features faster than Cloudflare, such as Actor forking, bottomless disk and agentOS, which runs code in lightweight VMs. We believe that makes Rivet a better foundation for Durable Objects than celld.

  2. No runtime limitations

    OpenOrange is built to remove the runtime limitations of celld and Cloudflare. It has no 128 MB memory limit, runs vanilla Node.js, and has bottomless SQLite storage.

  3. Years of scaling Actors

    Rivet’s architecture is significantly different from celld’s, built from years of experience scaling Actors. OpenOrange has better SSD cache hits, lower storage costs and better performance.

  4. Live migrations

    OpenOrange invests in live migrations from Cloudflare infrastructure, and between OpenOrange deployments.

    celld imports no Durable Object data, and some of its upgrades meant stopping the whole fleet.

  5. Proven integrations and features

    OpenOrange focuses on proven ecosystem integrations, such as OpenRouter, Browserbase, Amazon SES, E2B, Daytona and Freestyle, instead of Cloudflare’s walled-garden services. It also runs Workers AI, Email, Hyperdrive, Browser Rendering, Rate Limiting and Tail Workers, with more coming soon.

    celld runs none of those six.

  6. Support and longevity

    Cloudflare doesn’t make money from celld and has no incentive to support it beyond hobbyist and marketing use cases. Rivet supports OpenOrange professionally, because it’s tied to Rivet’s revenue.

    celld’s last release was Oct 21. Its pull requests are disabled, and only the latest release gets security fixes.

When to use which

Use OpenOrange when…

  • You run Cloudflare code in production.
  • You need storage that’s fast and stays online through S3 outages.
  • You’re live-migrating an app off Cloudflare, or between OpenOrange deployments.
  • You want proven integrations, not Cloudflare’s walled garden.
  • You want a maintained project with support behind it.

Use celld when…

  • You want to study a compact design for Durable Objects on one bucket.
  • You’ll maintain your own fork, security fixes included.
  • You need Python fetch handlers, which OpenOrange doesn’t run.

Side by side

Feature OpenOrange celld
Rivet ships faster
Actor forking OpenOrange Yes: Yes, with Rivet Actors beside your Workers celld No: No
Bottomless storage OpenOrange Yes: Yes. SQLite isn’t capped by host disk celld No: No. Bound by the node’s disk No per-cell quota.
Lightweight VMs for dynamic code OpenOrange Yes: Worker Loader runs each dynamic Worker in an agentOS VM Sandboxes can run in one too. celld No: No. A Dynamic Worker runs in the loader’s process “It is not a second process or a virtual machine.”
No runtime limitations
Memory OpenOrange Yes: No 128 MB cap: your machine’s memory Node.js heap: up to about 4 GB by default, configurable celld Partly: 128 MB heap per isolate by default Configurable. Over 90%, new hibernatable WebSockets are refused.
Node.js OpenOrange Yes: Vanilla Node.js 22 or later celld Partly: A listed subset of node: modules Other node: modules import, then throw on first call.
CPU and alarm time OpenOrange Yes: No cap celld Not documented
Years of scaling Actors
Durable Objects across machines OpenOrange Yes: Yes. Rivet places Actors across your machines celld Partly: Yes. Only hibernated cells move, placed by CPU count
Storage OpenOrange WarpDrive: S3 with an SSD tier in front celld A local SQLite file per active cell, replicated to peers and a bucket
Storage latency OpenOrange Yes: 0.6 ms from the SSD tier, not 50–200 ms from S3 celld Partly: After a cell moves, its pages load from the bucket on first use Until they’re filled in, “a large query can take minutes.”
S3 outage OpenOrange Yes: Hot and new Actors stay online celld The bucket holds every node lease and cell ownership record
S3 request cost OpenOrange Yes: SSD tiering cuts it by orders of magnitude celld Each commit is uploaded to the bucket
Deploy targets OpenOrange Yes: Rivet Cloud, BYOC or self-hosted celld Your servers, plus an S3, GCS or Azure bucket
Live migrations
Live migration of your data OpenOrange Yes: orange migrate moves Durable Objects live, with no downtime Off Cloudflare, or between OpenOrange deployments. celld No: No. Imports KV exports and D1 SQL only Some v0.6.0 upgrades meant stopping the whole fleet.
Proven integrations and features
Ecosystem integrations OpenOrange Yes: Services you choose, for AI, browsers, email and sandboxes Any OpenAI-compatible, Chrome DevTools or SMTP endpoint. celld No: Cloudflare’s own services only No providers for AI, browsers or email.
Sandboxes for untrusted code OpenOrange Yes: E2B, Daytona, Freestyle or agentOS E2B, Freestyle and agentOS run each sandbox in a VM. celld Partly: Docker or Podman on each node By default a container shares the node’s kernel. Experimental.
Runs your Cloudflare code as is OpenOrange Yes: 21 Cloudflare APIs celld Partly: Workers, Durable Objects, KV, D1, R2, Queues, Workflows and Cron
Workers AI OpenOrange Yes: Text and embedding models, on OpenRouter or any OpenAI-compatible API celld No: No
Email OpenOrange Yes: Send and receive, through Amazon SES or any SMTP server celld No: No
Hyperdrive OpenOrange Yes: Works unchanged, straight to your database celld No: No Workers that use it need changes.
Browser Rendering OpenOrange Yes: Your Puppeteer code, on Browserbase or any Chrome DevTools endpoint celld No: No
Rate Limiting OpenOrange Yes: Yes, one exact counter per namespace celld No: No
Tail Workers OpenOrange Yes: Yes, through Rivet Durable Streams celld No: No. The tail() handler is unavailable
Support and longevity
Support model OpenOrange Yes: Professional support from Rivet, tied to its revenue Rivet has invested in this platform since December 2024. celld No: No paid support. Cloudflare doesn’t make money from it
Production-ready OpenOrange Yes: Built for production on Rivet celld Partly: Beta, by its own docs
Security fixes OpenOrange Yes: Yes, from Rivet celld No: Latest release only “Only the latest release receives security fixes.”
Managed option OpenOrange Yes: Rivet Cloud, or BYOC in your account celld No: Self-hosted only
License OpenOrange Apache 2.0 celld Apache 2.0 Pull requests are disabled. Patches go by email.

Yes Partly No Storage figures for OpenOrange are WarpDrive’s, Rivet’s storage engine. celld as of v0.6.3, its last release.

What happened to celld

Cloudflare acquired Deno, celld’s developer. celld has been silent since its last release.

  1. v0.1.0 starts a run of 12 releases in 11 weeks. source

  2. Cloudflare announces that Deno, celld’s developer, is joining it.

  3. A user asks what celld’s future is. No maintainer answers. source

  4. v0.6.3, the last release and the last maintainer comment. source

  5. Since

    No commits and no releases. 22 new issues, none answered. source

Storage that doesn’t wait on S3

OpenOrange keeps every Durable Object, KV namespace, D1 database, Queue and Workflow on WarpDrive, Rivet’s storage engine. It’s backed by S3 and runs at SSD speed.

  • 0.6 ms

    Storage latency

    S3 takes 50–200 ms. WarpDrive’s SSD tier answers in 0.6 ms.

  • Beyond S3’s 99.9%

    Availability

    The SSD layer keeps hot and new Actors online when S3 is down.

  • Orders of magnitude

    Lower S3 request cost

    SSD tiering spreads each S3 request across many writes.

Same Wrangler project. Built for production.

Run orange dev in your Worker project.