EU LLM residency map
One row per live endpoint: region, country code, retention state, verification date and the source behind it. It is the table that answers "where would my request actually run?" without a claim about where it should.
Three studies, each computed from the endpoint rows this deployment actually routes on — not from a survey, not from a vendor deck. Every table can be downloaded as CSV and checked against the page that prints it.
This page is written in English and German. You are reading the English text because this locale has no translation of it yet.
One row per live endpoint: region, country code, retention state, verification date and the source behind it. It is the table that answers "where would my request actually run?" without a claim about where it should.
What each provider publishes, per endpoint: residency, retention, sub-processors, a pinned version, licence, and the documentation URLs a buyer is asked for. A missing field is an absence of review or of publication, stated as such — not a verdict.
Every live endpoint that records a rate, in the recorded unit, with the display conversion, the FX rate and the inclusion rule printed above the table. A rate with no source row does not appear.
Each study is a module that reads the same rows the router and the model cards read, and each page renders those rows without a hand-typed number. The CSV is written from that same module, so the file and the page cannot drift.
A field the row does not carry is printed as an absence rather than defaulted. "Verified" means a reviewer found documentation and recorded the date; it is never a certification, and no study makes a claim about a provider's legal obligations.
They are not a market report, a benchmark of model quality, a legal opinion or a statement that any model is hosted in the EU. On this build every live endpoint is a partner broker outside the EU, and the studies say so in the same table that shows it.