AI agents · AWS vs Google Cloud
Amazon Bedrock AgentCore vs Agent Runtime (formerly Agent Engine) / Agent Gateway / Agent Registry
AgentCore Gateway, Code Interpreter, and Browser split across Agent Runtime (code execution and computer use sandboxes), Agent Gateway (preview), and Agent Registry (preview).
Side-by-side comparison
| Aspect | Amazon Web Services | Google Cloud |
|---|---|---|
| Service | Amazon Bedrock AgentCore | Agent Runtime (formerly Agent Engine) Agent Gateway Preview Agent Registry Preview |
| Lifecycle | Generally available | Renamed from Vertex AI Agent Engine on Apr 22, 2026. Private Preview as of the Apr 22, 2026 release notes. Public Preview as of the Apr 22, 2026 release notes. |
| What it is | Modular agent platform. Harness (managed agent loop), Runtime, Memory, Gateway (MCP), Identity, Code Interpreter, Browser, Observability, Evaluations, Optimization, Policy, Registry, Payments. Works with any framework and any model. | Managed runtime to deploy and scale agents built with ADK or other frameworks, with Sessions, Memory Bank, code execution, and observability. Central gateway that governs how agents reach tools, models, and other agents. Catalog of agents, tools, and MCP servers for discovery and governance. |
| Pricing model | Per-component consumption (Gateway API calls and indexing, and Browser and Code Interpreter session compute). | Sandbox use is billed as part of Agent Runtime. Preview features may have no published price yet. |
| Docs | Amazon Bedrock AgentCore docs | Agent Runtime (formerly Agent Engine) docs Agent Gateway docs Agent Registry docs |
| Pricing page | Amazon Bedrock AgentCore pricing | Agent Runtime (formerly Agent Engine) pricing Agent Gateway pricing Agent Registry pricing |
Key differences
- Agent Gateway was in Private Preview and Agent Registry in Public Preview as of Apr 2026, so tool governance is less mature than AgentCore Gateway.
- ADK has built-in tools (such as Google Search grounding and code execution) and MCP support.
Pricing summary
Pricing models only. No prices are quoted because they change by region and over time.
- AWS
- Per-component consumption (Gateway API calls and indexing, and Browser and Code Interpreter session compute). Amazon Bedrock AgentCore pricing →
- GCP
- Sandbox use is billed as part of Agent Runtime. Preview features may have no published price yet. Agent Runtime (formerly Agent Engine) pricing → Agent Gateway pricing → Agent Registry pricing →
And on Azure?
Partial match Azure's equivalent is Foundry Agent Service. AWS vs Azure comparison →
Verification notes
- Agent Gateway and Agent Registry launch stages are from the Apr 22, 2026 release notes; re-check before relying on them.
FAQ
What is the Google Cloud equivalent of Amazon Bedrock AgentCore?
AgentCore Gateway, Code Interpreter, and Browser split across Agent Runtime (code execution and computer use sandboxes), Agent Gateway (preview), and Agent Registry (preview).
How does pricing compare between Amazon Bedrock AgentCore and Agent Runtime (formerly Agent Engine), Agent Gateway and Agent Registry?
AWS: Per-component consumption (Gateway API calls and indexing, and Browser and Code Interpreter session compute). Google Cloud: Sandbox use is billed as part of Agent Runtime. Preview features may have no published price yet. Check the official pricing pages for current rates.
What is the Azure equivalent?
Foundry Agent Service (partial match). AgentCore Gateway, Code Interpreter, and Browser map to the Foundry Agent Service toolbox (a managed MCP endpoint with web search, file search, code interpreter, OpenAPI, functions, and MCP tools).