Technology1 min read

Run Cloudflare Workers Anywhere

By · Published by Everything Blog

In short

OpenOrange implements the Workers API on stock Node.js, using Rivet as its underlying control plane to run workloads across environments like AWS, Azure, and Google Cloud. The framework maintains workflow compatibility by supporting standard Wrangler configurations, bindings, and environment variables via the orange command-line interface. Each Durable Object runs as a Rivet Actor powered by its own SQLite database. While a built-in migration tool moves Durable Objects with zero downtime, transitioning D1 databases requires a brief multi-minute service interruption.

Key points

  • Developers can maintain their existing Wrangler configurations and bindings while targeti…: Developers can maintain their existing Wrangler configurations and bindings while targeting alternative cloud providers or on-premises infrastructure.
  • Stateful Durable Objects transfer between environments without downtime and run as Rivet…: Stateful Durable Objects transfer between environments without downtime and run as Rivet Actors with individual SQLite databases.
  • The platform targets lower operational costs for heavily utilized applications compared t…: The platform targets lower operational costs for heavily utilized applications compared to metered GB-second and write pricing.

Sources checked by our analysis pipeline: 1

Run Cloudflare Workers anywhere.

- AWS

- Google Cloud

- Azure

- Rivet Cloud

- Your servers

The same developer experience, without the runtime limits, for a fraction of the bill.

Built for serious scale.

Run it where you want.

Next to your database, in the cloud and region you choose.

Same work. A fraction of the bill.

Cloudflare's meters, priced on raw AWS.

- 4.8×

- 8.7×

- 5.7×

No runtime limits.

128 MB is all the memory a Cloudflare Worker gets. OpenOrange runs your Workers and Durable Objects on machines you choose, so the limits are your hardware's.

Limit | Cloudflare Workers Paid | OpenOrange |

---|---|---|

Memory per Worker or Durable Object | Up to your machine's memory Node.js heap: up to about 4 GB by default, configurable | |

CPU time per request | No cap | |

Cron, queue and alarm handlers | No cap | |

Open connections per request | OS limits | |

Storage per Durable Object | No cap | |

Worker bundle | No cap | |

Node.js | Stock…

Technology