<- all tokdocs

NVIDIA's Personal AI Router Turns Your Home Computers Into One Local Inference Pool

Watch on TikTok

View on TikTok ->

NVIDIA released Personal AI Router (PAIR), an open source tool that links the computers on your home network into a shared pool for local AI inference, with no cloud connection required. The video is a 31-second walkthrough of the project's GitHub README. When you send a request, the router picks the best available machine on the network to handle it, so you get more usable compute than any single laptop provides while your prompts and responses stay on the local network.

What PAIR Actually Does

The video scrolls through the README at github.com/nvidia/personal-ai-router, which describes PAIR as a local inference router for a group of compatible computers on the same network. It discovers participating nodes, manages supported inference engines, and presents Ollama-compatible and OpenAI-compatible proxy endpoints to applications and agents. Requests are routed to eligible nodes based on engine availability, model availability, and current workload. The project carries an Apache-2.0 license and a security policy, both visible as badges in the frames.

Routing Requests, Not Merging GPUs

The README includes a limitation worth noting, shown clearly in several frames. 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. So this will not let you run a model too large for any single machine you own. The stated sweet spot is concurrent local workloads such as multi-agent applications, where many independent requests can fan out across the network.

The Dashboard in Action

Most of the video lingers on a screenshot of the PAIR desktop app showing two paired machines. One node runs an NVIDIA GeForce RTX 5090 alongside an AMD Ryzen 7 9800X3D, the other is an NVIDIA GB10 ARM box with 128 GB of memory. A queue of qwen3:0.6b jobs sits on the left, each tagged with the node it was routed to, while live charts track GPU usage, VRAM, and memory on both machines. The caption under the screenshot explains that requests arrive on one machine, run on whichever node suits each one, and both report live resource use throughout.

Platform Support

The "What is supported" table appears in the later frames. PAIR runs on Windows 11, Linux, and macOS, on both x64 and arm64, with Windows on ARM marked experimental. Installers ship as a Windows .exe, a Linux .deb, and a macOS .dmg, and other Linux distributions can build from source. Nodes on different operating systems can all be paired with each other. Supported inference engines are Ollama and LM Studio. The README also cautions that installing PAIR on a machine does not mean an engine will run there. Each engine sets its own OS, GPU, and driver requirements, and each model needs enough memory to load.

Why This Matters for Home Labs

The pitch in the narration is simple. If you already own several capable machines, PAIR lets you use them together for local AI instead of renting a server or sending data to a cloud API. Privacy is the other draw. Prompts and responses stay on the local network when every configured client, model source, engine, and node is local. Because the proxy endpoints mimic Ollama and OpenAI APIs, existing tools and agents can point at the router without code changes.

Key Takeaways

  • NVIDIA Personal AI Router (PAIR) is an open source, Apache-2.0 licensed router that spreads local AI inference requests across computers on the same network.
  • It exposes Ollama-compatible and OpenAI-compatible endpoints, so existing apps and agents can use the pool without modification.
  • It routes whole requests to single nodes. It does not merge GPUs or shard a model across machines, so it suits many concurrent requests rather than one oversized model.
  • It supports Windows 11, Linux, and macOS on x64 and arm64, with cross-OS pairing, and works with Ollama and LM Studio as engines.
  • Prompts and responses stay on the local network when all configured components are local, which keeps data private without renting cloud compute.

Resources

Published September 5, 2026. Writeup generated from a favorited TikTok.