Providers

Every Melious inference request runs on one of our provider partners. They're all in Europe, by construction — we don't have US or APAC fallbacks, and we won't add them.

The list

Eight partners across six countries, last we counted. Some requests also run on capacity Melious operates itself; it shows up as provider_id: "melious" in environment_impact. The live partner list — including which models each one runs and their current PUE — is on melious.ai under Providers.

Data residency

Your request body and the response never leave the EU — we don't mirror traffic to a non-EU region, and no provider on the list trains on your traffic. The full data-handling picture, including what we log and what we don't, is in Privacy and data residency.

If you need a guarantee narrower than "EU" — "only providers in Germany", say — tell us.

How routing picks between them

Use a routing flavor to express a preference for speed, price, or greener power.

PUE, power, and why it shows up in responses

Each provider reports a Power Usage Effectiveness (PUE) — total facility energy divided by energy actually delivered to the compute. Lower is better; 1.0 is the theoretical floor. PUE feeds into our environment_impact.energy_kwh calculation.

We publish each provider's PUE alongside their listing on the website, and it also appears as environment_impact.pue on the responses that carry the block — Chat completions, embeddings, and rerank. If a provider changes hardware or cooling, that number shifts — we don't hardcode it.

When a provider isn't on the list

We've got eight providers live today. If the one you need isn't on the list, tell us — we'll see what we can do. The bar is:

1. EU infrastructure, no US or APAC fallback.
2. No training on customer traffic.
3. Open-weight models only.

If all three hold, we're probably already talking to them.

Related

Environmental impact walks through what the per-response metrics mean and how they're computed. Routing covers the flavors you'll use to steer selection.