Multi-Region Support

Descope allows you to create projects across multiple regions. When creating a Descope Project, user data and all project configurations will only be stored and maintained within the region that the project resides in. Once a region has been selected during project creation, all user and tenant data cannot be moved between regions.

Currently Supported Regions

When on a Descope Growth or Enterprise plan, you can select which region to store the data when creating a new project.

Descope currently supports data residency in the following regions:

Data Centers

Descope leverages AWS data centers across the supported regions for the secure storage and processing of project and user information. Our data practices strictly adhere to all major regulatory requirements, ensuring confidentiality, integrity, and compliance at all times.

Descope Base URLs

A Descope base URL is the scheme and host used for API, OAuth, and Flow traffic—for example https://api.descope.com or https://auth.yourcompany.com. It does not include a path.

When SDKs Resolve the Host Automatically

For standard Descope projects on our public regional hosts, Descope SDKs derive the correct regional API base URL from your Project ID. You typically do not need to set baseUrl just to hit the right US/EU/AU/CA endpoint.

When You Must Set the Base URL Explicitly

The base URL does matter, and you must configure it in your app, when:

• You use a custom domain for your project (your own hostname replaces the default api.*.descope.com host for clients and flows), or
• You use a Private Cloud Descope environment (i.e. a "star" environment).

In those cases the SDK cannot infer the correct host from the Project ID alone. Set baseUrl (and where applicable baseStaticUrl, per the client SDK or your stack’s equivalent) to your custom or environment-specific hostname. Use the hostname from Customer Success, or derive the scheme and host from the OpenID Connect discovery URL on the default Federated application in the Console.

Federated Application Issuer and Discovery URLs

When configuring an Federated application in the console, issuer and discovery URLs follow your environment's base URL (regional defaults, custom domain, or private cloud).

They use the same hosts as described above and can be reviewed in your application settings.

Descope APIs

If you're unsure about the correct base URL to use, you can look at the base URL set for your federated application settings.

Default Regional API Hosts

For projects without a custom domain, each region has a fixed API host. Use this host for manual API requests and for understanding where traffic is routed.

When using Descope Services with our APIs directly, all requests must use the baseURL that matches your project's region and deployment type (public regional host, custom domain, or private cloud).

For regional CNAME targets used when configuring a custom domain in DNS, see Create a DNS Record in the Custom Domain guide.