Agent ID Deployment
Last Modified: 2026-11-19

Agent ID Deployment

This topic covers creating and installing gateway instances, and registering the resources and agents that run behind them. The gateway sits between your agents and the tools they use, whether those are MCP servers or REST APIs: every tool call passes through it, and for each call, you control who can use a tool, which agents may act for them, and when a person must approve an action before it runs.

Deployment Model

A gateway is the unit of deployment in Agent ID. You register a gateway instance in the console (which creates an empty record with no agents, resources, or policy inherited from the tenant), then install the gateway runtime package on your own infrastructure to bring that instance online. Resources, roles, and policies are authored tenant-wide and then associated with one or more gateways. A gateway only enforces the configuration that has been published to it. For more information, see Publishing Configuration Changes.

Agent ID supports two types of gateways. Every tenant has a default gateway that is hosted by RSA, which is

generally used to reach cloud resources. You can also create a self-hosted gateway, which you deploy on a Kubernetes cluster in your own environment (on-premises or in a private cloud) to reach on-premises resources, or when you want a dedicated gateway to handle all of your traffic.

The runtime follows a control-plane/data-plane split: the RSA-hosted administration console (control plane) is where you author configuration, and each gateway runtime (data plane) is where that configuration is enforced, however it is deployed—on cloud or on-premises. A secure communication channel lets the cloud-hosted console manage and monitor an on-premises runtime without that runtime being otherwise reachable from the internet. The gateway only opens outbound connections to the console, over mutual TLS, to send status heartbeats and to retrieve published changes.

Each gateway is connected to an identity provider, which identifies the people and agents that use it.

A self-hosted gateway is made up of the gateway service, which runs as a container, and its dependencies: a PostgreSQL database, a Valkey cache, and a secret store (OpenBao). You provide the Kubernetes cluster and the networking in front of it, which generally includes an ingress controller and a certificate issuer.

Note:  Deployment target is chosen per gateway, so a single tenant can mix cloud-hosted and on-premises gateways side by side.

Next Steps: