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

# License Regions

> Why and how to choose the right License Region for your application.

During the creation of your App, you must select a **License Region**. This is one of the most important architectural decisions for your project.

A License Region is a specific geographic area (e.g., `aws-us-east-1`, `aws-eu-west-1`) where WireSocket maintains a dedicated **Dashboard** presence and data storage cluster. In your JWT, this is identified by the **`dbCode`** claim.

### Why does it matter?

1. **Data Residency**: All metadata associated with your App—including billing logs, plan limits, and the **internal session routing table**—is stored in a regional database (`RegionDatabase`) within that specific geography.
2. **Latency**: For the best performance, you should select the region closest to your primary user base. This minimizes the "handshake time" when your backend requests tokens from the **Dashboard**.
3. **Regulatory Compliance**: If your project must adhere to data sovereignty laws (like GDPR in Europe), selecting the correct License Region ensures your data (metadata and usage info) never leaves that geographic boundary.

***

## Available License Regions

| Code                 | Location              |
| :------------------- | :-------------------- |
| `aws-ap-northeast-1` | Asia Pacific (Tokyo)  |
| `aws-ap-south-1`     | Asia Pacific (Mumbai) |
| `aws-eu-west-1`      | Europe (Ireland)      |
| `aws-us-east-1`      | US East (N. Virginia) |
| `aws-us-east-2`      | US East (Ohio)        |
| `aws-us-west-2`      | US West (Oregon)      |

### Can I change my region?

<Warning>
  **The License Region is a "set-once" property.** Because your App's data is
  physically provisioned in a regional database shard, it cannot be migrated to
  another region after the App is created.
</Warning>

If you need to change regions, you must create a new App and migrate your user traffic to the new credentials.