What is Gemini Enterprise Agent Platform

Google's April 2026 unification of agent tooling — a four-stage lifecycle (build, scale, govern, optimize) wrapping Agent Studio/ADK, a stateful Agent Runtime, an Identity/Registry/Gateway governance stack, and native A2A + MCP interop.

Updated July 10, 2026 · §202607081949-18 ·

Gemini Enterprise Agent Platform (GEAP) is Google’s April 2026 platform for the full agent lifecycle — “build, scale, govern, and optimize agents” in Google’s own framing. It’s the umbrella that now sits over what used to be three separate stories: Vertex AI (see What is Vertex AI) as the ML platform, Agentspace (launched December 2024) as the enterprise agent product, and What is Google ADK as the code-first build framework. Agentspace was rebranded Gemini Enterprise roughly ten months after launch; this platform is the next consolidation on top of that.


The four-stage lifecycle

Everything else in this note is a component slotted into one of four named stages:

Build                Scale                 Govern                Optimize
"choose the right    "clear the path       "establish             "guarantee
 environment"          to production"        centralized control"   quality"
     │                     │                      │                    │
Agent Studio        Agent Runtime          Agent Identity        Agent Simulation
ADK                  Memory Bank            Agent Registry        Agent Evaluation
Agent Garden         Agent Sandbox          Agent Gateway         Agent Observability
                                            Semantic Gov Policies  Agent Optimizer

Build

ComponentWhat it is
Agent StudioLow-code visual canvas for designing agent reasoning loops
What is Google ADKCode-first, model-agnostic framework — “AI-native coding capabilities”
Agent GardenCurated templates (code modernization, financial analysis, invoice processing)

This is the same Agent Builder split already covered in What is Vertex AI — GEAP is the branding it now ships under.

Scale — a runtime built for long-running agents

The Agent Runtime was explicitly re-engineered to support agents that “maintain state for days at a time,” not just request/response calls. Two things make that possible:

  • Memory Bank — persistent, long-term context, functionally the same problem What is Mem0 solves standalone, except scoped to this runtime.
  • Agent Sandbox — a hardened execution environment for model-generated code, so a long-running agent can safely run code it wrote itself rather than only calling pre-registered tools.

The metered vCPU/memory pricing for this runtime layer (formerly “Agent Engine”) is detailed in What is Vertex AI rather than duplicated here.

Govern — the control plane

This is the part of GEAP that doesn’t have an equivalent in What is CrewAI or a self-hosted What is Hermes Agent setup — it’s the reason an enterprise buys the managed platform instead of assembling the pieces:

ComponentRole
Agent IdentityUnique cryptographic ID per agent — the basis for access control and audit
Agent RegistrySingle source of truth indexing every internal agent, tool, and skill — including registered MCP servers
Agent Gateway”Air traffic control” — central policy enforcement for all MCP + A2A traffic
Semantic Governance PoliciesNatural-language constraints applied to an agent’s tool calls, not just RBAC on the tool itself

Model access and discovery

  • Model Garden — first-class access to 200+ models, not just Google’s own: Gemini 3.1 Pro, Claude Opus/Sonnet/Haiku, Gemma 4, Lyria 3. Anthropic is a named first-party partner here, the same multi-model posture What is Google ADK has at the framework level.
  • Agent Gallery — the discovery surface for agents, not models: validated agents from partners including Adobe, Salesforce, ServiceNow, and Workday, browsable inside the Gemini Enterprise app.

Optimize — closing the loop

ComponentWhat it does
Agent SimulationTests agents against synthetic, human-like user interactions
Agent EvaluationContinuously scores agents against live production traffic
Agent ObservabilityFull execution traces — a real-time view into agent reasoning, not just outcomes
Agent OptimizerClusters real-world failures automatically and suggests refined system instructions

This is a superset of the evaluation harness What is Google ADK ships (criteria-based scoring, user/ environment simulation) — GEAP adds the always-on observability and auto-clustering of failures on top.

Interop: A2A + MCP as first-class traffic, not an afterthought

The Agent2Agent (A2A) protocol is Google’s open protocol so agents from different builders and platforms can discover each other, collaborate, and securely delegate tasks — the piece that lets a partner agent from Agent Gallery talk to an in-house ADK agent without custom glue code. Agent Gateway enforces policy across both A2A and MCP traffic uniformly, and Agent Registry treats MCP servers as first-class citizens alongside agents and skills. Real deployments already lean on this: L’Oréal’s Beauty Tech Agentic Platform pairs ADK with MCP; PayPal layers its own Agent Payment Protocol (AP2) on top for multi-agent commerce workflows.

Pricing shape (2026)

Platform-level meters, distinct from the Agent Runtime’s own vCPU/memory billing (see What is Vertex AI):

MeterRate
Agent Storage$0.30 / GiB-month
Agent Compute$0.085 per 3M read operations

Editions are named Standard, Plus, Frontline, and Business — the public pricing page splits entitlements across these but doesn’t fully enumerate what’s gated per tier as of this writing, so treat the edition boundary as directional until confirmed against a live quote.

Where it fits

ConcernThis note (GEAP)What is Google ADKWhat is Vertex AI
ScopeUmbrella platform: build+scale+govern+optimizeCode-first build framework onlyDeploy runtime + historical ML platform
Governance (Identity/Registry/Gateway)Native, platform-levelNone — bring your ownNot covered
Agent discoveryAgent Gallery (partner agents)N/AN/A
Multi-agent interopA2A protocol, nativeA2A client supportN/A

Why it’s on the backlog: the governance stack (Agent Identity, Agent Registry, Agent Gateway) is the piece that would actually matter if the h-aiops SRE-agent line ever needs to run multiple agents with different trust levels against ShipSolid’s production tooling — audit and policy enforcement per-agent, not just per-service-account. The A2A protocol is the other reason to watch this: it’s what would let a home-grown ADK agent interoperate with a partner-built agent from Agent Gallery without custom integration work.

Local graph

Full graph →