The platform your team likes. The cloud your security team approved.
OpenOrange runs your Cloudflare Workers project inside the AWS, GCP or Azure account you already operate, under the contracts, controls and commitments you already have.
-
Data never leaves your network
Workers, Durable Objects and their storage run inside your VPC, next to your database. There is no third-party edge in the request path and nothing to add to a data-processing agreement.
-
Managed, in your account
With BYOC, Rivet deploys and updates the control plane inside your AWS, GCP or Azure account over an outbound connection. No inbound access. Your cloud bill is the only bill.
-
Or fully self-hosted
Rivet is a single Apache 2.0 binary. Run it on Kubernetes, VMs or air-gapped hardware with no license key, and own the stack end to end.
-
Spend your existing commitments
AWS EDP, Google and Azure commitments and credits pay for OpenOrange. Running on Cloudflare means a second contract, a second vendor review and a second bill.
-
Multi-cloud and exit without a rewrite
The same wrangler config deploys to any target. Run in two clouds for resilience, or move when procurement says so, with one command.
-
Upgrades on your schedule
Deploy when you choose. A stopping runtime closes accepted WebSockets with 1012 Service Restart, so clients reconnect to the new version.
Three ways to run it.
Every option is the same open-source stack. The difference is who operates the control plane and who you call when something breaks.
- Open source
- Community support on GitHub. Apache 2.0, no license key, no feature gating.
- Rivet Cloud and BYOC
- Managed control plane with a support SLA, migration help and an engineer on the call.
- Self-hosted with support
- Run it yourself with a support contract for upgrades, incident response and architecture review.
Bring the platform in‑house.
Tell us what you run on Cloudflare today and we will map it to your cloud, with a migration plan and a number.
Built for serious scale.