Model families

Mistral.
European open weights.

For European clients, Mistral frequently resolves a conversation that has nothing to do with benchmarks: the provider is EU-domiciled, several releases carry a standard permissive licence, and the weights can run inside your own building.

Last reviewed 4 September 2026 · Engineering guidance, not legal advice.

SPECIFICATION

Provider: Mistral AI, Paris, France
Weights: Published for a substantial part of the range; some commercial models are API-only
Licence: Varies by model — several are Apache-2.0, others carry a Mistral research or commercial licence. Check the specific model card; the family is not uniform.
Sizes: From small models suited to a single accelerator up to large mixture-of-experts releases
Access paths: Mistral's own API (EU-hosted at the time of writing — confirm against the provider's current terms), Azure and other cloud catalogues, or self-hosted
Where we use it: EU data-residency deployments, and wherever an Apache-2.0 licence is a procurement requirement

Provider-published specifications as of 1 September 2026, not figures we measured. Model families move quickly — check the provider's own documentation before committing to a number.

WHERE IT FITS WELL

EU jurisdiction end to end

A French provider with EU-hosted inference means the international-transfer analysis that dominates so many European AI projects is usually far simpler — confirm the provider's sub-processor list with your DPO. That is not a capability argument, and it decides more deployments than capability does.

Apache-2.0 where it matters

Several releases carry a standard permissive licence rather than a bespoke one. For organisations whose open-source policy is written around recognised licences, that difference usually means a materially shorter review.

Efficient sizes

The mid-size models are strong relative to their footprint, which makes them a natural fit for on-premise deployments where accelerator memory is the binding constraint and a frontier-scale model is simply not going to fit.

Multilingual European coverage

Solid performance across the major European languages, which matters for any organisation whose documents are not all in English and whose evaluation set should reflect that.

THE HONEST CAVEATS

On the hardest reasoning and coding tasks, the largest frontier models still lead. Where a workload genuinely sits at that ceiling — complex multi-step agentic work, difficult code generation — you will feel the difference, and choosing Mistral there for jurisdictional reasons is a trade you should make consciously rather than discover in production.

The licence position is not uniform across the family. Assuming everything is Apache-2.0 because one well-known release is has caught out teams before. Read the model card for the specific model you intend to deploy, and record which one you chose, because that record is what a future audit will ask for.

And EU domicile is not the same as compliance. It removes the transfer question; it does not remove your obligations around lawful basis, purpose limitation, retention or subject rights. Those still need designing into the system. See GDPR and EU data residency.

QUESTIONS

QUESTIONS — 3

No. It removes the international transfer question, which is often the hardest single obstacle, but lawful basis, purpose limitation, retention, subject access and the record of processing all remain yours to design. A model provider cannot be compliant on your behalf, and any vendor implying otherwise is describing a product that does not exist.

It varies by release and it changes, so we check the model card at selection time rather than working from memory — and we write the answer into the architecture decision record, because “which licence did we deploy under” is a question that gets asked eighteen months later by someone who was not in the room.

If the licence or the EU-provider question is live, Mistral. If tooling depth and the widest possible body of operational experience matter more, Llama. On raw capability at comparable sizes they trade places release by release, which is a good reason to build the system so the model is swappable.

Keep reading

Trust

Data Residency & Sovereignty

→

Trust

GDPR & EU Data Residency

30-minute technical call · no deck