Skip to main content
Atlan Agent Registry is a multi-tenant SaaS platform hosted on AWS and operated by Atlan. This page shows the planes it is built from, the trust boundaries between them, and the path a request takes. It is written for a reviewer with no access to Atlan’s internal systems. Agent Registry architecture: humans and agents reach a global edge, which routes sign-in to a global control plane and requests to a regional context plane; only the context plane reads and writes the regional data plane

​
How a request travels

  1. Sign in. People sign in through your identity provider using enterprise SSO. Agents, CLIs and integrations use API keys or OAuth clients. The platform issues short-lived tokens; Atlan never sees your identity-provider password.
  2. Scope to one organization. The Registry pins every request to one organization and one workspace before doing any work. There is no query path that crosses organizations.
  3. Read and write through one path. Only the context plane can reach the data plane. Your context is stored encrypted at rest and isolated per organization.
  4. Stay in your region. The context plane and data plane are deployed per region. Your context does not leave the region your organization runs in.

​
The three planes

The planes run in separate AWS accounts. The context plane is the only plane with a network path to the data plane.

​
Where your data lives

Everything your organization registers lives in the regional data plane. All four are encrypted at rest with keys held in the owning AWS account. Data in transit between your clients and the platform, and between the platform and the relational database, is encrypted with TLS. Traffic inside the data plane’s private network is bounded by network controls.

​
Trust boundaries

  • One public entry. Humans and agents reach the platform through a global edge network. The edge is the only internet-facing entry point; databases, Kubernetes APIs and administrative tooling are not reachable from the internet.
  • Planes in separate accounts. Control, context and data planes are isolated AWS accounts with no shared credentials. Only the context plane holds a path to the data plane.
  • Federated identity everywhere. People, pipelines and workloads use short-lived federated credentials. No long-lived cloud access keys exist on the platform.
  • Staff access is time-boxed. Atlan engineers have no standing write access to production and cannot read customer data by default. Elevated access is approved per task, expires within hours, and is logged to an immutable audit trail.

​
Deployment options

​
What this page does not cover

Internal network topology, account identifiers, address ranges and operational tooling are intentionally omitted. For the detailed security overview, sub-processor list, encryption standards and questionnaire answers, contact your Atlan account team.