OpenOrange is a platform for running Cloudflare Workers outside Cloudflare, using Node.js and Rivet to provide the Workers API and its bindings. It offers three deployment models: a managed Rivet Cloud cluster in a chosen AWS or Google Cloud region, Rivet-operated infrastructure in a customer’s AWS, Google Cloud, or Azure account, or self-hosting on cloud servers or on-premises. The project says existing Wrangler configuration and app code can stay unchanged, with the orange CLI used for local development and deployment. It supports bindings including Durable Objects, KV, D1, R2, Queues, Workflows, and Cron Triggers; several others, such as Vectorize and Images, are not yet implemented.
The main case for switching is lower infrastructure cost and fewer runtime restrictions. Price comparisons based on listed cloud rates claim compute can be 4.8 times cheaper and storage 8.7 times cheaper, with still larger savings for some database and workflow operations; actual write costs depend on workload. OpenOrange also removes Cloudflare’s stated limits on memory, CPU duration, connections, storage, and bundle size, subject instead to the chosen hardware. Its migration tool transfers Durable Objects while the application remains available, using lazy copying and a later backfill; D1 requires a brief interruption because Cloudflare does not support live migration. OpenOrange is Apache 2.0, while managed and BYOC services have separate pricing.
Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.