Web infrastructure giant Cloudflare is attempting to transform how enterprises deploy AI agents with the open beta release of Dynamic Workers, a new lightweight, isolate-based sandboxing system that starts in milliseconds, uses only a few megabytes of memory, and can run on the same machine ??even the same thread ??as the request that created it.
Compared with traditional Linux containers, Dynamic Workers is roughly 100x faster to start and between 10x and 100x more memory efficient. For a world where millions of users may each have one or more agents writing and executing code constantly, that difference is not incremental ??it is existential.
Cloudflare argument is direct: for consumer-scale agents, containers are too slow and too expensive. A container is fine when a workload persists. But it is a bad fit when an agent needs to run one small computation, return a result, and disappear. Developers either keep containers warm, which costs money, or tolerate cold-start delay, which hurts responsiveness.
The alternative is Dynamic Worker Loader, an API that allows one Worker to instantiate another Worker at runtime with code provided on the fly, usually by a language model. Because these dynamic Workers are built on isolates, they can be created on demand, run one snippet of code, and then be thrown away immediately afterward.
The release makes the most sense in the context of Cloudflare larger Code Mode strategy. Instead of giving an agent a long list of tools and asking it to call them one by one, give it a programming surface and let it write a short TypeScript function that performs the logic itself.
That means the model can chain calls together, filter data, manipulate files, and return only the final result ??rather than filling the context window with every intermediate step. Cloudflare says that approach cuts token usage by 81 percent on its own MCP server.
The company points to Zite as an early adopter, building an app platform where users interact through chat while the model writes TypeScript behind the scenes to build CRUD apps, connect to services like Stripe, Airtable, and Google Calendar, and run backend logic. Zite now handles millions of execution requests daily using Dynamic Workers.
Cloudflare does not pretend this is easy to secure. The company explicitly acknowledges that hardening an isolate-based sandbox is trickier than relying on hardware virtual machines.
Cloudflare response is that it has nearly a decade of experience making isolate-based multi-tenancy safe. The company points to automatic rollout of V8 security patches within hours, a custom second-layer sandbox, dynamic cordoning of tenants based on risk, and research into defenses against Spectre-style side-channel attacks.
Dynamic Workers land at a moment when AI infrastructure is becoming more opinionated. Cloudflare is taking the opposite angle ??for many workloads, the right agent runtime is not a persistent container or a tiny VM, but a fast, disposable isolate that appears instantly, executes one generated program, and vanishes.
Cloudflare is betting that this second category gets very large, very quickly. And if that happens, Dynamic Workers may prove to be more than just another Workers feature. They may define what the default execution layer for internet-scale AI agents looks like.