> ## Documentation Index
> Fetch the complete documentation index at: https://docs.corti.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Environments & Tenants

> Learn how Corti environments and tenants work, and how they affect authentication and data residency.

## Environments

Corti operates separate regional environments. Your environment determines where data is stored and which API endpoints you use. It also defines which identity provider you authenticate against.

Available environments:

| Environment | Region            | Base API URL               | Auth Base URL               |
| ----------- | ----------------- | -------------------------- | --------------------------- |
| `eu`        | Azure West Europe | `https://api.eu.corti.app` | `https://auth.eu.corti.app` |
| `us`        | Azure US East     | `https://api.us.corti.app` | `https://auth.us.corti.app` |

Your API client must authenticate against the correct environment. Tokens from one region cannot be used in another. When you create a client in the console, you can pick your preferred environment.

## Tenants

A tenant represents a shared identity realm for Corti API customers. All API customers operate inside the shared tenant named `base`. This keeps authentication consistent while maintaining strict segregation of customer data at the application layer.

You include the tenant name in the authentication URL or in headers when interacting with certain APIs. For most customers, this will always be: `Tenant-Name: "base"`

Bespoke private tenants are available only for specific enterprise or regulatory scenarios that require full isolation at the identity realm level. These cases are rare and need a dedicated review. If you believe your organisation needs its own tenant, speak with your Corti representative.