LLM hosting in Germany

Which catalogue models record German, which endpoint rows record a German region, and where a request is actually processed on this deployment.

Models that record German

76 of 617 catalogue models record de in languages_strong or languages_ok: 59 as strong and 17 as usable. That is a claim about the model, not about where it runs.

A language is listed as strong only where a source claims it, and the model cards link that evidence where one exists. Without a source the claim stays unverified — Verified.

52 more in the catalogue. Filter the catalogue

Endpoints that record a German region

5 endpoint rows record a German region (de-ber, de-fra). A row is a documented deployment: it is not a claim that weights run here.

Models Inference region Runtime Processed in Retention
Devstral Small 2 (24B) de-ber mock dev-mock zero
EuroLLM-9B-Instruct (2512) de-fra mock dev-mock zero
EuroLLM-22B-Instruct (2512) de-ber mock dev-mock zero
EuroLLM-1.7B-Instruct de-fra mock dev-mock zero
Whisper large-v3 de-fra mock dev-mock zero

None of these rows is served by a real runtime. The runtimes recorded are mock, so isHostedEndpoint is false for every row. A request to one of these models is answered in region dev-mock, not in Berlin, Germany — LLM EU operated or Frankfurt, Germany — LLM EU operated.

This deployment serves through the endpoints listed below and nothing else. A model with no live endpoint is catalogue-only: it is not callable, and no region or hosting class is claimed for it.

What does not run in Germany yet

0 catalogue models have a real runtime on this deployment; 0 have the mock row only, and 292 have no endpoint at all. Of the 76 models that record German, none has an endpoint — they are catalogue entries, not hosted models.

How a German endpoint comes to exist here is in the operator documentation: Self-hosting. Which classes a region can have is defined on Hosting classes.

See also: Hosting · Residency and regions · Self-hosting · Models · Platform status · Docs