OpenOrange runs your app. workerd runs a Worker.
OpenOrange
Runs your whole Cloudflare project in production. Your Workers run on Node.js, and Rivet runs Durable Objects, KV, D1, Queues, Workflows and the rest across your machines. Cloudflare locks your data in. OpenOrange opens it up and live-migrates it, with zero downtime for Durable Objects.
workerd
Cloudflare's core runtime: it executes a Worker, and it's what wrangler dev runs on your laptop. It doesn't run Durable Objects across machines, and it has no KV, D1, Queues or Workflows of its own. Its storage is for development, not data you keep.
Use OpenOrange when…
- You run a Cloudflare project in production on your own cloud.
- You need Durable Objects, Queues or Workflows across machines.
- You need production storage, not a SQLite file on one disk.
- You want stock Node.js, not the
nodejs_compatsubset. - You're live-migrating an app off Cloudflare, or between OpenOrange clusters.
- You want to fork an Actor and its state.
Use workerd when…
- You deploy to Cloudflare and want its exact runtime on your machine to test a Worker.
- Your Worker is a stateless fetch handler and needs nothing else.
Side by side
| Feature | OpenOrange | workerd |
|---|---|---|
| Runs your Cloudflare code as is | OpenOrange Yes: Your code and wrangler config, unchanged. | workerd Partly: The Worker runs. Most bindings call services you build. |
| Live migration of your data | OpenOrange Yes: Off Cloudflare or between OpenOrange clusters, with zero downtime for Durable Objects. | workerd No: No tooling. |
| Production-ready | OpenOrange Yes: Durable Objects and storage included. | workerd Partly: For stateless Workers only. |
| Durable Objects across machines | OpenOrange Yes: Rivet places them across your machines. | workerd No: One process holds every object. |
| Fork an Actor with its state | OpenOrange Yes: Yes, with Rivet Actors beside your Workers. A Durable Object facet clone() is a fork. | workerd No: No. |
| Storage | OpenOrange Yes: Rivet's durable store, in the region you choose. | workerd No: For development. Experimental SQLite on one disk. |
| Database size | OpenOrange Yes: Not capped by host disk. | workerd Not documented. |
| Latency to your database | OpenOrange Yes: In your VPC, next to it, with Durable Objects and storage. | workerd Partly: The Worker can sit next to it. Storage and services are yours to build. |
| KV, D1, R2, Queues, Workflows | OpenOrange Yes: Built in. R2 can use any S3-compatible store. | workerd No: Bindings only. You build the services. |
| Cron Triggers | OpenOrange Yes: Built in, same cron syntax. | workerd No: The handler runs. Nothing fires it. |
| Node.js | OpenOrange Yes: Stock Node.js 22 or later. | workerd No: The nodejs_compat subset. |
| Memory | OpenOrange Yes: Up to your machine's memory. The Node.js heap is configurable. | workerd Partly: No cap, but one process holds every Durable Object. |
| CPU and alarm time | OpenOrange Yes: No CPU cap. Alarms run past 15 minutes. | workerd Partly: No CPU cap. Alarms stop at 15 minutes, hard-coded. |
| Wrangler config | OpenOrange Yes: Read unchanged. | workerd Partly: A few fields. Anything else is an error. |
| Deploy targets | OpenOrange Yes: Rivet Cloud, your AWS, GCP or Azure account, or your own servers. | workerd Any machine. You build the rollout. |
| Managed option | OpenOrange Yes: Rivet Cloud, or BYOC in your account. | workerd No: None, outside Cloudflare itself. |
| License | OpenOrange Apache 2.0 | workerd Apache 2.0 |
| Maintained and supported | OpenOrange Yes: Maintained by Rivet, with support contracts. | workerd Maintained by Cloudflare as the core of Workers. |
Yes Partly No
Compared with workerd's default configuration as of November 12, 2026. workerd read from cloudflare/workerd v1.20261112.1.
The details
Service by service Each Cloudflare service, read from workerd's source.
-
Workers
OpenOrange
Drop-inNode.js.
workerd
SupportedThe production V8 runtime. source
-
Durable Objects
OpenOrange
PartialRivet Actors, spread across your instances.
workerd
PartialSQLite on local disk, marked experimental. One process owns every object. source
-
Workers KV
OpenOrange
Drop-inOne Actor per namespace, strongly consistent.
workerd
Shim onlyCalls are forwarded to a service you write. source
-
Queues
OpenOrange
Drop-inBatching, retries, dead-letter. One batch at a time per queue.
workerd
Shim onlyCalls are forwarded to a service you write. No broker, retries or dead-letter queue. source
-
Workflows
OpenOrange
PartialCloudflare's own engine, one Rivet Actor per instance.
workerd
Shim onlyThe engine is a service you supply. wrangler dev gets it from Miniflare. source
-
Cron Triggers
OpenOrange
Drop-inSame cron syntax.
workerd
Not includedThe handler exists. Nothing fires it.
-
D1
OpenOrange
Drop-inOne Actor's SQLite per database.
workerd
Shim onlyNo d1 binding in the schema. The client wraps a fetcher you provide.
-
R2
OpenOrange
PluggableActor storage, or any S3-compatible store: S3, GCS, R2 or MinIO.
workerd
Shim onlyCalls are forwarded to a service you write. source
-
Cache API
OpenOrange
PartialOne Rivet Actor per cache name. Vary is ignored.
workerd
Not includedThrows "No Cache was configured" unless you supply an HTTP cache. source
-
Hyperdrive
OpenOrange
Drop-inPasses the connection string through.
workerd
PartialPasses straight to Postgres. No pooling.
-
Workers AI, Vectorize, Browser Rendering
OpenOrange
PluggableAI and Browser Rendering use your provider. Vectorize is not supported.
workerd
Not includedShims only. wrangler dev proxies them to Cloudflare.
-
Email Workers
OpenOrange
PluggableSend and receive email through your SMTP server.
workerd
PartialHandler type only. No ingress, no send_email.
-
Static assets
OpenOrange
PartialServes the assets directory with Wrangler's rules. _headers and _redirects are not applied.
workerd
PartialA disk service with no Content-Type, _headers or _redirects. source
-
Service bindings, WebSockets, Wasm
OpenOrange
Partialconnect() and WebSocket upgrades to another Worker throw. Wasm module bindings are not supported.
workerd
Supported -
wrangler config
OpenOrange
Drop-inRead unchanged. A few keys, such as legacy_assets, stop orange dev.
workerd
Partialname, main, compat date and flags, vars, durable_objects, exports and migrations. Anything else is an error. source
workerd read from cloudflare/workerd v1.20261112.1 (e0240de), default configuration. Shim only: the binding ships, the service doesn't. Test results per feature: compatibility; per binding: bindings.
Limits OpenOrange, workerd and Cloudflare. The 128 MB and 30 second caps are Cloudflare's, not workerd's.
-
Memory per Worker
- OpenOrange
- The Node.js heap of the runtime process
- workerd
- No limit
- Cloudflare
- 128 MB
-
CPU time per request
- OpenOrange
- No limit
- workerd
- No limit
- Cloudflare
- 30 s default, 5 min max
-
Subrequests per request
- OpenOrange
- OS limits
- workerd
- No limit
- Cloudflare
- 10,000
-
Alarm wall time
- OpenOrange
- About 24.8 days, the longest Node.js timer
- workerd
- 15 min, hard-coded
- Cloudflare
- 15 min
-
Node.js APIs
- OpenOrange
- Node.js modules, with workerd-shaped process and fs
- workerd
- nodejs_compat subset
- Cloudflare
- nodejs_compat subset
-
Native npm modules
- OpenOrange
- Not tested
- workerd
- No
- Cloudflare
- No
-
Process model
- OpenOrange
- One process per Worker per instance. Rivet places Actors across instances.
- workerd
- One thread per process. You run the load balancer.
- Cloudflare
- Cloudflare's
-
Durable Objects across machines
- OpenOrange
- Yes
- workerd
- No. One process holds every object.
- Cloudflare
- Yes
-
Running untrusted code
- OpenOrange
- Same as any Node.js service
- workerd
- "Not a hardened sandbox"
- Cloudflare
- Hardened
-
Runtime upgrades
- OpenOrange
- Your schedule
- workerd
- Your schedule
- Cloudflare
- Cloudflare's schedule
Cloudflare: Workers Paid plan, checked 2026-10-08. workerd: worker-factory.c++ at v1.20261112.1.
Same project. All of it runs.
Keep your code and your wrangler config.
Built for serious scale.