Agent Runtime is a set of services that enables developers to deploy, manage, and scale AI agents in production. Agent Runtime handles the infrastructure to scale agents in production so you can focus on creating applications. Agent Runtime offers the following services that you can use individually or in combination:
- Runtime:
- Deploy and scale agents with a managed runtime and end-to-end management capabilities.
- Customize the agent's container image with build-time installation scripts for system dependencies.
- Use security features including VPC-SC compliance and configuration of authentication and IAM.
- Access models and tools such as function calling.
- Deploy agents built using different Python frameworks and the Agent2Agent open protocol.
- Quality and evaluation (Preview): Evaluate agent quality with the integrated Gen AI Evaluation service and optimize agents with Gemini model training runs.
- Agent Platform Sessions: Agent Platform Sessions lets you store individual interactions between users and agents, providing definitive sources for conversation context.
- Agent Platform Memory Bank: Agent Runtime Agent Platform Memory Bank lets you store and retrieve information from sessions to personalize agent interactions.
- Code Execution: Agent Runtime Code Execution lets your agent run code in a secure, isolated, and managed sandbox environment.
- Example Store (Preview): Store and dynamically retrieve few-shot examples to improve agent performance.
- Observability: Understand agent behavior with Google Cloud Trace (supporting OpenTelemetry), Cloud Monitoring, and Cloud Logging.
- Governance: Agent Runtime supports several features to help you
govern agents in production and meet your security and enterprise needs:
- Detect threats with Security Command Center: Agent Runtime Threat Detection (Preview) is a built-in service of Security Command Center that helps you detect and investigate potential attacks on agents that are deployed to Agent Runtime.
- Agent identity (Preview): Use Identity Access Management (IAM) agent identity to provide security and access management features when using agents on Agent Runtime.
- Agent Gateway (Preview): Use Agent Gateway to define rules for agentic communications and enforce security and access control policies across agents, clients, and tools connecting to and from your Google Cloud project.
Create and deploy on Agent Runtime
The workflow for building an agent on Agent Runtime is:
- Set up the environment: Set up your Google project and install the latest version of the Agent Platform SDK for Python.
- Develop an agent: Develop an agent that can be deployed on Agent Runtime.
- Deploy the agent: Deploy the agent on the Agent Runtime managed runtime.
- Use the agent: Query the agent by sending an API request.
- Manage the deployed agent: Manage and delete agents that you have deployed to Agent Runtime.
The steps are illustrated by the following diagram:
Supported frameworks
The following table describes the level of support Agent Runtime provides for various agent frameworks:
| Support level | Agent frameworks |
|---|---|
| Custom template: You can adapt a custom template to support deployment to Agent Runtime from your framework. | CrewAI, custom frameworks |
| Agent Platform SDK integration: Agent Runtime provides managed templates per framework in the Agent Platform SDK and documentation. | AG2, LlamaIndex |
| Full integration: Features are integrated to work across the framework, Agent Runtime, and broader Google Cloud ecosystem. | Agent Development Kit (ADK), LangChain, LangGraph |
Deploy in production with Agents CLI
The Agents CLI is the unified command-line interface and skill set for the Gemini Enterprise Agent Platform. It provides coding agents and developers with a predictable path through the Agent Development Lifecycle: scaffold, evaluate, deploy, publish, and observe. The Agents CLI provides the following:
- Pre-built agent templates: ReAct, RAG, multi-agent, and other templates.
- Interactive playground: Test and interact with your agent.
- Automated infrastructure: Uses Terraform for streamlined resource management.
- CI/CD pipelines: Automated deployment workflows leveraging Cloud Build.
- Observability: Built-in support for Cloud Trace and Cloud Logging.
To get started, see the Quickstart.
Use cases
To learn about Agent Runtime with end-to-end examples, see the following resources:
Click to expand use cases
| Use Case | Description | Links | |
|---|---|---|---|
| Build agents by connecting to public APIs | Convert between currencies. Create a function that connects to a currency exchange app, allowing the model to provide accurate answers to queries such as "What's the exchange rate for euros to dollars today?" |
Agent Platform SDK (Python) notebook - Intro to Building and Deploying an Agent with Agent Runtime | |
| Designing a community solar project. Identify potential locations, look up relevant government offices and suppliers, and review satellite images and solar potential of regions and buildings to find the optimal location to install your solar panels. |
Agent Platform SDK (Python) notebook - Building and Deploying a Google Maps API Agent with Agent Runtime | ||
| Build agents by connecting to databases | Integration with AlloyDB and Cloud SQL for PostgreSQL. | Blog post - Announcing LangChain on Gemini Enterprise Agent Platform for AlloyDB and Cloud SQL for PostgreSQL Agent Platform SDK (Python) notebook - Deploying a RAG Application with Cloud SQL for PostgreSQL to Agent Runtime Agent Platform SDK (Python) notebook - Deploying a RAG Application with AlloyDB for PostgreSQL to Agent Runtime |
|
| Build agents with tools that access data in your database. | Agent Platform SDK (Python) notebook - Deploying an Agent with Agent Runtime and MCP Toolbox for Databases | ||
| Query and understand structured datastores using natural language. | Agent Platform SDK (Python) notebook - Building a Conversational Search Agent with Agent Runtime and RAG on Agent Search | ||
| Query and understand graph databases using natural language | Blog post - GenAI GraphRAG and AI agents using Agent Runtime with LangChain and Neo4j | ||
| Query and understand vector stores using natural language | Blog post - Simplify GenAI RAG with MongoDB Atlas and Agent Runtime | ||
| Build agents with Agent Development Kit | Build and deploy agents using Agent Development Kit. | Agent Development Kit -- Deploy to Agent Runtime | |
| Build agents with OSS frameworks | Build and deploy agents using the OneTwo open-source framework. | Blog post - OneTwo and Agent Runtime: exploring advanced AI agent development on Google Cloud | |
| Build and deploy agents using the LangGraph open-source framework. | Agent Platform SDK (Python) notebook - Building and Deploying a LangGraph Application with Agent Runtime | ||
| Debugging and optimizing agents | Build and trace agents using OpenTelemetry and Cloud Trace. | Agent Platform SDK (Python) notebook - Debugging and Optimizing Agents: A Guide to Tracing in Agent Runtime | |
| Build multi-agent systems with A2A protocol (preview) | Build interoperable agents that communicate and collaborate with other agents regardless of their framework. | For more information, see the A2A protocol documentation. | |
Enterprise security
Agent Runtime supports several features to help you meet enterprise security requirements, adhere to your organization's security policies, and follow security best practices. The following features are supported:
VPC Service Controls: Agent Runtime supports VPC Service Controls to strengthen data security and mitigate the risks of data exfiltration. When VPC Service Controls is configured, the deployed agent retains secure access to Google APIs and services, such as BigQuery API, Cloud SQL Admin API, and Agent Platform API, verifying seamless operation within your defined perimeter. Critically, VPC Service Controls effectively blocks all public internet access, confining data movement to your authorized network boundaries and significantly enhancing your enterprise security posture.
VPC Service Controls isn't supported with Agent Gateway. However, you can use custom organization policy constraints to restrict which gateways can be associated with your agents. For more information, see Route traffic through Agent Gateway.
Private Service Connect interface: For Agent Runtime, PSC-I lets your agents interact with privately hosted services in a user's VPC. For more information, see Using Private Service Connect interface with Agent Runtime.
Customer-managed encryption keys (CMEK): Agent Runtime supports CMEK to protect your data with your own encryption keys, which gives you ownership and full control of the keys that protect your data at rest in Google Cloud. For more information, see Agent Runtime CMEK.
Data residency (DRZ): Agent Runtime supports Data residency (DRZ) to ensure that all data at rest are stored within the specified region.
HIPAA: As a part of Agent Platform, Agent Runtime supports HIPAA workloads.
Access Transparency: Access Transparency provides you with logs that capture the actions Google personnel take when accessing your content. For more information about how to enable Access Transparency for Agent Runtime, see Access Transparency in Agent Platform.
The following table shows which enterprise security features are supported for each Agent Platform service:
| Security feature | Agent Runtime | Sessions | Memory Bank | Example Store | Code Execution |
|---|---|---|---|---|---|
| VPC Service Controls | Yes | Yes | Yes | No | Yes |
| Customer-managed encryption keys | Yes | Yes | Yes | No | Yes |
| Data residency (DRZ) at rest | Yes | Yes | Yes | No | Yes |
| HIPAA | Yes | Yes | Yes | Yes | Yes |
| Access Transparency | Yes | Yes | Yes | No | No |
| Access Approval | Yes | Yes | Yes | No | No |
Supported regions
See Locations for a list of supported regions for Agent Runtime.
Quota
See Quota and system limits for Agent Runtime quota information.
Pricing
A free tier is available for Agent Runtime. For information about pricing for Agent Runtime, see Gemini Enterprise Agent Platform pricing.
Migration to the client-based SDK
The agent_engines module within the Agent Platform SDK is being refactored to a
client-based design for the following key reasons:
- To align with the Agent Development Kit (ADK) and Google Gen AI SDK in canonical type representations. This ensures a consistent and standardized way of representing data types across different SDKs, which simplifies interoperability and reduces conversion overhead.
- For client-level scoping of Google Cloud parameters in multi-project multi-location applications. This allows an application to manage interactions with resources across different Google Cloud projects and geographical locations by configuring each client instance with its specific project and location settings.
- To improve discoverability and cohesiveness of Agent Runtime services