# Data plane installation

> Install the Agent Router data plane, the Controller and gateway, into a Kubernetes cluster and connect it to the management plane.

# Data plane installation

  The data plane is a Kubernetes deployment containing the Controller and the Agent Router. This step installs those components in the target cluster and connects them to the management plane. Select the guide that matches the target cloud platform and preferred installation tooling.

Select a guide

  
    Azure · AKS · tare CLI
    Azure using tare CLI
    Install on Azure Kubernetes Service using the tare CLI. The recommended path for AKS deployments when the tare CLI is available in the environment.
    <Link to="/agent-router-enterprise/self-hosted-data-plane/data-plane-installation/installation-guide-az/" className="tare-card-link">Azure installation guide →</Link>
  
  
    Azure · AKS · Helm
    Azure using Helm
    Install on Azure Kubernetes Service using Helm and a private container registry such as Azure Container Registry. Use this guide when a private registry is required by the environment.
    <Link to="/agent-router-enterprise/self-hosted-data-plane/data-plane-installation/installation-guide-az-helm/" className="tare-card-link">Azure Helm guide →</Link>
  
  
    AWS · EKS · tare CLI
    AWS using tare CLI
    Install on Amazon Elastic Kubernetes Service using the tare CLI.
    <Link to="/agent-router-enterprise/self-hosted-data-plane/data-plane-installation/installation-guide-aws/" className="tare-card-link">AWS installation guide →</Link>
  
  
    GCP · GKE · tare CLI
    GCP using tare CLI
    Install on Google Kubernetes Engine using the tare CLI.
    <Link to="/agent-router-enterprise/self-hosted-data-plane/data-plane-installation/installation-guide-gcp/" className="tare-card-link">GCP installation guide →</Link>
  
  
    Any cloud · Helm
    Helm (cloud-agnostic)
    Helm-based installation for platform teams that own the Helm release lifecycle and maintain a private container registry such as Harbor, JFrog Artifactory, Nexus, or Google Artifact Registry.
    <Link to="/agent-router-enterprise/self-hosted-data-plane/data-plane-installation/installation-guide-helm/" className="tare-card-link">Helm installation guide →</Link>
  

Before you begin

All data plane guides assume the following steps are already complete:

- [Prerequisites](/agent-router-enterprise/self-hosted-data-plane/prerequisites/) confirmed: access, accounts, cloud quotas, and network rules.
- [Management plane onboarding](/agent-router-enterprise/self-hosted-data-plane/onboarding/) complete through Step 5: organization details, providers, models, and the data plane credential (`service-account.json`).
- Target Kubernetes cluster provisioned and meeting the [Kubernetes version requirement](/agent-router-enterprise/self-hosted-data-plane/prerequisites/#kubernetes-requirements). Cluster provisioning is not covered by Tetrate support.

SSO is **not** required before data plane installation. Configure SSO after the gateway is running and before opening the Console to developers — see [SSO configuration](/agent-router-enterprise/guides/identity-and-access-management/single-sign-on/sso-configuration-guide/).

After installation

  <Link to="/agent-router-enterprise/self-hosted-data-plane/gateway-installation/gateway-installation-guide/" className="tare-nav-card">
    Gateway installation
    Next step: install the data plane gateway components that manage inbound access and configure request routing.
  </Link>
  <Link to="/agent-router-enterprise/guides/identity-and-access-management/single-sign-on/sso-configuration-guide/" className="tare-nav-card">
    SSO configuration
    After the gateway is running, connect an OIDC identity provider before developer handoff.
  </Link>
  <Link to="/agent-router-service/quickstarts/quickstart-console/" className="tare-nav-card">
    Console quickstart
    Once SSO is working and the gateway is reachable, issue an API key and make a first routed request from the Console.
  </Link>