§01The 2026 landscape

Three things have happened since 2024. The frontier consolidated around four families (Anthropic, OpenAI, Google, xAI). Open-weight quality crossed the threshold where, for narrow tasks at sustained utilisation, self-hosting actually pays. And each family settled into a clear specialty rather than chasing a generic "best on every benchmark" position.

The open-weight tier

Four open-weight families are genuinely competitive on the right slice of workloads: Llama 4 (Meta — broadest deployment story, best Bedrock/Azure availability), Qwen 3 (Alibaba — strong multilingual, leading the open coding charts), DeepSeek V4 (MoE architecture, extraordinary inference economics at scale, R-series reasoning variants), and Mistral Large (European data-sovereignty story, mid-tier sizing for on-prem deploys).

§02The benchmark trap

If you are picking a model on MMLU, HumanEval, or HellaSwag scores: stop. Three problems.

Contamination. Public benchmarks are in the training data. Every frontier lab has scrubbed for them and every one of them has missed some. A 2-point HumanEval gap between vendors is inside the noise floor of "did they accidentally train on it."

Distribution mismatch. MMLU asks four-option multiple-choice questions about US history and elementary biology. Your workload is, presumably, not that. A model that's 4 points better on MMLU can be measurably worse at your retrieval-grounded customer-service queries, because the failure modes you care about — hallucination on out-of-distribution chunks, format-following on JSON output, refusal calibration on edge cases — aren't what MMLU measures.

Saturation. The frontier is at 88-92% on most of these benchmarks. Differences in the noise zone don't predict workload performance. The benchmarks that do still discriminate (ARC-AGI-2, FrontierMath, SWE-Bench Verified, GPQA Diamond, OSWorld) are useful only if your workload looks like those benchmarks.

§03The comparison matrix

Twenty rows: frontier closed, frontier open-weight, plus a handful of specialised models (embeddings, rerankers, NLI). Sort by any column. The filter buttons restrict to a tier. Prices are per million tokens, approximate, May 2026.

§04By task

Where each family genuinely wins. None of this is a soft preference — these are observable in workload-specific evals at margins wider than benchmark noise.

§05By constraint

The same model can be the right answer for one workload and wrong for another — not because of capability, but because of the surrounding box: latency budget, cost ceiling, context need, compliance regime. Walk these in order. The first hard constraint usually narrows you to one or two families before capability even enters the picture.

§06When does open-weight self-host actually win?

The honest answer is: narrower than the open-source enthusiast crowd will tell you, but real where it does win. Three patterns.

Pattern 1: A small specialised model at sustained high utilisation. The canonical example is NLI for hallucination-checking — a fine-tuned DeBERTa-v3-large at 400M parameters is essentially free to run on a single GPU and beats a frontier LLM at deciding "does this answer follow from this context." If you are doing fact-checking at any volume (millions of decisions per day), self-hosting that one model saves five figures monthly versus calling a frontier API for the same task. The win here is task specialisation, not size.

Pattern 2: Data sovereignty as a hard requirement. European public sector, certain healthcare workloads, anything where the data physically cannot leave a particular jurisdiction or your tenancy. Self-hosted Llama 4 70B on EU infrastructure, or Mistral Large via Scaleway, is genuinely the only option. The cost is higher than calling Gemini Flash; the alternative is "the project does not exist."

Pattern 3: Sustained, predictable, very-high-volume workload. At >10M tokens/day with predictable shape, a dedicated DeepSeek V4 or Llama 4 405B deployment on H200s amortises against the per-token premium that frontier APIs charge. The breakeven volume keeps creeping up as the frontier labs drop prices; in 2024 it was 1M/day, in 2026 it's closer to 20M/day before pure cost makes the case. Cost alone is rarely the winning argument anymore.

§07Specialised models — what you also need

A real production stack uses an LLM plus three or four specialised models. Treating "the LLM" as the whole answer is one of the more expensive mistakes in this domain.

§08The decision tree

Five questions. Answer in order. Each answer either narrows the field or lands you on a recommendation. This codifies the rubric above into a path you can defend in a procurement meeting.

§09The wrong-default trap

The most expensive mistake in 2026 is not picking the wrong frontier model. It is defaulting to a frontier model when a tier-2 model would do.

"We use Claude Sonnet for everything" or "we just call GPT-5.5" are statements I hear from engineering teams whose actual workload — classification, extraction, simple Q&A, retrieval-grounded chat — would run identically well on Haiku, Flash, or Mini at one-tenth the cost. The per-call savings look small. Multiplied by your monthly volume, it is the difference between a $40K and a $4K invoice for the same outcome.

The corollary: a real eval suite, including a cost-tier comparison, is the single highest-ROI engineering investment in this space. You will discover that 60-80% of your traffic can be routed to a cheaper tier without quality regression, and you will spend the difference on the 20-40% that genuinely needs the frontier model.