# Manage multiple gateways on a data plane

> Review and operate the gateways a single Tetrate Agent Router data plane provisions and manages, including their URLs, owning projects, config versions, and health.

Enterprise Tier

  A data plane is shared provisioning capacity: one data plane can provision and manage many gateways at once, each serving a single project. This guide covers operating that shared capacity: reviewing the gateways a data plane manages, placing more projects on it so their gateways are auto-provisioned, and understanding how the data plane reconciles each one independently.

Each gateway on a data plane has its own customer-facing URL and serves exactly one project, so a request to a gateway URL always resolves to a single project's configuration. The data plane provisions the runtime for each gateway and keeps it aligned with the desired configuration the management plane publishes. Because gateways are reconciled independently, they can be added, changed, and recovered without affecting one another.

**Persona:** Platform operator with data-plane operations access, working in the Admin Dashboard.

**Estimated time:** 10 to 15 minutes.

## Outcomes

By the end of this guide:

- The gateways a data plane manages can be reviewed, with their URL, owning project, configuration version, and health.
- Additional gateways appear on the data plane when more projects select it.
- The independence of gateway reconciliation is understood: one gateway's problem does not block the others.

## Prerequisites

- Administrator access to the Admin Dashboard, with data-plane operations permissions.
- A data plane deployed and registered. See [Deploy and register a data plane](/agent-router-enterprise/guides/operate-and-govern/project-and-data-plane-management/deploy-a-data-plane/).

## Step 1: Review the gateways a data plane manages

1. In the Admin Dashboard, open **Data planes** and select the data plane.
1. Review the gateways it manages. For each gateway, the view shows the customer-facing URL, the owning project, the configuration version applied, and the gateway's health.

The management plane tracks whether the desired configuration version is applied per gateway, so a gateway that has not yet caught up with a recent change is visible as such.

## Step 2: Assign more gateways to the data plane

Gateways appear on a data plane when their projects select that data plane. There is no top-level **Gateways** menu for creating gateways separately, and gateways are not created on the data plane directly.

1. On a project, select this data plane so its gateway is auto-provisioned here, following [Provision a gateway for a project](/agent-router-enterprise/guides/operate-and-govern/project-and-data-plane-management/provision-a-gateway/).
1. Confirm the new gateway appears among those the data plane manages.

A single data plane can host many projects' gateways this way, which is how several teams share one deployment while each keeps its own isolated endpoint.

## Step 3: Understand independent reconciliation

The data plane reconciles each gateway on its own.

1. Note that a failure affecting one gateway's assignment does not block the other gateways the data plane manages.
1. Use the per-gateway health and configuration-version indicators to isolate a problem to a single gateway rather than the whole data plane.

Spreading traffic across several data planes, rather than several gateways on one, is covered in [Load balance across regional deployments](/agent-router-enterprise/guides/operate-and-govern/load-balance-across-regional-deployments/). That pattern is about capacity and backends across regions. Separately, when a **single project** optionally attaches several like-configured gateways for high availability behind customer-managed DNS, see [Gateway sets and DNS-level failover](/agent-router-enterprise/guides/operate-and-govern/project-and-data-plane-management/gateway-sets-and-dns-failover/) — that is not the same as many projects sharing one data plane.

## What to do next

- **Understand guardrail enforcement on shared capacity**: when several projects' gateways share one data plane, each project's guardrails apply only to its own traffic, and gateway attachment health determines what is enforced. See [Guardrails on shared data planes](/agent-router-enterprise/guides/operate-and-govern/safety-and-data-protection/guardrails-on-shared-data-planes/).
- **Migrate a gateway or upgrade its runtime**: move a gateway to another data plane, or upgrade it in place, without changing its URL. See [Migrate a gateway or upgrade its runtime](/agent-router-enterprise/guides/operate-and-govern/project-and-data-plane-management/migrate-a-gateway/).
- **Plan high availability and disaster recovery**: topology and recovery planning across data planes. See [Plan high availability and disaster recovery](/agent-router-enterprise/guides/operate-and-govern/plan-high-availability-and-disaster-recovery/).
- **Optional: gateway sets and DNS-level failover**: attach additional members to one project for DNS failover. See [Gateway sets and DNS-level failover](/agent-router-enterprise/guides/operate-and-govern/project-and-data-plane-management/gateway-sets-and-dns-failover/).

Where to go next

  <Link to="/agent-router-enterprise/guides/operate-and-govern/project-and-data-plane-management/migrate-a-gateway/" className="tare-nav-card">
    Migrate a gateway or upgrade its runtime
    Move a gateway between data planes, or upgrade in place, with a stable URL.
  </Link>
  <Link to="/agent-router-enterprise/guides/operate-and-govern/project-and-data-plane-management/gateway-sets-and-dns-failover/" className="tare-nav-card">
    Gateway sets and DNS-level failover
    Optional Enterprise HA for several members of the same project.
  </Link>