Overview
PAIR — the Personal AI Router — is NVIDIA's Apache-2.0 tool for using more than one machine to serve local AI requests. It runs no models itself. Instead it discovers the compatible computers on the same network, keeps track of which inference engines and models each one has, and exposes Ollama-compatible and OpenAI-compatible endpoints that any existing client can point at. Each incoming request is routed to a single node that can serve it, based on which systems have capacity.
The important limit to understand up front is what PAIR does not do: it does not pool VRAM and it does not shard a model across machines. A model still has to fit on one node. What PAIR buys you is parallelism — when an agent fans a task out into several independent jobs, those jobs can land on different GPUs instead of queueing behind one. NVIDIA's own framing is an assistant that splits inbox triage across subagents while PAIR distributes the work over the PCs already sitting idle.
It ships as a public beta written in Go, with signed installers for Windows 11, Linux and macOS on both x64 and arm64, and mixed clusters are supported — a Windows desktop and a Mac can pair together. Supported hardware is GeForce RTX 20 Series and newer, RTX PRO workstation GPUs from Turing onward, DGX Spark, and Apple M4 or newer silicon. The supported inference engines at launch are Ollama and LM Studio.
What it does
- Automatic discovery of compatible machines on the local network, with pairing confirmed by a six-digit PIN
- Ollama-compatible and OpenAI-compatible endpoints, so existing agent and client code does not have to change
- Per-request scheduling to a single node based on which systems have an enabled engine, the model in place, and free capacity
- Heterogeneous clusters — Windows, Linux and macOS nodes can be paired with each other
- Ollama and LM Studio installed and managed per node from PAIR's own Engine settings
- Graphical and terminal interfaces, with .exe, .deb and .dmg installers
Getting started
PAIR is installed per machine, then the machines are paired with each other. Start with a single node and confirm a request works locally before adding a second one.
Install PAIR
Download the installer for the platform from the repository's releases. On Windows and macOS you double-click the .exe or .dmg and follow the prompts; on Linux install the .deb package.
sudo apt install ./NVPAIR-Setup-*.debAdd an inference engine and a model
Launch PAIR from the application menu. Install Ollama or LM Studio through the node's Engine settings, then pull a model with the Add model option. PAIR only routes to a node that already has the requested model.
Send a request
Point any Ollama- or OpenAI-compatible client at the endpoint. The README's example targets Ollama's default port.
curl http://127.0.0.1:11434/v1/chat/completions \
-H "Content-Type: application/json" \
-d '{"model":"qwen4:12b","messages":[{"role":"user","content":"In one sentence, what does a router do?"}]}'Pair a second machine
Open Settings → Cluster on the first machine to generate a six-digit PIN, then enter that PIN on the second machine. Once paired, requests can be scheduled onto either node.
Commands and code are distilled from the project's own documentation — always check the official repo for the latest.
When to use it
- Run an agent that fans a task out to several subagents without every job queueing on one GPU
- Put an idle desktop or a DGX Spark to work serving requests from a laptop that is short on VRAM
- Keep an entire local AI setup offline while still using more than one machine's worth of compute
- Give a household or small team one endpoint in front of several Ollama and LM Studio installs
How NVIDIA PAIR compares
NVIDIA PAIR alongside other open-source gateways & routing tools AI/TLDR tracks, ranked by GitHub stars.
| Tool | Stars | What it does |
|---|---|---|
| RTK | ★ 79.1k | A single-binary Rust CLI proxy that filters, groups, truncates and dedupes the output of 100+ dev commands before a coding agent reads it, cutting token use by 60–90%. |
| Headroom | ★ 69.1k | Local context-compression layer that shrinks tool outputs, logs, files and RAG chunks before they reach the model, usable as a library, a drop-in proxy or an MCP server. |
| OmniRoute | ★ 61.9k | A local-first AI gateway that fronts hundreds of model providers with one OpenAI-compatible endpoint, quota-aware auto-fallback, many routing strategies and prompt compression. |
| LiteLLM | ★ 58.2k | A Python SDK and proxy server that gives one OpenAI-compatible API to 100+ LLM providers, with cost tracking, budgets, fallbacks, rate limiting, and an admin UI. |
| Apache APISIX | ★ 17.1k | A cloud-native API gateway whose AI plugins add multi-provider LLM proxying, load balancing, retries and fallbacks, token-based rate limiting, and content moderation. |
| Portkey AI Gateway | ★ 12.9k | An LLM gateway that routes calls to 100+ providers through one API and adds logging, tracing, caching, and fallbacks for production AI traffic. |
| Higress | ★ 9.3k | An AI-native API gateway built on Istio and Envoy that proxies and governs traffic to many LLM providers, with token rate limiting, caching, and MCP server hosting. |
| NVIDIA PAIR | — | Turns the spare PCs on your home network into extra capacity for local model calls |