skip to content

Which Mistral models are Apache-2.0 and which need a commercial licence?

level: middleimportance: must knowfreq 66%

answer

  1. two tracks, not one catalogue
  2. permissive for the small models
  3. flagship weights are look-but-don't-ship
  4. three licence names, one API-only tier
  5. Apache 2.0 vs MRL vs MNPL

basics

~20 s

Mistral runs two licence tracks. Apache-2.0 releases — Mistral 7B, Mixtral 8x7B and 8x22B, Mistral NeMo, Mistral Small, Pixtral 12B — are free to self-host commercially. Flagship and specialist weights ship research-only or non-production and need a paid licence.

solid answer

~50 s

Mistral deliberately maintains two tracks. The **open track** is Apache 2.0: Mistral 7B, the Mixtral 8x7B and 8x22B MoE models, Mistral NeMo, Pixtral 12B and the Mistral Small line (Apache 2.0 from Small 3 onward). Apache 2.0 means you may download, modify, fine-tune, redistribute and run those weights in a commercial product with no revenue or user-count threshold and no separate agreement. The **restricted track** covers weights published for inspection but not for business use: the **Mistral Research License (MRL)** on flagship weights such as Mistral Large 2 and Pixtral Large permits research and evaluation only, and any commercial deployment requires a negotiated Mistral Commercial License. **Codestral** uses the **Mistral Non-Production License (MNPL)** — development and testing yes, production no. Some tiers, notably Mistral Medium, are API-only with no weights at all. So the practical rule: weights on Hugging Face prove availability, not permission. Read the LICENSE file of the specific release, because Mistral has moved individual models between tracks.

go deeper

for a junior

Know that Mistral publishes some models under Apache 2.0 and keeps others restricted, and that you must open the LICENSE file of the specific release before using it in a product.

for a middle

Be able to name the three instruments — Apache 2.0, Mistral Research License, Mistral Non-Production License — say which models sit where, and explain that downloadable does not mean commercially usable.

for a senior

Show you would build a licence inventory per deployed model, track derivatives and quantisations as inheriting the base terms, and re-verify on every model upgrade rather than once at selection time.

for a principal

Own the tradeoff: the Apache-2.0 tier buys you portability and freeze-in-place control at a capability cost, while the flagship tier means either an API dependency or a negotiated commercial weight agreement with real procurement lead time.

## Why Mistral has two licence tracks Mistral's commercial strategy is deliberately split. It publishes genuinely open weights to build adoption and community mindshare, and it keeps its strongest and most commercially valuable models either behind the API or behind a paid weight licence. Understanding which track a given model sits on is the first question in any "can we self-host Mistral?" conversation, and it is what interviewers are actually probing — not the parameter counts. ## Track 1 — Apache 2.0 Apache License 2.0 is a permissive OSI-approved licence. For model weights it practically means: you may download them, run them anywhere including in production, modify and fine-tune them, redistribute the originals or your derivatives, embed them in a closed-source commercial product, and you owe no royalty. There is **no monthly-active-user cap, no revenue threshold, and no obligation to open-source your derivative**. The obligations are light: retain the copyright and licence notices, state significant changes, and note that the licence includes an express patent grant that terminates if you sue over patents in the work. As of mid-2026 the Apache-2.0 side of the Mistral catalogue includes Mistral 7B, Mixtral 8x7B and Mixtral 8x22B (the sparse mixture-of-experts pair), Mistral NeMo 12B, Pixtral 12B (vision-language), and the Mistral Small line from Small 3 onward — the 24B-class model that in practice replaced Mixtral 8x7B for most self-hosting teams. Several agentic/coding and audio releases have also landed under Apache 2.0. ## Track 2 — the Mistral Research License The MRL is a source-available, **non-commercial** licence. Mistral publishes the weights so researchers and engineers can study, benchmark and experiment with them, but any use "in connection with a commercial activity" — internal or external — requires a separate Mistral Commercial License obtained from the company. Mistral Large 2 and Pixtral Large are the canonical MRL releases. Two consequences people miss: internal business use inside your company still counts as commercial, and a fine-tune or distillation of MRL weights is a derivative that inherits the restriction. ## Track 3 — the Mistral Non-Production License The MNPL, used for Codestral, is narrower still. It allows development, testing, research and evaluation, and explicitly excludes production and any commercial use. It exists so a developer can prototype with the model locally before deciding to pay for either a commercial weight licence or hosted API access. ## Track 4 — no weights at all Mistral Medium is API-only: there is no public weight release, so the only lawful path is la Plateforme (or a cloud partner such as Azure AI Foundry, AWS Bedrock or Google Vertex AI where Mistral models are resold). API use is governed by Mistral's terms of service, not by a weight licence at all — a different legal instrument covering data handling, rate limits and acceptable use. ## The hazard: availability is not permission The single most common mistake is treating a Hugging Face model page as proof of open source. Mistral publishes MRL and MNPL weights on the same hub, in the same format, downloadable with the same `from_pretrained` call. Nothing in the tooling stops you; only the LICENSE file does. Equally, tags like "open-weights" or "open model" in blog posts do not mean OSI-open. ## Practical compliance workflow 1. For every Mistral model you intend to ship, record the exact release name and read that release's LICENSE and any accompanying use policy. 2. Classify it: Apache 2.0 (ship freely), MRL (research only — needs a commercial agreement), MNPL (non-production only), or API-only. 3. Track derivatives: fine-tunes, merges, quantised GGUF builds and distilled students inherit the base licence, and third-party quantisations on the hub often carry a different, sometimes wrong, licence tag than the original. 4. Re-check on upgrade. Mistral has changed licences between generations — Mistral Small moved to Apache 2.0 at version 3 — so the answer for one release is not automatically the answer for the next. ## What the answer signals in an interview A candidate who can name the three licence instruments and state the practical difference (free commercial self-hosting vs research-only vs non-production) is showing that they can run a vendor-selection conversation with legal in the room. A candidate who says "Mistral is the open-source one" is showing they have only read the marketing.

  • If you fine-tune a model released under the Mistral Research License, what licence does your adapter carry?
    The fine-tune is a derivative work and inherits the MRL restriction, so it remains research/non-commercial regardless of how much of your own data went in. A LoRA adapter is only useful in combination with the base weights, so the base licence governs the deployment. To ship the result commercially you need a Mistral commercial agreement for the base model, or you fine-tune an Apache-2.0 base instead.
  • Your legal team asks whether Apache 2.0 imposes any user-count or revenue threshold on the Mistral weights. What do you tell them?
    No. Apache 2.0 has no scale trigger of any kind — no MAU cap, no revenue ceiling, no obligation to re-license your product or to open-source derivatives. The obligations are attribution: keep the licence and copyright notices, and mark significant modifications. That is precisely what makes the Apache-2.0 half of Mistral's catalogue attractive versus community-style licences that add usage thresholds.
  • Does calling a research-licensed Mistral model through la Plateforme require that research licence?
    No. The weight licence governs weights you download. Calling the model over Mistral's hosted API is governed by Mistral's commercial terms of service, which permit production use on paid plans. That is why a model can be simultaneously research-only as a download and perfectly legal to use commercially as an API — the same is true of Mistral models resold through cloud marketplaces.

saying these in an interview costs you the question

  • Assuming every Mistral model is Apache-2.0 because some are
  • Treating weights on Hugging Face as permission to ship
  • Believing Apache 2.0 has a user or revenue threshold
  • Thinking internal-only use escapes a non-commercial licence
  • Assuming a fine-tune resets the base model's licence

context