homeservicesworkaboutblogfree templatescontactFree Tools →Free AI ModelsResearch LibraryROI CalculatorSavings CalculatorAI Readiness ScoreHire vs. AutomateAutomation Quote
book a 30-min call
home / free-models / shieldstral-3b

Shieldstral 1.0 3B

Mistral AI · European Union · Apache 2.0

Commercial use: Yes — free for commercial use

Apache 2.0. Unrestricted.

What this means for your business

A small model whose only job is checking whether text going into or out of your AI is a problem.

Why it should matter to you

Guardrails are the part of an AI build that gets cut first and missed most. A general model asked to police itself is unreliable, because the same prompt injection that redirects the model redirects its self-check. A separate classifier is a different, harder target.

How it connects to our work

We run guardrails as a distinct layer outside the model, because a model that follows its instructions 98% of the time is an impressive research result and an unacceptable compliance posture. Hidden prompt injection is the attack that makes this concrete.

From our field notesHidden prompt injection is the attack vector nobody's demo covers.

Parameters3B
Active per token3B (dense)
Context32K
Modalitytext
Memory @ Q4_K_M~2 GB
Memory @ Q8_0~3.5 GB
LicenceApache 2.0
Last verified2026-09

Advantages

  • A dedicated safety classifier rather than a general model asked to police itself
  • Tiny and fast enough to sit in front of every request without adding noticeable latency
  • Apache 2.0 and EU-origin, so it can run inside a GDPR-constrained pipeline

Disadvantages

  • Classifier only — it does not generate
  • No classifier catches everything, particularly prompt injection hidden inside documents
  • Adds a step to every request, so it needs to be genuinely fast in your stack

Reach for it when

Filtering input and output around a production agent, especially where you need the guardrail itself to stay in the EU.

Where it falls down

Being the whole safety story. It is one layer; policy enforcement, blast-radius limits and logging are the others.

Running it

4 GB. Runs on almost anything. See the hardware sizing tables for how that maps to specific chips and cards, and the quantisation guide for what you give up at each bit width.

will it fitShieldstral 1.0 3B against common GPUs
Shieldstral 1.0 3B at Q4_K_M
0 GB
Shieldstral 1.0 3B at Q8_0
0 GB
RTX 3060 12GB
0 GB
RTX 4060 Ti 16GB
0 GB
RTX 4090
0 GB
RTX 5090
0 GB
RTX 6000 Ada
0 GB
A100 80GB
0 GB
H100 80GB
0 GB
Weight sizes for Shieldstral 1.0 3B as recorded in this directory; GPU memory from the hardware table on the directory hub. Weights only: context adds KV cache.
where the weights fitGPU and Mac memory, checked
Q4_K_MQ8_0
RTX 3060 12GB (12 GB)
RTX 4060 Ti 16GB (16 GB)
RTX 4090 (24 GB)
RTX 5090 (32 GB)
RTX 6000 Ada (48 GB)
A100 80GB (80 GB)
H100 80GB (80 GB)
Mac, 16 GB unified
Mac, 24 GB unified
Mac, 32 GB unified
Mac, 36 GB unified
Mac, 64 GB unified
Mac, 96 GB unified
Mac, 128 GB unified
Mac, 192 GB unified
Mac, 512 GB unified
✓ fits with room for context, ~ fits with under 15% headroom, ✕ does not fit. Weights only, computed from the figures on this page.

Free tiers carrying this model

ProviderTypeThe catchLive limits
Mistral La PlateformeFirst-party APINot every Mistral model is commercially free even when the weights are public — Codestral ships under a non-production licence. Check per model, not per vendor.check →

Jurisdiction: European Union

Mistral is the only EU-headquartered lab shipping frontier-adjacent open weights. Contracting with an EU entity removes the international-transfer question entirely rather than solving it with a framework. Most of the Mistral open range is Apache 2.0, so you can also self-host and remove the vendor from the data path altogether.

Watch for: EU jurisdiction is not the same as EU data residency, and neither is the same as EU-only sub-processors. Ask for all three in writing if it matters to you. Also note that Codestral ships under a non-production licence — being a European vendor does not make every model commercially free.

Frequently asked

Can I use Shieldstral 1.0 3B commercially?

Apache 2.0. Unrestricted.

What hardware do I need to run Shieldstral 1.0 3B?

4 GB. Runs on almost anything. Weights alone are roughly 2 GB at Q4_K_M and 3.5 GB at Q8_0. Add KV cache on top of that, which grows with your context length.

What licence is Shieldstral 1.0 3B released under?

Apache 2.0. Full commercial use, modification and redistribution. Patent grant included. The most permissive licence in common use for open-weight models.

Where can I use Shieldstral 1.0 3B for free?

Free tiers carrying it include Mistral La Plateforme. Limits differ per provider and change often, so check each provider's own limits page. You can also self-host the weights, which has no rate limit at all.

Similar models

Wiring Shieldstral 1.0 3B into something real?

We build the evaluation harness, the failover and the cost ceilings around a model like this, so it survives contact with production.

Maps to AI agent development, AI automation development and AI strategy and consulting. Or see it working: our case studies.