Why the edge runtime uses V8 isolates

Most edge platforms run your function inside their network, behind their billing meter. It works — until you need a guarantee that the layer underneath you won't change. We are building the edge runtime as V8 isolates inside a stack we operate ourselves. Today that stack runs on one rented cloud server in one region, and the runtime is in preview.

Isolates, not containers

A container has to boot. An isolate doesn't. V8 isolates share a single process and spin up a fresh, sandboxed JavaScript context without waiting for an OS image to come alive. We have not published a cold-start benchmark yet, so we make no latency promise here. Your code executes against standard Web APIs — Request, Response, fetch, streams — so there's no proprietary runtime to learn and nothing to rewrite if you ever leave.

Why owning the metal matters

When you run the whole stack yourself, the numbers stop being someone else's abstraction. There is no container scheduler and no multi-tenant queue in front of you. And there is no third-party CDN or proxy in the request path: between a user and your code there is only our own reverse proxy and gateway, on the cloud server we rent.

The trade-off we accept

Owning infrastructure is harder than renting it. We run the hardware, the network, and the control plane ourselves. We think that's the point: a developer platform that depends on a competitor's PaaS in its own operations is one pricing change away from a bad day. Self-sufficiency is the feature.