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.
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:REST
Call the EU host directly:cURL
Connect
Send your users to the EU Connect domain to link their accounts: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.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:Storage
Your documents, extracted text, chunks, and vector embeddings live in EU-region
Postgres and object storage.
Embeddings
Embeddings are generated by an embedding model running in-region.
LLM inference
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) is limited to models available in the
EU — choosing one that isn’t returns an error rather than routing your request
outside the region.Backups
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.
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.