Foundations
This week's biggest agent infrastructure bets from Google, AWS, and Cloudflare all converge on one architectural insight: containment isn't a security feature bolted on later, it's the compute primitive.
Foundations
This week's biggest agent infrastructure bets from Google, AWS, and Cloudflare all converge on one architectural insight: containment isn't a security feature bolted on later, it's the compute primitive.
Why Agent Infrastructure Starts Empty
In a single week this April, Google, AWS, Cloudflare, and CIS independently shipped agent infrastructure built around the same architectural choice. None coordinated. All converged. At the same time, roughly 200,000 MCP servers sat exposed to arbitrary code execution — and the protocol's creator called it "expected behavior." Cloud infrastructure has followed the same sequence for nearly two decades: provision compute, then figure out security. Agent workloads appear to have broken that sequence. What replaced it is a different starting point entirely.
Why Agent Infrastructure Starts Empty
In a single week this April, Google, AWS, Cloudflare, and CIS independently shipped agent infrastructure built around the same architectural choice. None coordinated. All converged. At the same time, roughly 200,000 MCP servers sat exposed to arbitrary code execution — and the protocol's creator called it "expected behavior." Cloud infrastructure has followed the same sequence for nearly two decades: provision compute, then figure out security. Agent workloads appear to have broken that sequence. What replaced it is a different starting point entirely.
What Happens When the Sandbox Costs More Than the Work Inside It
A container takes hundreds of milliseconds to start and hundreds of megabytes to hold. For a web service that runs for weeks, nobody notices. But Cloudflare's rough math puts the near-term agent future at 24 million simultaneous sessions, each spawning streams of isolated tasks that live for a few milliseconds and die. At that cadence, spinning up the execution environment takes longer than the work inside it.
Infrastructure teams are used to optimizing what runs inside the sandbox. Agent workloads may be turning that assumption on its head. The choice of sandboxing primitive locks in per-unit costs before a single line of code runs.
What Happens When the Sandbox Costs More Than the Work Inside It
A container takes hundreds of milliseconds to start and hundreds of megabytes to hold. For a web service that runs for weeks, nobody notices. But Cloudflare's rough math puts the near-term agent future at 24 million simultaneous sessions, each spawning streams of isolated tasks that live for a few milliseconds and die. At that cadence, spinning up the execution environment takes longer than the work inside it.
Infrastructure teams are used to optimizing what runs inside the sandbox. Agent workloads may be turning that assumption on its head. The choice of sandboxing primitive locks in per-unit costs before a single line of code runs.
Further Reading
Past Articles
Playwright has 84,000 GitHub stars and roughly double the adoption of Selenium. By most measures, it won. So why did one...
Ninety-seven million monthly downloads. Every major lab shipping a framework. Thousands of MCP servers, most less than a...
OpenClaw's April 9 "Dreaming" update shipped a UI called the Diary Timeline. Browse it and you'll find daily notes sitti...
Docker found its seam between application and infrastructure, and that boundary turned out to be clean enough to hold ac...