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

# Regions & Data Residency

> Choose where your data is stored and processed — United States or European Union.

Hyperspell runs as two fully independent **regions** (data-residency cells): the
default **United States** region and a **European Union** region hosted in AWS
Europe (Ireland). Each region is a separate, isolated stack on its own domains.
You choose a region when you create your account, and everything under that
account — documents, embeddings, and queries — is stored and processed in that
region.

<Note>
  Regions are isolated. An account, its API keys, and its data belong to exactly
  one region — there is no cross-region access, and data is never replicated
  between regions.
</Note>

## Endpoints

Use the endpoints for the region your account was created in.

| Service   | United States (default)          | European Union                      |
| --------- | -------------------------------- | ----------------------------------- |
| API       | `https://api.hyperspell.com`     | `https://api.eu.hyperspell.com`     |
| Dashboard | `https://app.hyperspell.com`     | `https://app.eu.hyperspell.com`     |
| Connect   | `https://connect.hyperspell.com` | `https://connect.eu.hyperspell.com` |

## Using the EU region

### SDKs

Point the client at the EU API by setting the base URL:

<CodeGroup>
  ```python Python theme={null}
  from hyperspell import Hyperspell

  client = Hyperspell(
      api_key="API_KEY",
      user_id="YOUR_USER_ID",
      base_url="https://api.eu.hyperspell.com",
  )
  ```

  ```typescript TypeScript theme={null}
  import Hyperspell from 'hyperspell';

  const client = new Hyperspell({
      apiKey: 'API_KEY',
      userID: 'YOUR_USER_ID',
      baseURL: 'https://api.eu.hyperspell.com',
  });
  ```
</CodeGroup>

### REST

Call the EU host directly:

```bash cURL theme={null}
curl -X POST "https://api.eu.hyperspell.com/memories/query" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "query": "what is a borogove?", "sources": ["vault"] }'
```

### Connect

Send your users to the EU Connect domain to link their accounts:

```html theme={null}
<a href="https://connect.eu.hyperspell.com?token=<user_token>">Connect your accounts</a>
```

<Note>
  An API key is valid only in the region it was created in. A key issued from
  `app.hyperspell.com` will not authenticate against `api.eu.hyperspell.com`, and
  vice-versa.
</Note>

## What stays in region

In the EU region, all of your **content** is stored and processed in AWS Europe
(Ireland) and never leaves the EU:

<CardGroup cols={1}>
  <Card title="Storage" icon="database">
    Your documents, extracted text, chunks, and vector embeddings live in EU-region
    Postgres and object storage.
  </Card>

  <Card title="Embeddings" icon="vector-square">
    Embeddings are generated by an embedding model running in-region.
  </Card>

  <Card title="LLM inference" icon="microchip">
    Summarization, entity extraction, and answer generation run on Amazon Bedrock
    using EU inference profiles. Hyperspell does not call any model endpoint outside
    the EU for EU-region content. Custom `answer_model` selection (see
    [Manual Integration](/core/integration)) is limited to models available in the
    EU — choosing one that isn't returns an error rather than routing your request
    outside the region.
  </Card>

  <Card title="Backups" icon="clock-rotate-left">
    Point-in-time backups of EU-region data are stored and replicated only within
    the EU (across Availability Zones in Europe (Ireland)), never to another region.
  </Card>
</CardGroup>

## Shared services

A small number of operational services are operated from the United States under
the **EU-US Data Privacy Framework**. They process account and operational
metadata — user identifiers, usage events, and error diagnostics — rather than
your stored documents and memories:

* **Authentication** (Clerk) — user identities and sign-in.
* **Error monitoring** (Sentry) — exception traces and diagnostics.
* **Product analytics** (PostHog) — usage events and identifiers.

See [Security](/concepts/security) for Hyperspell's broader security and
compliance practices.