Runs existing Cloudflare Workers and Durable Objects projects on AWS, Google Cloud, Azure or self-hosted servers, using the Rivet control plane
- Language
- TypeScript
- License
- Apache-2.0
- Stars
- 587
- Try it
pnpm add -g open-orange && orange dev
Rivet, a startup that builds infrastructure for stateful backends and agents, has released OpenOrange, an open-source tool that takes an existing Cloudflare Workers project and runs it on AWS, Google Cloud, Azure or your own machines. It doesn't change your code. The launch post is dated November 12. The repository is Apache 2.0 licensed, written mostly in TypeScript, and had 587 stars and 21 forks on November 15, according to GitHub's search API.
Why it matters: Durable Objects, Cloudflare's stateful compute primitive, have had no standard way out. Rivet's post notes that Cloudflare offers no built-in export for Durable Object data. If you've built on Workers and your bill or the platform's limits are starting to hurt, OpenOrange is the first serious attempt at a no-rewrite exit. It's also a sales funnel for Rivet's managed cloud, and its headline numbers come from Rivet.
How it works
You keep your wrangler config. The orange CLI stands in for Wrangler, according to the README:
pnpm add -g open-orange # needs Node.js 22+ and pnpm; deploying also needs Docker
orange dev # replaces `wrangler dev`, serves on localhost:8787
orange deploy # builds a Docker image and rolls it out to a Rivet cluster
orange migrate # moves Durable Objects off Cloudflare
There's no Cloudflare runtime underneath. Rivet says OpenOrange is not a fork and doesn't run workerd. It reimplements the Workers API on stock Node.js and maps each Cloudflare service onto Rivet. Each Durable Object becomes a Rivet Actor with its own SQLite database, stored in S3. Rivet does reuse some MIT-licensed Cloudflare code, including the Workflows engine.
You can run it on Rivet Cloud (managed), as BYOC (your cloud account, operated by Rivet) or fully self-hosted, with Rivet's control plane on Kubernetes, ECS, Docker Compose, Hetzner or a plain VM.
The claims, and what's behind them
Rivet's comparison against Cloudflare's paid-plan meters, from the launch post:
| Meter | Cloudflare | OpenOrange on AWS (Rivet's model) | Rivet's claim |
|---|---|---|---|
| Durable Object compute, per GB-hour | $0.045 | $0.0094 | 4.8× cheaper |
| Workers CPU, per vCPU-hour | $0.072 | $0.051 | 1.4× cheaper |
| Durable Object SQLite storage, per GB-month | $0.20 | $0.023 | 8.7× cheaper |
| SQLite writes, per million rows | $1.00 | $0.18 | 5.7× cheaper |
| KV writes, per million | $5.00 | $0.18 | 28.4× cheaper |
These are modelled figures, not invoices. According to the cost model on openorange.dev, they assume on-demand AWS Graviton instances in us-east-1 with 40% spare headroom, at list prices checked October 8, 2026. The write price comes from one workload Rivet measured: 5,000 agents each doing a small SQLite upsert every 10 seconds, which cost $232 in S3 requests for 1.32 billion writes a month. Rivet says your cost per write will depend on your workload.
The model leaves out ops time, and Rivet Cloud and BYOC fees are priced separately. Calls from Cloudflare to a database in AWS still pay AWS egress ($0.09/GB, per the site). General Workers CPU is claimed to be only 1.4× cheaper, so the big savings are on busy Durable Objects and storage-heavy bindings. The README concedes that for small, spiky Workers, Cloudflare's free tier and per-request pricing are often hard to beat.
On limits, Cloudflare's paid plan gives each Worker 128 MB of memory. OpenOrange gives it whatever the machine has (the Node heap defaults to about 4 GB), and drops the CPU-time, 10 GB per-object storage and 64 MiB bundle caps, per the README.
What doesn't work yet
The README says your code runs "unchanged," but its own binding table is more cautious:
| Status | Bindings |
|---|---|
| Drop-in | KV, D1, Rate Limiting, Queues, Cron Triggers, Hyperdrive |
| Partial (known differences) | Durable Objects, Cache, Workflows, Tail Workers, Worker Loader |
| Pluggable (bring a provider) | R2 (S3, GCS, MinIO…), Workers AI (OpenAI-compatible APIs), Send Email (SES/SMTP), Browser Rendering, Sandbox |
| Not supported | Vectorize, Images, Media, Stream, Pipelines, AI Search, mTLS certificates, VPC (calls throw); Analytics Engine silently drops data points |
Other gaps the project acknowledges:
- Migration: Durable Objects move with no downtime, but D1 databases go offline for a few minutes while they copy. R2 buckets have to be moved separately with S3 tools.
- Regions: Multi-region Durable Objects, including edge regions, are listed on the site as an upcoming update. Today it runs wherever you deploy it. Rivet argues that sitting next to your database beats being at the edge.
- Evidence: Neither the launch post nor the homepage gives a compatibility pass rate. Rivet points to an
orange doctorcommand that checks your project, plus per-binding notes.
Independent coverage so far is thin. A DEV Community roundup called it the most interesting portability project of the week. It also warned that early stars say nothing about production readiness, and that "runs unchanged" has to be tested against your own app. RuntimeWire reports that Rivet co-founders Nathan Flurry and Nicholas Kissel built it. OpenOrange states it isn't affiliated with or endorsed by Cloudflare, and we found no public response from Cloudflare.
One caution: the README's suggested coding-agent prompt starts by connecting Rivet's hosted MCP server and signing in to Rivet. If you plan to self-host, follow the manual steps instead.
Who should try it
- Teams with busy Durable Objects or big KV/D1 bills. Run
orange devon a branch, thenorange doctor. Price your own workload against Cloudflare's meters before trusting the multipliers. - Teams hitting the 128 MB or CPU-time limits, or who need packages that
nodejs_compatcan't load. - Teams with data-residency rules that need to choose the region or datacentre.
If your Workers lean on Vectorize, Images, Stream or Analytics Engine, wait. Those bindings either throw or drop data today.
Sources
- Rivet — Introducing OpenOrange: Run Cloudflare Workers Anywhere rivet.dev
- GitHub — rivet-dev/open-orange github.com
- OpenOrange — project site and cost model openorange.dev
- DEV Community — Azure Outage Triage, Browser MCP, Code Security, and Agent Tools dev.to
- RuntimeWire — Rivet launches OpenOrange to run Cloudflare Workers on your own cloud runtimewire.com