Residentie en regio's

Four distinct classes for ownership, operation and location. They are not interchangeable and do not confer immunity from legal disclosure obligations.

EU-eigendom, EU-beheerd: An EU company owns and operates the infrastructure in the EU. A classification, not a legal guarantee against disclosure.
EU-regio van een niet-EU-moeder: Processing in an EU region, but the parent company is outside the EU. The location is European; the jurisdiction is not exclusively so.
On-premises bij de klant: The model runs inside infrastructure the customer controls.
Catalogusvermelding, hosting niet gedocumenteerd: A catalogue entry with no LLM EU inference. Its processing location is unverified.

Deze vier labels vervangen het losse woord soeverein, dat we niet op zichzelf gebruiken. Een model wordt alleen soeverein genoemd met zijn klasse en regio ernaast, omdat eigendom, beheer en jurisdictie drie verschillende feiten zijn.

Regions in the catalogue

Region rows are configuration data, not evidence of running machines or confirmed operator contracts. Seeded endpoints use the mock: dev-mock, no model weights run. Real inference requires a configured backend per region and matching endpoints. Region configuration is not independent geolocation.

Region	Country	Class	Operator (configuration)
de-ber	DE	EU-eigendom, EU-beheerd	llmeu
de-fra	DE	EU-eigendom, EU-beheerd	llmeu
eu-owned	EU	EU-eigendom, EU-beheerd	llmeu
eu-region	EU	EU-regio van een niet-EU-moeder	hyperscaler
fr-par	FR	EU-eigendom, EU-beheerd	ovh

How to constrain it

curl https://api.llmeu.com/v1/chat/completions \
  -H "Authorization: Bearer $LLMEU_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"llmeu-auto","messages":[{"role":"user","content":"Hello"}],
       "llmeu":{"residency":"eu-owned"}}'

Alternatively, set it in the policy resolved for the request. An empty eligible endpoint set returns 409 no_endpoint_for_policy; failover does not widen it.