---
title: "Frontier vs workhorse vs local LLM | Len P. van der Hof"
description: Frontier, workhorse, and local are operating classes for language-model work. Frontier is rationed for jobs that need it, workhorse carries the bulk, local…
image: "https://lenvanderhof.com/media/generated/blog-hero-frontier-workhorse-local-v1.df91f81eff4e.wide.webp"
---

[AI Systems](https://lenvanderhof.com/en/blog/category/ai-systems/) Research guide

# Frontier, workhorse, or local: three classes, not a religious war

The forum fight is cloud versus local. The operator question is which class owns this task.

Len P. van der HofPublished 24 September 20263 min read

Three classes in one room. The job picks the bench.

Direct answer

Frontier, workhorse, and local are three classes of language-model work from The Model Portfolio. Frontier is the scarce, expensive tier, rationed for tasks that fail on anything cheaper. Workhorse is the default-capable tier where volume is meant to live. Local is a placement decision: the model runs on infrastructure you control because privacy, latency, sovereignty, or volume says it must. Frontier and workhorse are capability tiers. Local is about where the model runs, and a local model can serve a workhorse route or even a frontier route if your own evaluation says so. The book also names a fourth archetype, specialist, for narrow domains. A private, high-volume, easy task is not a frontier job. The Model Portfolio is live. This page is the split, not the routing policy.

## Key takeaways

- Class follows the task and its privacy class, not the vendor keynote.
- Frontier is rationed. If everything is frontier, nothing is.
- Local is a placement decided by who controls the infrastructure, not a moral stance.
- This page is the split. Model routing is the policy that uses it.

Search “local LLM vs API” and you get a forum fight. One camp treats the cloud as betrayal. The other treats a local model as a hobby. Neither is an operating split.

**Frontier, workhorse, or local?** Three classes. The task picks the class. The brand does not.

**Frontier** is the scarce tier. Deep reasoning, messy ambiguity, long-context synthesis, jobs where a cheaper miss costs more than the token bill. You ration it. The moment frontier becomes the default destination, the invoice starts explaining your architecture.

**Workhorse** is the default-capable tier. Bulk extraction, classification, summaries, drafts a human will actually read. This is where volume is meant to live. If the class is empty, every task inflates to frontier.

**Local** is a placement, not a capability rank. A model is local when control of the infrastructure it runs on is part of its mandate: on-premise, a private VPC, an edge device, a developer laptop. Privacy class “never leaves”, a latency budget inside the room, or a volume that would turn the API into a tax. A local model can clear the bar of a workhorse route, or a frontier route, if your own evaluation says so.

## Not a cloud religion, not a leaderboard row

“Open versus closed” is a procurement argument. A closed workhorse and an open workhorse can share a mandate.

A leaderboard rank does not know the privacy class of your prompt. If the prompt carries customer data you promised not to export, the class is local or the call does not happen.

The Model Portfolio names a fourth archetype, the **specialist**: a model fine-tuned or built for one narrow domain such as code, legal extraction, or a single language pair. It earns a place only when a general model at any tier fails a well-defined task, and the task is frequent enough to pay for the maintenance. This page keeps to the three most people search for.

## How to choose this week

Write the task in one sentence. Then score three things, in this order.

**Privacy.** May this text leave the building? If not, local. Stop scoring.

**Difficulty.** Does a cheaper miss cost more than the tokens you save? If yes, frontier. If no, workhorse.

**Volume.** Will it run thousands of times a day? Then workhorse or local, never frontier by default.

Write the answer next to the task, so next week’s hire does not reverse it in a chat window. A vendor SKU is not a class. You assign the class, and the same hosted model can be workhorse on Tuesday and a forbidden privacy miss on Wednesday.

## Two pages

[What is model routing?](https://lenvanderhof.com/en/blog/what-is-model-routing/) is the policy that uses these classes. This page is the split.

[The Model Portfolio](https://lenvanderhof.com/books/the-model-portfolio/) is live. You do not need the hardcover to stop sending private bulk to the flagship.

Cite this:Frontier, workhorse, or local: three classes, not a religious war.Len P. van der Hof. [https://lenvanderhof.com/en/blog/frontier-vs-workhorse-vs-local/](https://lenvanderhof.com/en/blog/frontier-vs-workhorse-vs-local/) · Published 24 September 2026.

## Terminology

- [ROUTE](https://lenvanderhof.com/glossary/route/)

## Sources

1. [ROUTE (glossary)](https://lenvanderhof.com/glossary/route/)
2. [What is model routing?](https://lenvanderhof.com/en/blog/what-is-model-routing/)
3. [The Model Portfolio](https://lenvanderhof.com/books/the-model-portfolio/)

## Further reading

- [ROUTE](https://lenvanderhof.com/glossary/route/)
- [What is model routing?](https://lenvanderhof.com/en/blog/what-is-model-routing/)
- [The Model Portfolio](https://lenvanderhof.com/books/the-model-portfolio/)

About the author

## [Len P. van der Hof](https://lenvanderhof.com/en/authors/len-p-van-der-hof/)

Entrepreneur, AI Innovator and Venture Builder

Len P. van der Hof builds practical AI systems, digital ventures and evidence-informed tools for founders.

```json
{
	"@context": "https://schema.org",
	"@graph": [
		{
			"@type": "Person",
			"@id": "https://lenvanderhof.com/#person",
			"name": "Len P. van der Hof",
			"alternateName": [
				"Len van der Hof",
				"L.P. van der Hof",
				"Leendert Pieter van der Hof"
			],
			"honorificSuffix": "MSc",
			"url": "https://lenvanderhof.com/",
			"image": [
				"https://lenvanderhof.com/photos/len-portrait-1.jpg",
				"https://lenvanderhof.com/photos/len-portrait-2.jpg",
				"https://lenvanderhof.com/photos/len-portrait-3.jpg",
				"https://lenvanderhof.com/photos/len-portrait-4.jpg",
				"https://lenvanderhof.com/photos/len-speaking.jpg",
				"https://lenvanderhof.com/photos/len-hero.jpg"
			],
			"jobTitle": "Entrepreneur, AI Innovator and Venture Builder",
			"description": "Len P. van der Hof, MSc, is a Dutch entrepreneur and AI innovator in Zwijndrecht. He builds ReasonKit, MindSesh, Undominated.ai, books under his name, the fiction imprint LPH98.lifestyle, and technology ventures through LPH98.ventures. Eleven titles in Systems for the Strategic Self are available now, in English and Dutch.",
			"address": {
				"@type": "PostalAddress",
				"addressLocality": "Zwijndrecht",
				"addressCountry": "NL"
			},
			"alumniOf": {
				"@type": "CollegeOrUniversity",
				"name": "Rotterdam School of Management, Erasmus University"
			},
			"knowsAbout": [
				"Artificial intelligence",
				"AI agents",
				"Agentic AI systems",
				"LLM routing",
				"SEO",
				"Generative engine optimization",
				"Answer engine optimization",
				"Venture building",
				"Founder performance",
				"Founder psychology",
				"Evidence-based decision-making"
			],
			"sameAs": [
				"https://www.linkedin.com/in/lenvanderhof/",
				"https://x.com/LenvanderHof",
				"https://www.youtube.com/channel/UCTG20buKqYYbitqqf7l3zJA",
				"https://www.instagram.com/Lenvanderhof/",
				"https://www.threads.com/@lenvanderhof",
				"https://github.com/Lenvanderhof",
				"https://huggingface.co/LPH98",
				"https://www.npmjs.com/~lenvanderhof",
				"https://www.goodreads.com/author/show/70983905.Len_P_van_der_Hof",
				"https://www.amazon.com/author/lenvanderhof",
				"https://www.bol.com/nl/nl/b/len-p-van-der-hof-msc/609879394/",
				"https://bsky.app/profile/lenvanderhof.com",
				"https://mastodon.social/@Lenvanderhof",
				"https://crates.io/users/Lenvanderhof",
				"https://cursor.com/@Lenvanderhof",
				"https://medium.com/@Lenvanderhof",
				"https://gitlab.com/Lenvanderhof",
				"https://hub.docker.com/u/lenvanderhof/",
				"https://dev.to/lenvanderhof",
				"https://www.facebook.com/Lenvanderhof",
				"https://soundcloud.com/Lenvanderhof"
			],
			"affiliation": [
				{
					"@id": "https://lenvanderhof.com/#publisher"
				},
				{
					"@id": "https://lenvanderhof.com/#mindsesh"
				},
				{
					"@id": "https://lenvanderhof.com/#lifestyle"
				}
			]
		},
		{
			"@type": "WebSite",
			"@id": "https://lenvanderhof.com/#website",
			"url": "https://lenvanderhof.com/",
			"name": "Len P. van der Hof",
			"description": "Len P. van der Hof, MSc, is a Dutch entrepreneur and AI innovator in Zwijndrecht. He builds ReasonKit, MindSesh, Undominated.ai, books under his name, the fiction imprint LPH98.lifestyle, and technology ventures through LPH98.ventures. Eleven titles in Systems for the Strategic Self are available now, in English and Dutch.",
			"inLanguage": [
				"en",
				"nl"
			],
			"publisher": {
				"@id": "https://lenvanderhof.com/#person"
			}
		},
		{
			"@type": "Organization",
			"@id": "https://lenvanderhof.com/#publisher",
			"name": "LPH98.ventures",
			"url": "https://lph98.ventures",
			"founder": {
				"@id": "https://lenvanderhof.com/#person"
			}
		},
		{
			"@type": "Organization",
			"@id": "https://lenvanderhof.com/#mindsesh",
			"name": "MindSesh",
			"url": "https://mindsesh.net",
			"founder": {
				"@id": "https://lenvanderhof.com/#person"
			}
		},
		{
			"@type": "SoftwareApplication",
			"@id": "https://lenvanderhof.com/#reasonkit",
			"name": "ReasonKit",
			"url": "https://reasonkit.sh",
			"creator": {
				"@id": "https://lenvanderhof.com/#person"
			}
		},
		{
			"@type": "SoftwareApplication",
			"@id": "https://lenvanderhof.com/#undominated",
			"name": "Undominated.ai",
			"url": "https://undominated.ai",
			"creator": {
				"@id": "https://lenvanderhof.com/#person"
			}
		},
		{
			"@type": "Organization",
			"@id": "https://lenvanderhof.com/#lifestyle",
			"name": "LPH98.lifestyle",
			"url": "https://lph98.lifestyle",
			"founder": {
				"@id": "https://lenvanderhof.com/#person"
			}
		},
		{
			"@type": "ImageObject",
			"@id": "https://lenvanderhof.com/en/blog/frontier-vs-workhorse-vs-local/#primaryimage",
			"url": "https://lenvanderhof.com/media/generated/blog-hero-frontier-workhorse-local-v1.df91f81eff4e.wide.webp",
			"contentUrl": "https://lenvanderhof.com/media/generated/blog-hero-frontier-workhorse-local-v1.df91f81eff4e.wide.webp",
			"representativeOfPage": true
		},
		{
			"@type": "BreadcrumbList",
			"@id": "https://lenvanderhof.com/en/blog/frontier-vs-workhorse-vs-local/#breadcrumb",
			"itemListElement": [
				{
					"@type": "ListItem",
					"position": 1,
					"name": "Home",
					"item": "https://lenvanderhof.com/"
				},
				{
					"@type": "ListItem",
					"position": 2,
					"name": "Blog",
					"item": "https://lenvanderhof.com/en/blog/"
				},
				{
					"@type": "ListItem",
					"position": 3,
					"name": "AI Systems",
					"item": "https://lenvanderhof.com/en/blog/category/ai-systems/"
				},
				{
					"@type": "ListItem",
					"position": 4,
					"name": "Frontier, workhorse, or local: three classes, not a religious war",
					"item": "https://lenvanderhof.com/en/blog/frontier-vs-workhorse-vs-local/"
				}
			]
		},
		{
			"@type": "WebPage",
			"@id": "https://lenvanderhof.com/en/blog/frontier-vs-workhorse-vs-local/#webpage",
			"url": "https://lenvanderhof.com/en/blog/frontier-vs-workhorse-vs-local/",
			"name": "Frontier, workhorse, or local: three classes, not a religious war",
			"description": "Frontier, workhorse, and local are operating classes for language-model work. Frontier is rationed for jobs that need it, workhorse carries the bulk, local is where the data must stay. The task and its privacy class pick the class. The vendor keynote does not.",
			"isPartOf": {
				"@id": "https://lenvanderhof.com/#website"
			},
			"primaryImageOfPage": {
				"@id": "https://lenvanderhof.com/en/blog/frontier-vs-workhorse-vs-local/#primaryimage"
			},
			"breadcrumb": {
				"@id": "https://lenvanderhof.com/en/blog/frontier-vs-workhorse-vs-local/#breadcrumb"
			},
			"inLanguage": "en-GB"
		},
		{
			"@type": "BlogPosting",
			"@id": "https://lenvanderhof.com/en/blog/frontier-vs-workhorse-vs-local/#article",
			"mainEntityOfPage": {
				"@id": "https://lenvanderhof.com/en/blog/frontier-vs-workhorse-vs-local/#webpage"
			},
			"headline": "Frontier, workhorse, or local: three classes, not a religious war",
			"description": "Frontier, workhorse, and local are operating classes for language-model work. Frontier is rationed for jobs that need it, workhorse carries the bulk, local is where the data must stay. The task and its privacy class pick the class. The vendor keynote does not.",
			"datePublished": "2026-09-24T14:00:00.000Z",
			"author": {
				"@id": "https://lenvanderhof.com/#person"
			},
			"publisher": {
				"@id": "https://lenvanderhof.com/#person"
			},
			"image": [
				"https://lenvanderhof.com/media/generated/blog-hero-frontier-workhorse-local-v1.df91f81eff4e.square.webp",
				"https://lenvanderhof.com/media/generated/blog-hero-frontier-workhorse-local-v1.df91f81eff4e.landscape.webp",
				"https://lenvanderhof.com/media/generated/blog-hero-frontier-workhorse-local-v1.df91f81eff4e.wide.webp"
			],
			"articleSection": "AI Systems",
			"inLanguage": "en-GB"
		}
	]
}
```
