Skip to content
Logic Tribune LT markLTLogicTribune

Public questions about intelligent systems.

Agent workflows

Google donates agent sandboxing project to CNCF

Google Cloud moves Agent Substrate to open source, aiming to isolate AI agents and save compute costs while idle.

Depth
1 outlet · newest source 94h ago
Google donates agent sandboxing project to CNCF

Key points

  • Google donated Agent Substrate to the Cloud Native Computing Foundation.
  • The project uses Kubernetes to sandbox AI agents.
  • It saves resources by snapshotting idle agents out of memory.

Google LLC donated its Agent Substrate project to the Cloud Native Computing Foundation, according to a report by SiliconANGLE AI. The open-source initiative aims to provide secure isolation for artificial intelligence agents running on existing infrastructure.The project helps companies run AI tools safely without wasting money on unused computing power.The donation introduces a Kubernetes-native approach to agent isolation and resource reclamation.

Evidence: reportedAgents may soon be the main workload, and most of the time they’re doing nothing

aifleet-siliconangle

The facts

Brandon Royal, a product manager at Google Cloud, told theCUBE that customers have requested secure and efficient agent execution for eighteen months. He stated that any agent accessing tools or browsers requires full isolation. Benjamin Elder, a staff software engineer at Google, explained that the system injects credentials on the wire rather than exposing them to the sandbox.

The facts

The architecture relies on hardened sandbox runtimes packed densely on Kubernetes clusters. All traffic passes through a policy layer that understands identity, ensuring an agent cannot reach anything it has not been explicitly granted access to. This design keeps secrets away from the agent’s direct control.

What to make of it

Security is only part of the challenge, as agents often wait for large language model responses or human input. Agent Substrate addresses this by snapshotting idle agents out of memory and CPU, storing them offline until needed. This frees resources across the cluster while maintaining the ability to restore the agent state.

In practice

Users deploying this tool operate within Kubernetes clusters with hardened sandbox runtimes. Access is controlled through a policy layer that understands identity; agents cannot reach tools or credentials without explicit grants. Availability depends on the underlying infrastructure, and the system handles credential injection on the wire to keep secrets out of the sandbox.

Why it matters

  • Users can avoid runaway compute bills by pausing idle agents instead of holding resources.
  • The open-source nature allows integration with existing Kubernetes infrastructure.
  • Credential injection on the wire reduces the risk of secrets being exposed within sandboxes.
  • Hard isolation ensures that agents driving browsers or writing code cannot escape their boundaries.

Topics: AI agents, Kubernetes, Google Cloud, open source, security

Updated

Then / now / next

Then

AI agent sandboxing was often an afterthought in enterprise deployments.

Now

Google has open-sourced Agent Substrate to provide hard walls for agent workloads.

Next

Users should watch for broader adoption and integration with other cloud-native tools.

Story timeline

  1. Then AI agent sandboxing was often an afterthought in enterprise deployments.
  2. 11 Nov 2026 Agents may soon be the main workload, and most of the time they’re doing nothing
  3. Now Google has open-sourced Agent Substrate to provide hard walls for agent workloads.
  4. Next Users should watch for broader adoption and integration with other cloud-native tools.

The strongest doubt

Counterpoint from the sources

The project assumes agents spend significant time idle, which may not apply to all workloads.

For readers

Developers

  • Must deploy agents on Kubernetes clusters with hardened sandbox runtimes.
  • Need to configure policy layers for identity and credential injection.

Business

  • Can reduce compute costs by snapshotting idle agents.
  • Should assess security requirements for agent isolation.

Investors

  • Google’s move signals growing enterprise demand for agent infrastructure.
  • Open-source adoption may lower barriers to entry for agent platforms.

Ask the article

Local keyword search of this article; no generated answers.

Did this article give you the evidence you needed?

No vote saved on this device.
Your choice stays on this device. No public tally.

Questions readers ask

Does Agent Substrate support all AI agents?

It is designed for agents that write code, run tools or drive browsers, deployed on Kubernetes.

Is the project available immediately?

Google has donated the project to the Cloud Native Computing Foundation, making it open source.

How are credentials handled?

Credentials are injected on the wire, keeping them out of the agent’s direct hands.

Connected stories

This storyMastercard executive flags data-in-use protection gap for AI agents on KubernetesMastercard executive flags data-70% plan AI agents but Oracle says security patches block production70% plan AI agents but Oracle saOpenAI partners with Hacktron to test third-party service connectionsOpenAI partners with Hacktron toOpenInference standards enable 60-minute eval pipelines for multi-turn agents via Gemini Enterprise and ADKOpenInference standards enable 6

Reading receipt

  • Google donated Agent Substrate to the Cloud Native Computing Foundation.
  • The project uses Kubernetes to sandbox AI agents.
  • It saves resources by snapshotting idle agents out of memory.

Still open: How will the project handle updates to underlying Kubernetes versions?

Still open: What specific performance overhead does the policy layer introduce?

Time spent: 0:00 · Depth: Full

Sources

  1. SiliconANGLE AI

Related stories

Background reading