Regions

The cloud API runs in three regions. Each one is a separate deployment with its own database, and your documents are parsed in the region you send them to.

All three run the same API. Only the host changes.

Use the region you signed up in

Your account, your organizations, your credits and your API keys are rows in one region's database. They are not copied to the others. So:

• A key created in Europe authenticates against the Europe host and nowhere else.
• Credits bought in Europe are spent in Europe.
• Signing in to the console on one host does not sign you in on another.

A key used against the wrong host is answered 401 unauthorized. The other region has genuinely never seen it, so the answer is the same as for a key that does not exist. If a key you are sure about returns 401, check the host first.

You can hold accounts in more than one region. They are separate accounts that happen to share your email address, each with its own keys and its own credits.

Picking a region

If you are signing up now, pick the region closest to the people you parse for, or the one your data residency rules require. Parsing happens in that region: nothing is stored afterwards, but the document is read there.

If you already have an account, you are already in a region: it is the host you sign in to. Accounts are not copied between regions, so signing up on a second host gives you a second account rather than a second door into the first one.

Self-hosted has no regions

The container runs wherever you run it, and no document leaves it. A trial license is minted by one region's console, and the license itself is a signed token that the container verifies offline, so the region that issued it does not matter afterwards. See Self-hosted.