[ammmir]

The main difference is that ExecAPI is intended for running periodic or triggered background tasks, and you're not limited to JavaScript or Wasm code running on just V8. You can run any Docker container as a background job; mix and match Bash, Python, and Node.js if you like. I would say ExecAPI is closer to a combo of Cloudflare Workers Durable Objects and Queues products, than meant to handle/filter HTTP requests traveling to your origin server.

Code ("actions") run in a Docker container using the gVisor runtime. I'm also toying with using firecracker-containerd, which uses Firecracker microVMs underneath.

It's funny you mention that. A previous "iteration" of this project was an edge function runtime, which would take Docker images and convert them to Firecracker VMs, prebooting them, and taking a snapshot at the right moment using some VSOCK magic. It was similar to Fly.io, Lambda@Edge, etc. and ultimately I decided to go another direction because most people don't care about low-latency compute on the edge.