> For the complete documentation index, see [llms.txt](https://docs.enapi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enapi.com/getting-started/pick-your-region.md).

# Pick your region

ENAPI runs in more than one region.

A region is a complete, independent ENAPI platform — its own infrastructure, its own database, its own partner directory. Choosing a region decides two things at once: where your data is stored and processed, and which counterparties you can roam with.

You pick your region once, when you create your account. Everything after that — your handshake, your agreements, your CDRs — happens inside it.

**The regions**

| Region        | Portal           | OCPI base URL        | Data stored and processed in |
| ------------- | ---------------- | -------------------- | ---------------------------- |
| Europe        | app.enapi.com    | OCPI base URL        | European Union               |
| North America | app.us.enapi.com | roaming.us.enapi.com | United States                |

Europe and North America are the two regions available today. If you need a region that isn't listed, talk to your account manager before you start onboarding.

**What "region" actually means**

Each region is a separate deployment of the whole platform, not a setting inside one platform. In practice:

* Your account and organization live in one region. So do your users, your party IDs, and your OCPI platform configuration.
* Handshakes are per region. The Versions URL and ENAPI party ID you exchange are the ones shown in that region's handshake wizard. A handshake performed in Europe does not exist in North America.
* The roaming directory shows that region only. You discover, offer to, and sign with counterparties onboarded to the same region as you.
* Agreements, tariffs, sessions, CDRs and clearing stay in region. Nothing is copied between regions.

{% hint style="info" %}
Cross-region roaming isn't available. A party in Europe cannot roam with a party in North America. If you need to trade in both, you onboard to both — see [Operating in both regions](https://docs.google.com/document/d/1J3atEwzDpV5W9nTrUC1MGlTN-AsPrlOiXtZSNdQqE-M/edit#operating-in-both-regions). 
{% endhint %}

**Which region should you choose?**

1. Where does your data have to live? If you have a contractual or regulatory requirement that charging data is stored and processed on US soil, choose North America. If your requirement is the EU, choose Europe. See [Compliance and Data Residency](about:blank).
2. Where are the counterparties you want to roam with? This is the one partners most often get wrong. The directory you see is the directory of your region — a North American CPO onboarded to Europe will not find US eMSPs there.

For almost everyone the answer is simply: the region where your charge points or your drivers are.

**One caveat:** for partners operating in Australia and New Zealand, please select “Europe’. As we scale we will build new interfaces and data residencies. At present, these partners are surfaced in, and stored in, our European instance. 

**Choosing your region when you register**

The registration form asks which region you want your account created in. Pick Europe or North America and your organization is created there.

{% hint style="info" %}
Make sure you're on the right registration form: the Region switcher at the top of the login screen takes you to the registration form for that region. Registering from the Europe screen creates a European account, whichever region you had in mind. 
{% endhint %}

If you pick the wrong region, contact support before you go any further. Moving an organization between regions is a manual operation, and it's far cheaper to do before you've run a handshake, signed agreements, or started clearing CDRs.

**Switching region at login**

The login screen carries a Region switcher — plain text labels, no flags. It does two things:

* It tells you where you are. The portals look identical; the switcher is how you know whether you're looking at Europe or North America.
* It takes you to the other region's login and registration screens.

Your user belongs to one region. If you sign in from the other region's login screen, you're sent to your own region's portal — the switcher changes which screen you're on, not which region your account is in.

**Operating in both regions**

Some partners trade in both Europe and North America. That's supported, with one caveat: the two are separate platforms, so you run two of everything.

* An organization in each region, each with its own users and login.
* A handshake in each region, against that region's OCPI base URL.
* Agreements signed and managed per region.

Data doesn't overlap and the two accounts don't interfere with each other. Use a separate login for each region — one user cannot hold both.

{% hint style="info" %}
Planning to run in both regions? Tell your account manager at the start. Party IDs, contacts and contract templates are easier to keep aligned if both organizations are set up together. 
{% endhint %}

**Regions and data residency**

Region is the partner-facing control for data residency: Europe keeps your data in the European Union, North America keeps it in the United States. The compliance detail — GDPR roles, data minimization, certification status — is on [Compliance and Data Residency](/security-compliance-and-slas/compliance-and-data-residency.md).

**Next**

* Create your account in the right region → [Onboarding to ENAPI](/getting-started/onboarding-to-enapi.md)
* Run your handshake against your region's endpoints → [Set up your OCPI Handshake with ENAPI](/getting-started/set-up-your-ocpi-handshake-with-enapi.md)
* Understand where your data is held → [Compliance and Data Residency](/security-compliance-and-slas/compliance-and-data-residency.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.enapi.com/getting-started/pick-your-region.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.