Google’s Agent Compute Engine now lets you run AI agents inside dedicated microVM sandboxes that can be paused and later resumed via checkpointing. For engineers, this means a new execution model that isolates agent code from credentials while offering built‑in state management.
Isolation via microVMs
Each agent runs in its own microVM, providing a lightweight boundary between the agent process and the host environment. The isolation reduces the risk that a compromised agent can affect other workloads or the underlying node, and it aligns with typical container‑orchestrated security postures.
Checkpointing for stateful agents
The service captures the full execution state of an agent at a checkpoint, allowing the environment to be suspended and later restored. This capability can simplify long‑running or batch‑oriented agent tasks, enable graceful upgrades, and reduce cold‑start latency when agents need to be re‑instantiated.
External secret injection
Credentials, API keys, and OAuth refresh tokens are kept outside the microVM sandbox. An external Agent Gateway authenticates inbound requests and injects the required secrets at runtime. This design separates secret storage from agent execution, which can lower the attack surface and simplify secret rotation policies.
Related CloudNinjas coverage: AI engineering.
What This Means For Practitioners
- Assess whether existing agent workloads can be migrated to microVM isolation to gain security and operational benefits.
- Plan for checkpoint integration if your agents require state persistence across restarts or upgrades.
- Review secret‑management processes to align with the external Agent Gateway model, ensuring that injection points are properly audited.
- Monitor Google Cloud announcements for any additional controls or integration points that may affect deployment pipelines.

