See how co-designed, open systems scale AI on November 9 Every decade or so, a shift in software forces us to rethink computer architecture from first principles. After the first boom of web-scale traffic, Google pioneered warehouse-scale computing and Linux containers on Borg. This reshaped how we run internal workloads and ultimately sparked the modern cloud-native ecosystem through Kubernetes. A decade later, when deep learning models outgrew their compute and power needs, we went back to the drawing board and created Tensor Processing Units (TPUs).
And as cloud security demanded stronger, hardware-rooted guarantees, we built Titanium , a custom silicon and Infrastructure Processing Unit (IPU) architecture that offloads I/O virtualization, storage, and cryptographic trust from the host CPU. Today, we are in the middle of the next foundational shift: the transition to agentic AI that goes beyond answering questions and to taking action. Across Google, AI agents are writing and executing code, running tools, driving browsers, orchestrating enterprise workflows, and iterating on software repositories.
In a remarkably short span of time, agentic workloads have grown into one of the fastest-expanding consumers of compute and storage across our fleet. Traditional compute primitives are not built for running hundreds of millions of these agents at planet scale at the required cost and latency. A new form factor is needed, which led us to build Agent Compute Engine , a new Google Cloud service that gives every AI agent its own hardware-isolated microVM with container-speed and zero credentials held inside the sandbox.
In this blog, we discuss the problems that we encountered when trying to use existing paradigms to run agentic workloads at scale, and how we solved those foundational systems problems at every layer of the stack. The Gemini team set a simple-sounding goal. Every Gemini user would get a personal agent that runs in the cloud, remembers their work, and acts for them while they are away. To do that, each agent needed its own computer, with a filesystem, language runtimes, a browser, and network access. Around the same time, the Gemini for business team set out to let companies build agents for their employees.
