AI News

GKE Agent Sandbox: Cut Agent Costs by 75%

Quick answer

GKE Agent Sandbox and Pod snapshots let you pack 3.5x more agents per node, slashing costs by 75%. Learn how orchestration beats idle waste.

In the agentic era, cloud apps are evolving from passive tools into fleets of autonomous digital workers. But as you scale, you hit a snag: AI agents work in bursts, then idle—wasting CPU and memory on static compute. The fix? Orchestration upfront. Google Kubernetes Engine (GKE) offers sophisticated tools to pack more agents onto the same node without sacrificing reliability. Google tested it, and the results are impressive: up to 75% cost reduction per agent.

Baseline: MicroVMs Hit a Wall

Running untrusted multi-agent workloads often means using microVMs (like Kata containers) for isolation. But each microVM consumes a guest OS, eating resources. On a standard GKE node (n2-standard-48), Google hit a wall at 61 OpenClaw agents before reliability dropped.

Optimization 1: GKE Agent Sandbox

Google migrated to GKE Agent Sandbox, which uses gVisor—a lightweight user-space kernel—for secure isolation without the overhead. Result: 88 agents on the same node—a 44% increase. Cost per agent dropped over 30%. No wonder usage grew 7x in four weeks after GA.

Optimization 2: Orchestration with Pod Snapshots

Idle agents are the real drain. GKE Pod snapshots freeze agents to storage, releasing resources. When a trigger arrives, they resume in milliseconds. This lets you oversubscribe compute based on workload behavior. Different agents have different needs:

  • Real-time coding assistant (latency-sensitive): Sub-second startup with warm pools.
  • Autonomous teammate (balanced): Suspend/resume on demand.
  • Headless background agent (latency-tolerant): Max oversubscription for cron jobs.

GKE handles them all simultaneously. For performance-optimized setups with warm pools, Google ran 133 agents. For cost-optimized, latency-tolerant workloads, Google hit 274 agents—over 3x the baseline—with startup times under 5 seconds.

Scale Agents, Not Budget

By combining GKE Agent Sandbox with suspend/resume, you can freeze idle agents and oversubscribe compute. For intermittent workloads, this means up to 3.5x greater density and 75% cost reduction per agent. Ready to get more out of your compute? Check the GKE Agent Sandbox docs.

Original announcement published on Google Cloud.