TypeScript at the edge
Cloudflare Workers run TypeScript inside V8 isolates instead of VMs or containers: sub-millisecond starts, no cold-start boot cost, and a stack built around that same disposable unit of compute.
A request to a Cloudflare Worker doesn't reach a server. It reaches a V8 isolate — the same sandboxing tech that keeps browser tabs apart — spun up in under a millisecond wherever the request landed. A traditional serverless function boots inside a VM or container, and that boot cost is real time before your code runs. Workers skip it: no machine to boot, no container to schedule, execution starts on whichever edge location the request reached. TypeScript's job here isn't stylistic. A Worker's binding surface — the other services and models it's wired to — is a contract that has to hold at every edge location at once; compile-time types catch a broken binding before it ships everywhere. Isolates are disposable by design, which is fine until a request needs to remember something. Durable Objects answer that: stateful isolates with strongly consistent in-memory storage, addressable by an ID that always routes to the same instance. The same properties that make Workers cheap for stateless HTTP make them plausible as an agent runtime — lightweight enough that running thousands of distinct agent profiles, each waking only on a webhook, is a reasonable default instead of a scaling problem. Trace one request through the stack and the hops are always the same three: isolate, Durable Object, model binding, no home region in the middle. A V8 isolate isn't a fast server. It's compute cheap enough to hand one to every agent that needs one.