Alpha
Ctrl K
Contact
Implement · Mistral

Can you run it?

Ownership levelLimitednone·limited·partial·substantial·fullAnalytical input C ยท 63.2/100

This page is a projection of the one entry record, the Reliability and Data control factors that Implement covers. The full verdict is set by all four factors together, floor-weighted so the weakest caps the whole.

Which domain expands which factor
  • AssessUse & modify + Transparency
  • ImplementData control + Reliability
  • UseReliability
  • SupportTransparency

Install & run

Download the safetensors from the verified mistralai organisation on Hugging Face and serve with vLLM, transformers, llama.cpp, or Ollama - for research / non-production use only. Pin the exact revision and verify checksums, and confirm the per-model licence tier (MRL vs MNPL).

Hardware & VRAM requirements

A wide range: Ministral 8B and Codestral 22B run on one or two GPUs; Mistral Large 2 (123B) and Pixtral Large (124B) need serious multi-GPU infrastructure or aggressive quantization. Any production deployment is licence-barred without a commercial agreement.

Serving stacks

vLLM, transformers, llama.cpp, and Ollama - strong mechanics, but production serving is licence-barred without a commercial agreement.

Safe-deployment controls & Deployment Ceiling

Deployment Ceiling: T2 (conditional). First, do not deploy in production or commercially without a negotiated Mistral licence - the MRL/MNPL bar it. Then: supply your own input/output guardrails and a guard/classifier model (historically lighter safety tuning, no first-party guard), add prompt-injection defences, and treat images as untrusted input for Pixtral Large.

Available quantizations

Community GGUF / AWQ / FP8 builds circulate, but their use remains bound by the MRL/MNPL non-commercial terms - a quant confers no commercial rights.

Fine-tuning & adaptation

Fine-tuning for research is permitted, but derivatives inherit the non-commercial bar - commercial/production use of a derivative needs a negotiated Mistral licence. Training data and code are closed, so there is no from-scratch reproduction.

API / OpenAI-compatible integration

Serve behind vLLM's OpenAI-compatible endpoint for research. Mistral also offers these models on its own commercial API/platform, which is the licensed commercial path for production use.

How this scores

The ownership factors this domain covers, drawn from the one entry record.

3

ReliabilityIs it reliable and good enough for the job?

Strong

Performance 4, operational 4 and safety 3 from an accountable EU provider: capable models with strong serving; all at or above 3, two at 4, so reliability is strong. The caveat is the absence of a first-party guard model.

How this scores (AOI sub-dimensions)
Operational4/5how practical it is to run, serve and maintain in productionStrong serving mechanics (vLLM, transformers, llama.cpp, Ollama) and community quants, but the largest models (123B/124B) need serious infrastructure and, decisively, production deployment is licence-barred - so the practical operational ceiling is lower than the Apache line.
Safety3/5whether misuse risks are evaluated and guardrails are providedSafety-tuned instruct/multimodal models with documented behaviour, meeting the score-3 anchor, but Mistral has historically shipped lighter safety tuning than some peers and no first-party guard model - deployers must add their own guardrails.
4

Doesn't extract your dataDoes running it keep your knowledge and data yours?

Strong

Self-hosted for research, the weights run entirely on your own infrastructure with no telemetry or clawback, so your data stays yours - the constraint is on permitted use, not data residency.

How this scores
Not a scored AOI dimension. For a self-hosted model, data-control is a structural property of running the weights yourself, strong by default unless the model phones home or the licence claws back rights. For a hosted API this factor is the retention + train-on-inputs + residency read, scored from the binding terms.
What this means for adoptionYou have only limited ownership of these Mistral models: self-hosting keeps your data yours and the models are capable and well-supported (data-control and reliability strong), but the MRL/MNPL bar commercial and production use without a separately negotiated licence, so use-and-modify is weak - ownership is limited. For anything beyond research or evaluation, either negotiate a commercial licence with Mistral or use the Apache-2.0 Mistral models (the `mistral` entry), which carry none of these restrictions and reach substantial ownership.

Sources

The same evidence records as the entry sheet. Read means the text was verified; unverified means it is known to exist but not yet read.

Licenceread2026-08-03
Mistral licence docs, read: [MRL-0.1] use "solely for (a) personal, scientific or academic research, and (b) for non-profit and non-commercial purposes", excluding revenue activity and SaaS distribution (Ministral 8B, Mistral Large, Pixtral Large).
Model cardread2026-08-03
mistralai Hugging Face org (verified) and Mistral docs: Ministral 8B, Mistral Large 2 (123B), Pixtral Large (124B multimodal) tagged MRL; Codestral tagged MNPL; safetensors with checksums; broad serving (vLLM, transformers, llama.cpp, Ollama).
Third-party analysisunverified2026-08-03
On public leaderboards Mistral Large 2 and Pixtral Large are strong open-weight models, and Ministral 8B is strong for its size; not OneHill-reproduced this session.
Third-party analysisunverified2026-08-03
Mistral has historically shipped lighter safety tuning than some peers and no first-party guard model; independent behavioural analysis is limited.
Third-party analysisunverified2026-08-03
Mistral AI is EU-domiciled (France) and an early GPAI Code of Practice signatory with public per-model licensing and good documentation, but the MRL/MNPL are non-commercial (non-FOSS), so no open-source exemption applies on the licence axis.