Cloudflare Containers have been around for a while (still in beta though) to address that. They are using Firecracker VMs under the hood (https://firecracker-microvm.github.io/) and allow you to deploy any Docker image across their infrastructure.
But for somebody who just wants to take their Docker image and deploy, going through the whole Wrangler setup, writing a Worker script, dealing with Durable Objects may be discouraging for quick experimentation.
I built a simple Node.js CLI that implements Heroku/Fly.io developer experience on top of Cloudflare Containers.
1. Open directory with Dockerfile 2. Auth with Cloudflare API token 3. Deploy
- it will create a routing/loadbalancing worker - add Durable Objects and Container bindings - and return live app url within couple of minutes
You can then play with scaling it across regions and instances:
``` flarepilot scale myapp -r eeur,weur -i 1 flarepilot scale myapp -r eeur -i 4 ```
It is a very basic proof-of-concept using locationHints, not ready for production.
Just experimenting for fun.
maxxmini•49m ago
Question: how does cold start compare to Fly.io? Since these are Firecracker VMs under the hood, I'd expect similar performance, but curious if the Cloudflare routing layer adds overhead.