NVIDIA Personal AI Router (PAIR)

NVIDIA Personal AI Router (PAIR), shown as NVIDIA PAIR once installed, is a local inference router for a group of compatible computers on the same network. It discovers participating nodes, manages supported inference engines, and presents local proxy endpoints for Ollama-compatible, OpenAI-compatible, and Anthropic Messages API requests. Independent requests can be routed to eligible nodes according to engine availability, model availability, and current workload.

PAIR is useful for concurrent local workloads such as multi-agent applications. Prompts and responses are intended to remain on the local network when every configured client, model source, engine, and node is local.

PAIR routes each independent request to one node. It does not pool GPU memory, combine GPUs into a larger logical GPU, shard one model across machines, or split an in-flight inference request between nodes.

Two paired machines: requests arrive on one, run on whichever node suits each one, and both report live GPU and memory use throughout. [Watch the full clip](assets/pair-demo.mp4).

What is supported

PAIR running on a machine does not mean an engine will. PAIR itself runs on any supported Windows, Linux, or macOS machine. Each engine sets its own requirements for the operating system, GPU, and drivers, and each model needs enough memory to load. Whether a particular engine and model work on a particular machine is between that engine and that machine, so check the engine's own documentation before assuming a node can serve a model. A node only becomes a candidate for a request once it is actually running a compatible engine, and PAIR prefers the nodes it already knows hold the model.

Run it

• Open PAIR the way you would any application — the Start menu on Windows,

Launchpad or the Applications folder on macOS, your applications list on Linux. On a machine with no desktop environment, drive it from the [terminal interface](docs/terminal-interface.mdx) instead, which starts the same background services and gives you a full-screen view in the terminal.

• Let it finish starting. Overview shows this machine once the services

are up. If it stays on Starting service... or Fetching nodes, open Settings → Service and read the status there.

• Get an engine running. On the node's card, open Engine settings and