AGENTIC COMMONSAI industry briefings

繁中EN

TopicAI Policy & RegulationPublished

All English articles

Exa EU Data Residency: Region-Locked Keys in Stockholm

Summary: Exa announced on November 13, 2026 that customers can now run its search inside the European Union, on the same main web index and models the US region uses, with queries, results, and page contents stored and processed in AWS Stockholm (eu-north-1). For teams whose European customers made a US-only search API a procurement blocker, this is a working endpoint today — not a waitlist — with enforcement done in code rather than in a policy PDF.

What Exa actually moved to Stockholm

This isn’t a thin proxy in front of US servers. Exa describes building “a true second home”: it replicated its main web index — petabytes of data maintained in real time across two continents — and runs API routers, vector databases, inference, rerankers, and highlights services on its own GPUs in Stockholm. Page contents are retrieved and fetched from the EU. TLS connections to api.eu.exa.ai are terminated only in EU data centers.

On day one the EU region serves the Search and Contents API endpoints, with the auto and lite search types. More search types are coming soon, and Agents, Websets, and Monitors will follow.

The failure mode is refusal, not silent fallback

The part worth copying into your own thinking: Exa enforces residency with guardrails that fail loudly.

  • Region-locked accounts. An EU team’s API key works only on the EU endpoint. A misconfigured client gets a failed request — it cannot quietly end up at the US endpoint.
  • No silent fallback. If a feature isn’t available in the EU yet, the request is refused before it’s metered, never served from another region.
  • Auditable processing. Every response carries an x-exa-processing-region: eu header, so you can verify where each request ran.
  • Zero retention by default. Every EU team runs with request content not kept at all — the same provider-side privacy posture we’ve looked at elsewhere for zero data retention on AI API calls.

One boundary to note: account and identity metadata and aggregated service metrics may still be kept outside the EU.

Getting started means pointing your client at the EU base URL:

from exa_py import Exa

exa = Exa(api_key="YOUR_EU_KEY", base_url="https://api.eu.exa.ai")
results = exa.search("EU AI Act obligations for model providers", type="auto")

EU access comes with a new EU team, set up by your Exa rep, and a team’s region is fixed at creation — which is part of how the data stays where you put it.

Quality and latency: Exa’s own numbers

Exa compared US and EU results across standard benchmarks. The largest gap it reports is on Exa Auto’s ATLAS score, at −0.028 for EU versus US; Exa Lite’s deep-search-qa (F1) was identical at 0.867 on both. Across all benchmarks the difference was no more than three percentage points. Exa also measured more than 100ms of latency saved by using the nearer EU endpoint instead of the US one.

Keep in mind whose numbers these are: they’re Exa’s own benchmarks, on its own endpoint and definitions. They’re a reason to run a comparison, not a reason to switch on their own.

Our take: If you ship an AI product to European users and data residency has been blocking Exa entirely, act now — this is usable today, the failure mode is the conservative one (refusal, never silent cross-region serving), and migration for a compatible workload is a base URL swap. But this verdict holds only for teams living within the auto and lite Search and Contents endpoints. If your stack depends on Agents, Websets, or Monitors, waiting is the right call until those ship in the EU, since unsupported requests fail outright. We’re also treating the parity claim as provisional: it rests entirely on Exa’s own benchmark runs, so diff EU and US results on your real queries before pointing production traffic at Stockholm. What would reverse the “act now” position: a parity gap you can reproduce on your own workload, or EU pricing and SLAs that diverge from the US terms — neither of which this announcement addresses. Teams with no European users can ignore this for now.

One more operational note: the region lock cuts both ways. Because a team’s region never changes, picking EU is a commitment — if your requirements later shift, you’re setting up a new team rather than flipping a flag. That friction is deliberate, and it’s the price of the guarantee.

Sources

Original post
AGENTIC COMMONSOperated by PHLEGON LABS
ShareXEmail
Support us

Related reading

  1. Exa Podcasts: Agent-Ready Audio Knowledge

    Exa indexes 3.2M podcast episodes with speaker-labeled transcripts, live in its search API at no extra cost.

    Exa

  2. Exa Places structured search data for agents

    Existing Exa users can assess place fields; its vendor-run 400-query comparison does not establish coverage in every city.

    Exa

  3. Exa Snapshot historical web search for backtesting

    Evaluation teams should use snapshots for preliminary backtests: Exa cites over 400 billion, without establishing full coverage.

    Exa