Ollama Herd vs Docker Model Runner

Docker Model Runner puts LLMs in your container workflow. Herd puts every machine you own to work. Docker Model Runner is a single-machine serving tool for the Docker-native developer. Herd is a multi-machine fleet router for teams with several machines, Mac, Linux, or Windows.

What is Docker Model Runner?

Docker Model Runner is Docker's native LLM inference feature, introduced in Docker Desktop in early 2026. It extends Docker's container model to include AI model serving as a first-class primitive, letting developers pull and run models with familiar docker model CLI commands. It supports GPU passthrough on NVIDIA and Apple Silicon, integrates with docker-compose workflows, and exposes an OpenAI-compatible API for local development.

What is Ollama Herd?

Ollama Herd is an open-source smart AI router that turns the machines you already own (Apple Silicon Macs, Linux servers, and Windows PCs, with or without NVIDIA GPUs) into one endpoint. It routes LLMs, embeddings, image generation, speech-to-text, and vision with 8-signal scoring, mDNS auto-discovery, and an 8-tab real-time dashboard. Apple Silicon Macs get extras: an MLX backend, native image generation, and speech-to-text. Two commands to set up, zero config files. pip install ollama-herd or brew install ollama-herd.

Feature Comparison

FeatureDocker Model RunnerOllama Herd
Core approachDocker-native model servingFleet request routing (8-signal scoring)
Primary use caseRun models inside the Docker workflowRoute requests across a device fleet
ScopeSingle machineMulti-machine fleet
Model typesLLMs (text generation)LLMs, embeddings, image gen, STT
Key innovationModels-as-containers UX8-signal adaptive routing with capacity learning
API compatibilityOpenAI-compatibleOpenAI + Ollama dual API
Device discoveryN/A (single machine)mDNS auto-discovery
Load balancingNone8-signal scoring across fleet
Health monitoringDocker health checks30+ health checks, 8-signal scoring
DashboardDocker Desktop UI8-tab dashboard (fleet, models, routing, benchmarks)
BenchmarkingNoneBuilt-in smart benchmark with statistical analysis
Context optimizationNoneDynamic context window optimization
Capacity learningNoneLearns per-model, per-node performance over time
Loaded-model awarenessNonePrefers nodes where the model is already loaded
Meeting detectionNoneReduces load on Macs running video calls (macOS only)
Container integrationNative (docker-compose, Docker networking)None (standalone service)
SetupDocker Desktop + enable Model Runnerpip install ollama-herd on one machine
Cross-platformmacOS, Windows, Linux (via Docker Desktop)macOS, Linux, Windows (MLX, mflux image gen, and STT need Apple Silicon)
TestsDocker's internal testing1200+ tests, 30+ health checks
LicenseProprietary (Docker Desktop)MIT

Where Docker Model Runner Wins

  1. Docker ecosystem integration. If your development workflow is Docker-native, docker-compose for local dev, Docker for CI/CD, containers in production, Model Runner fits perfectly. Models become just another service in your compose file alongside your database and API server.
  2. Familiar tooling. docker model pull, docker model run, the CLI patterns are instantly recognizable to the millions of developers who already know Docker. Zero learning curve for the serving layer.
  3. Container isolation. Models run within Docker's isolation model. Clean separation between the model runtime and your host system. Easy to tear down, rebuild, or version-pin.
  4. Same tooling on every OS. Runs on macOS, Windows, and Linux, anywhere Docker Desktop runs, with the same docker model commands everywhere. Herd also runs on all three, but its Apple Silicon extras (MLX backend, mflux image gen, speech-to-text) don't carry over to Linux or Windows.
  5. Compose-native networking. Application containers can reach the model server via Docker's internal DNS, no port mapping, no host networking configuration. Clean service-to-service communication.
  6. DevOps alignment. For organizations that think in containers, Model Runner means AI inference doesn't require a separate operations model. Same monitoring, same deployment patterns, same team.

Where Ollama Herd Wins

  1. Multi-device fleet routing. Docker Model Runner runs on one machine. Herd coordinates a fleet, 3, 5, 8 machines, routing each request to the best available node. This is the fundamental difference.
  2. Intelligent 8-signal routing. Model warmth, memory fit, queue depth, estimated wait, role affinity, availability trend, context fit, and session affinity, Herd considers all of this for every request. Docker Model Runner is first-come, first-served on one machine.
  3. Multimodal routing. Four model types with type-aware routing. Docker Model Runner currently handles LLM text generation. Herd routes embeddings, image generation, and speech-to-text with the same intelligence.
  4. No Docker required. Herd is a lightweight Python package, pip install ollama-herd or brew install ollama-herd. No Docker Desktop subscription, no container runtime overhead, no daemon running in the background.
  5. Capacity learning. Herd learns how each node performs with each model over time and adjusts routing accordingly. No manual tuning, no configuration, it gets smarter the more you use it.
  6. Real-time fleet dashboard. 8-tab dashboard showing fleet health, model distribution, routing decisions, and benchmark results. Docker Desktop shows per-container metrics, but nothing fleet-aware or AI-specific.
  7. Native performance, no container layer. Herd talks directly to Ollama (and, on Macs, MLX) running natively on each machine. No container layer between the model and the GPU. On Apple Silicon, this means no overhead from Docker's virtualization layer.
  8. Meeting and availability awareness. When a MacBook is on a Zoom call (macOS) or a machine's learned availability drops, Herd routes traffic elsewhere. Docker Model Runner has no concept of the host machine's real-world state.
  9. Smart benchmarking. Built-in benchmark with statistical analysis across your fleet. Know exactly how each node performs for each model before routing decisions are made.

The Core Difference

Docker Model Runner extends the container paradigm to model serving, it's a single-machine tool that makes LLMs fit the Docker workflow. Ollama Herd is a fleet orchestration layer that makes multiple machines act as one intelligent AI system.

  • Docker Model Runner answers: "How do I serve a model alongside my containers on this machine?"
  • Ollama Herd answers: "Which of my machines should handle this request right now?"

Docker Model Runner is about developer workflow integration. Herd is about distributed fleet intelligence.

Conceptual: where each tool sits (a tool can span layers)
Clientschat UIs, coding agents, apps
Open WebUI Claude Code Codex Your apps and agents
Gateway / edgeauth, rate limits, cloud providers
Inference serverruns the model on one machine
Ollama mlx_lm.server vLLM LocalAI llama-swap Docker Model Runner LM Studio llama.cpp server NVIDIA PAIR (manages engines)
One model, many machinessplits a model too big for one
Hardwarethe machines themselves
Macs Linux servers Windows PCs NVIDIA GPU servers
Docker Model Runner serves models on one machine, the same layer as Ollama; Herd is the layer above that picks a machine for each request, and it routes to Ollama, not to Docker Model Runner.

A Note on Maturity

Docker Model Runner is early. Docker is a company that iterates quickly and has massive distribution, Docker Desktop is on millions of developer machines. Features like multi-model management, batching, and better GPU utilization are likely coming.

What Docker is unlikely to build: multi-machine fleet routing. Docker's mental model is containers on a host (or orchestrated via Kubernetes/Swarm). Cross-machine AI routing with adaptive scoring is a different problem space entirely. Even Docker Swarm mode doesn't do intelligent workload-aware routing, it does round-robin or simple load balancing.

When to Choose Each

ScenarioChoose
Docker-native dev workflow, single machineDocker Model Runner
Team with several machines (Mac, Linux, Windows) sharing AI workloadsOllama Herd
Need models in docker-compose alongside other servicesDocker Model Runner
Need multimodal routing (LLM + embeddings + image gen + STT)Ollama Herd
Want the same container tooling on every OSDocker Model Runner
Mixed fleet on one LAN (Mac + Linux + Windows), want zero-config discoveryOllama Herd
CI/CD pipeline needs a local model for testingDocker Model Runner
Need intelligent load balancing across devicesOllama Herd
Want container isolation for model servingDocker Model Runner
Want fleet-wide operational dashboardOllama Herd

Bottom Line

Docker Model Runner is Docker doing what Docker does, making infrastructure accessible through familiar tooling. For a single developer who already lives in Docker, it's a natural way to add local model serving. Pull a model, add it to your compose file, call it from your app. Simple, clean, Docker-native.

Ollama Herd solves a different problem: making the machines you already own work together as one AI system. It doesn't care about containers or compose files. It cares about which of your 6 machines has the most memory headroom, the lowest queue depth, and the best historical performance for the model you need right now.

The typical Docker Model Runner user is a developer who wants a local LLM in their Docker dev environment. The typical Herd user is a team that wants their collective hardware (Macs, Linux boxes, Windows PCs) to serve as a shared AI platform. Docker Model Runner is a serving tool. Herd is an orchestration layer. They can coexist side by side as separate endpoints (Herd does not route to Docker Model Runner), but they're solving fundamentally different problems.

Getting Started

pip install ollama-herd    # or: brew install ollama-herd
herd                       # start the router
herd-node                  # on each device

Using Docker Model Runner for local dev? Herd complements it, Docker Model Runner serves models on one machine, Herd routes across your whole team's machines. Try Herd on two machines to see what fleet routing adds.

Frequently Asked Questions

Is Ollama Herd a good alternative to Docker Model Runner?

They solve different problems. Docker Model Runner integrates LLM serving into your Docker workflow on a single machine. Ollama Herd routes AI requests across multiple devices with intelligent scoring. If you want models alongside your containers in docker-compose, use Docker Model Runner. If you want your team's machines (Macs, Linux boxes, Windows PCs) working together as one AI system, use Herd.

Can I use Ollama Herd with Docker Model Runner?

Side by side, yes. As a Herd backend, not today: Herd nodes serve Ollama and MLX (mlx-lm) models, and Herd does not route to Docker Model Runner endpoints. Keep Docker Model Runner in your container workflow, run Herd across your fleet, and point each app at the endpoint that fits.

How does Docker Model Runner compare to Ollama Herd for teams?

Docker Model Runner is a single-machine tool, each developer runs models on their own laptop. Ollama Herd turns the entire team's devices (Macs, Linux workstations, Windows PCs) into a shared AI fleet with intelligent routing, so everyone benefits from the collective hardware. A team of five with MacBooks has 120–480GB of unified memory available through Herd.

Does Ollama Herd require Docker Desktop?

No. Herd installs via pip or Homebrew and runs as a lightweight Python service. No Docker Desktop subscription, no container runtime, no virtualization overhead. On Apple Silicon, this means the model talks directly to Metal/MLX with no container layer in between.

Is Ollama Herd free?

Yes. Open-source, MIT license. No paid tiers, no API keys, no subscriptions.

See Also