Exa announcement graphic with the words Exa Search, now in the EU next to a grey globe on which Europe is highlighted in blue
Exa (Blog, 13.11.2026)

News

Exa moves AI web search into the EU, data in Stockholm

Since 13.11.2026 Exa processes search queries, results and page contents for enterprise customers in AWS Stockholm, refuses requests it cannot serve there and keeps no request content by default.

By Nova 5 min read

Key takeaways

  • Exa's Search and Contents API run in AWS Stockholm since 13.11.2026, with the auto and lite search types.
  • EU keys work only on api.eu.exa.ai, and requests that cannot be served in the EU are refused instead of sent to the US.
  • EU teams keep no request content by default, but account metadata and aggregated metrics may stay outside the EU.
  • Exa remains a US company, so data processing agreements and transfer assessments still need checking.
On this page
  1. What exactly did Exa launch?
  2. How does Exa enforce EU data residency?
  3. Is the EU version as good as the US one?
  4. Why does this matter for companies in Europe?
  5. How has the launch been received?
  6. What should teams in Luxembourg check now?

Since 13.11.2026 the US search provider Exa lets enterprise customers run its web search for AI applications entirely inside the EU: queries, results and page contents are stored and processed in AWS Stockholm, and requests that cannot be served there are refused rather than sent to the US.

For European companies that build AI agents or chatbots on top of a web search API, that removes one of the most common objections in data protection and procurement reviews. It does not remove all of them, and Exa says so itself.

What exactly did Exa launch?

In its announcement of 13.11.2026 Exa says it has replicated its main web index into the EU, "petabytes of data, maintained in real time across two continents". API routers, vector databases, inference, rerankers and highlights run on Exa's own GPUs in Stockholm (AWS region eu-north-1), and page contents are fetched through EU endpoints. Customers reach the region through a separate endpoint, api.eu.exa.ai.

The first release is limited. The EU region serves the Search and Contents API endpoints with the "auto" and "lite" search types. More search types are to follow, and Exa's Agents, Websets and Monitors products will come later, without a date. According to Exa's post on X, the region is available to enterprise customers; access requires a new EU team set up by an Exa sales representative.

How does Exa enforce EU data residency?

Exa describes four mechanisms on its blog and on its EU data residency page. Accounts are region locked: an EU team's API key works only on the EU endpoint and is refused everywhere else, so a misconfigured client fails instead of quietly switching to the US. Features that are not yet available in the EU are refused before the request is metered. Every response carries the header x-exa-processing-region: eu, so customers can audit where a request was processed. And every EU team runs with zero data retention by default, meaning request content is not stored at all.

Exa also states the limit of the promise: "Account and identity metadata and aggregated service metrics may be kept outside the EU." A team's region is fixed when the team is created and cannot be changed later.

A woman stands with a laptop at an open server rack in a data centre aisle while a colleague works nearby
Symbolic image of a data centre, not Exa's Stockholm site: Exa runs its EU search stack in AWS region eu-north-1 | Image: Gorodenkoff/Shutterstock.com

Weekly, Thursday morning, Central European Time.

The Thinking briefing

One email a week: what changed in European business software, which prices moved, and which comparison we published. No sales mail.

Is the EU version as good as the US one?

Exa published benchmark comparisons between the two regions. On four tests, including deep-search-qa, ATLAS, live-browsecomp and finsearchcomp, the scores differed by no more than three percentage points; the largest gap was 2,8 points on ATLAS in "auto" mode, in favour of the US. For users in Europe, the nearer endpoint cut latency by more than 100 milliseconds, according to Exa. These are the provider's own measurements and have not been independently verified.

Why does this matter for companies in Europe?

Web search APIs are a building block of many AI products: an agent or assistant sends the user's question to the search service and feeds the results back into a language model. The query often contains customer names, internal project details or personal data. Under the GDPR, sending such data to a country outside the European Economic Area is a transfer that needs an adequacy decision, appropriate safeguards or a derogation, as the Luxembourg data protection authority CNPD explains in its guidance on international transfers. Exa itself writes that companies with customers in Europe "often can't send queries to a US service", because of GDPR residency requirements or internal rules from procurement, security and compliance teams, and that a significant portion of its API traffic already comes from Europe.

Processing in Stockholm with zero retention narrows the question considerably. It does not make it disappear. Exa remains a US company, Exa Labs Inc. in San Francisco according to its privacy policy, and account metadata may still leave the EU. How US access laws interact with data stored in Europe by US providers was assessed in 2019 by the EDPB and the EDPS in their joint response on the US CLOUD Act. Companies should therefore still check the data processing agreement, the list of subprocessors and the metadata exception, and record the result in their own transfer assessment.

How has the launch been received?

Exa's announcement on X reached more than 25.000 views by the morning of 14.11.2026. Specialist outlets such as AlphaSignal and the German site mindprio picked it up, the latter concluding that it is progress but no free pass and that case by case checks remain necessary. We found no coverage in major business media by then.

What should teams in Luxembourg check now?

Teams that already use Exa should know that switching requires a new EU team and new keys; existing US teams are not converted. Anyone comparing providers can use the same questions as for other AI services: where is the data processed, what is retained, which metadata leaves the EU, and who is the contracting party. Our guide to AI email and the GDPR applies the same checklist to mail tools, and our comparison of Mistral Le Chat and ChatGPT shows how European and US providers handle data residency. The political debate about dependence on non-European cloud providers is covered in our report on the Cloud and AI Development Act.

Sources

Every price and fact above was checked against these pages on the date shown.

  1. [1] Exa Blog, Exa Search, now in the EU (13.11.2026) accessed 2026-11-14
  2. [2] Exa, EU Data Residency accessed 2026-11-14
  3. [3] Exa on X, Exa now runs in Europe accessed 2026-11-14
  4. [4] Exa Privacy Policy accessed 2026-11-14
  5. [5] CNPD, Transferts internationaux de données personnelles accessed 2026-11-14
  6. [6] EDPB-EDPS Joint Response to the LIBE Committee on the impact of the US Cloud Act accessed 2026-11-14
  7. [7] AlphaSignal, Exa Launches EU-Hosted AI Search in Stockholm accessed 2026-11-14
  8. [8] mindprio, KI-Websuche mit Daten in Schweden accessed 2026-11-14
Topics Exasearch APIEU data residencyGDPRAI agentsStockholm