AI Model Zoo — open-weight models for local inference
The most important open-weight models in September 2026. Which model fits which , what hardware sits behind it, which licence applies. The figures are checked against the providers' model cards and the library.
Pull models via Ollama
# General purpose with image understanding, Apache-2.0 - runs in about 18 GB at Q4
ollama pull qwen3.8:27b
# Small model for modest hardware, Apache-2.0
ollama pull gemma4:12b
# European alternative from Paris, Apache-2.0
ollama pull mistral-small:24b
# Reasoning and mathematics, MIT licence
ollama pull deepseek-r1:32b
# OpenAI's open-weight model, Apache-2.0
ollama pull gpt-oss:20b
Each listed model is available with a single command. The size variant after the colon adapts the model to the hardware you have. All names checked against ollama.com/library on 11 September 2026.
Seven models compared
Every model has its own strengths — size, licence, context length, . Here is the compact overview, linked to each provider's official model page. Newer families such as GLM 5.3, DeepSeek V4.1 or MiniCPM5 already exist on Hugging Face but were not yet in the library on 11 September 2026, which is why they are not listed here.
Llama 4
Meta
Mixture-of-Experts
Meta flagship
Llama 4 comes as a mixture of experts: Scout with 16 experts, Maverick with 128, each with 17 billion active parameters. Meta has not released a new generation since April 2025. The Llama licence permits commercial use with conditions.
Mistral Small 3 with 24 billion parameters is the practical size for a single graphics card. Above it sit Mistral Small 4 and Mistral Large 3 for server hardware. All Apache-2.0, and the provider is based in Paris.
Qwen 3.8 with 27.3 billion parameters also understands images and holds around 262,000 tokens of context. Apache-2.0, and therefore unproblematic for mid-sized businesses. Excellent German quality — this is the model we use day to day ourselves.
4 ranges from the tiny E2B and E4B variants up to 31 billion parameters, plus a mixture-of-experts version with 26 billion. The key change from 3: the separate licence is gone, 4 is Apache-2.0.
DeepSeek R1 still sets the standard for logical reasoning and mathematics. The full version with 671 billion parameters needs server hardware; the distilled variants with 32 and 70 billion run on hardware a mid-sized company actually buys. MIT licence.
Phi 4 with only 14B parameters shows: well-curated training data beats sheer size. Very good performance on a single RTX 4090. MIT license, commercially unrestricted.
In August 2025 OpenAI released gpt-oss in two sizes (20B and 120B) under Apache-2.0. In model quality clearly better than older OSS models, with full commercial release.
An open-weight model is an whose trained weights (the parameter file) are publicly available — typically as a download on HuggingFace, on the vendor website or through . That distinguishes them from ChatGPT, Claude or Gemini Pro, whose weights are not released and which are accessible only via APIs.
Important: “open weight” is not the same as “open source”. Licences vary widely — from genuine MIT or Apache-2.0 (Qwen, 4, Mistral, Phi, DeepSeek, gpt-oss) to bespoke provider licences with conditions (Llama). Anyone deploying commercially reads the licence before the download, not after.
Which model for what?
Recommendations from our own client work, as of September 2026. Not “the best model” — there is no best. Rather: for this purpose, this model is the most pragmatic fit.
General purpose in SMBs (text, translation, Q&A)
Qwen 3.8 27B has become the standard — Apache-2.0, very good German, understands images as well, needs around 18 GB at Q4. Gemma 4 31B as the alternative if a Google model is preferred.
Coding & code completion
Qwen3 Coder Next with 79.7 billion parameters for serious work on a codebase — around 49 GB at Q4, so a workshop machine rather than a laptop. Where that space is missing, Qwen 3.8 27B does the job well too.
Reasoning, logic, mathematics
DeepSeek R1 remains ahead on logical reasoning. The distilled variants with 32 and 70 billion parameters bring a large part of that onto hardware a mid-sized company actually buys.
Small and fast (edge, mobile, embedded)
Gemma 4 in its E2B, E4B and 12B variants, alternatively Phi 4 14B. All run on a single consumer graphics card or even a capable CPU — for embedded AI features in your own applications.
Multilingual with a GDPR bonus
Qwen 3.8 for multilingual work, with an Apache-2.0 licence. Mistral Small 3 24B as the European alternative — Mistral AI is based in Paris and its weights are Apache-2.0 as well.
When nobody is allowed to use the OpenAI cloud
gpt-oss in 20B or 120B, Apache-2.0. OpenAI has not released a newer open-weight model since August 2025 — for industries that want ChatGPT quality but may not use the OpenAI cloud, it remains the obvious choice.
What do all open-weight models have in common?
Six properties that make these seven models a class of their own — and distinguish them from cloud frontier models.
Local inference
Model runs on your own hardware (Mac, workstation, server). No request leaves the network. Mandatory in industries with confidentiality or GDPR obligations — lawyers, doctors, tax advisors, engineers with IP protection.
Quantisation available
Per model quantisations (Q4_K_M, Q5_K_M, Q8_0) are available that reduce RAM/VRAM footprint by a factor of 2–4 — with just barely acceptable quality loss. Q4_K_M is standard for self-hosting.
OpenAI-API compatible
Via , vLLM or llama.cpp all these models are served behind an OpenAI-compatible . Existing OpenAI client libraries (Python SDK, nodes) work without code change.
Multi-modal optional
Most current models accept images — Qwen 3.8 and 4 out of the box. Applications: reading scanned invoices, assessing component photos for complaints, capturing forms.
Fine-tuning possible
With your own data (glossary, style guides, domain knowledge) the models can be further trained — usually via LoRA/QLoRA for moderate hardware needs. Domain-specific strengths without full pre-training.
No vendor lock-in
Switching models without code changes: swap the tag, the OpenAI-compatible endpoint stays the same. Anyone using 4 today moves to Qwen 3.8 tomorrow — within minutes. We have made exactly that switch ourselves.
OpenAI-compatible API call against a local model
# Pick a model (variable)
MODEL="qwen3.8:27b"
# Alternative: gemma4:12b · mistral-small:24b · deepseek-r1:32b · gpt-oss:20b
# OpenAI-compatible chat-completion call
curl http://localhost:11434/v1/chat/completions \
-H "Content-Type: application/json" \
-d '{
"model": "'$MODEL'",
"messages": [
{"role": "system", "content": "You are a pragmatic AI consultant for SMBs."},
{"role": "user", "content": "Which model do you recommend for an 8-person law firm with an RTX 4090?"}
],
"temperature": 0.2
}'
# The same request also works with the OpenAI Python SDK,
# simply set OPENAI_API_BASE to http://localhost:11434/v1.
A single curl call against the local Ollama API. Model name as a variable — swappable across all seven models. Source: own practice.
Cloud alternatives honestly compared
If open-weight is not enough — what else?
Three cloud frontier models that are still often ahead in absolute quality. Trade-off: data flow and per-token costs against top quality.
Frontier cloud (USA)
ChatGPT (GPT-5)
OpenAI
+ Best general-purpose frontier vendor
+ Tools, function calling, vision very mature
− US cloud, no self-hosting
− Data flow even with an enterprise DPA
Frontier cloud (USA/EU)
Claude (Anthropic)
Anthropic
+ Very strong on long texts
+ EU endpoints available
− Also no self-hosting option
− Per-token cost rises quickly at volume
Frontier cloud (USA)
Gemini Pro
Google
+ Very long context window (1M+ tokens)
+ Strong multi-modal
− Google cloud, US data location
− Data policy less transparent than OpenAI/Anthropic
Rule of thumb: with GDPR obligations or IP protection — open-weight local. For maximum quality on uncritical content — cloud frontier. For both — multi-routing in (sensitive content local, general research cloud).
Pricing
Hardware investment vs. per-token costs.
License
Mix of Apache-2.0 (Mistral, Qwen, Phi, GPT-oss), MIT (DeepSeek), custom community licences (Llama, Gemma). For SMB own-use in nearly all constellations unproblematic — verify per model on the respective card.
Hardware costs
Mid-range (for models up to 32B): RTX 4090 24GB + 32GB RAM workstation, around €3,000. Premium (for 70B+): Apple Mac Studio M4 Ultra 192 GB from €8,000 or an NVIDIA server with RTX 5090. Power: 150–300 W during inference, <50 W idle.
vs. cloud API
Cloud costs scale linearly with volume. At 1,000 tokens/day per 10 staff: GPT-5 around €60/month, Claude Sonnet similar. Self-hosted: hardware amortisation in 12–18 months. From 50+ staff clearly cheaper.
Important: quantisation quality is not linear. Q4_K_M is standard and 'good enough' for 95 % of . Q5/Q6 for higher demands. Full FP16 only for research. Anyone trying to make do with less VRAM should first check quantisation before picking a smaller model.
Related topics
Models need an inference server and a frontend
Models alone are useless. loads them, provides the user surface, the server solution sits behind: