Skip to content

As of

OpenOrange is powered by Rivet.

Already have Cloudflare code? Use OpenOrange. Starting from scratch? Use Rivet. You can also use both.

OpenOrange

For existing Cloudflare code

Runs Cloudflare Workers projects on Rivet. Every Durable Object, KV namespace, D1 database, Queue and Workflow runs as a Rivet Actor, behind the Cloudflare APIs your code already uses.

Rivet

Recommended for new projects

Open-source infrastructure for stateful backends and agents. Rivet Actors are long-lived processes with their own state and SQLite database. Rivet schedules and scales them, and WarpDrive stores their data on S3 behind an SSD tier.

When to use which

Use OpenOrange when…

Your Workers and Durable Objects run as they are.

  • You already have Workers, Durable Objects or other Cloudflare bindings.
  • You want off Cloudflare without a rewrite.
  • You’re moving a live app and can’t take downtime.
  • Your team knows Wrangler: wrangler dev becomes orange dev.

Use Rivet when…

Its API is cleaner, more modern and more flexible than Cloudflare’s, with more features.

  • You’re starting a new backend or agent.
  • You want typed actions, events and realtime connections built in.
  • You want schedules and workflows inside every Actor.
  • You want to fork an Actor and its SQLite database.
  • You write Rust as well as TypeScript.

Use both when…

Keep your existing code on OpenOrange and add Rivet Actors as you need them.

  • Your Cloudflare code works and you’re adding features.
  • A new feature needs something only Rivet has, like realtime events or forking.
  • You want one platform: both run on Rivet, with the same storage and deploy targets.

Side by side

Feature OpenOrange Rivet
Best for OpenOrange Yes: Existing Cloudflare projects Rivet Yes: New projects
API OpenOrange Cloudflare Workers, Durable Objects and bindings Rivet Rivet Actors
Languages OpenOrange JavaScript and TypeScript Rivet TypeScript and Rust
Runtime OpenOrange Node.js 22 or later Rivet Node.js or Bun
Typed actions and events OpenOrange Partly: Durable Object RPC, with no built-in events Rivet Yes: Built in
Realtime connections OpenOrange Partly: WebSockets you wire up yourself Rivet Yes: Built in
Schedules and workflows OpenOrange Yes: Alarms, Cron Triggers and Workflows, as separate APIs Rivet Yes: Part of every Actor
Actor forking OpenOrange Partly: Only through a Durable Object facet `clone()` Rivet Yes: Fork an Actor and its SQLite database
Runs your Cloudflare code as is OpenOrange Yes: 21 Cloudflare APIs, from your Wrangler config Rivet No: No. A different API
Migrate a live app off Cloudflare OpenOrange Yes: orange migrate moves Durable Objects live, with no downtime Rivet No: Rewrite it as Rivet Actors
Storage Same on both WarpDrive: S3 with an SSD tier in front
Deploy targets Same on both Rivet Cloud, BYOC or self-hosted
License Same on both Apache 2.0
Maintained by Same on both Rivet

Yes Partly No

Start with the one that fits.

Cloudflare code: bring it to OpenOrange. New project: build on Rivet.