NVIDIA has released PAIR, a free open-source Personal AI Router designed to spread local AI inference requests across compatible computers on the same network. The beta is aimed at people who already run models locally through tools such as Ollama or LM Studio and have more than one capable machine available.
PAIR does not turn several GPUs into one giant virtual GPU. NVIDIA describes it as a router for independent inference requests: a client can send work to another paired machine with spare capacity, while each request still runs within the memory and compute limits of the host that receives it. That distinction matters for anyone hoping to use PAIR to load a model that is too large for every individual device.
What PAIR cannot combine
The biggest limitation is memory. PAIR does not pool VRAM across machines, split a single model across several hosts or make one oversized inference job fit where it otherwise would not. Each routed request must still fit on the machine that runs it.
NVIDIA's launch post includes a demonstration in which a three-device setup completed a batch of independent tasks faster than a single system. That is a vendor demonstration, not a universal performance guarantee: results will depend on the models, hardware, network and how much parallel work is actually available.
For local-AI users, the useful change is therefore orchestration rather than magic extra memory. PAIR gives compatible machines a common routing layer and can reduce idle hardware when several independent requests are waiting. NVIDIA has released it as a beta, so users should expect the feature set and compatibility details to evolve as the project develops.
PAIR also leaves the model-serving tools in place rather than replacing them. NVIDIA says the router works with existing Ollama and LM Studio endpoints, which should make it easier to add a second machine without rebuilding a local workflow from scratch. The company also describes pairing as local-network based rather than a public cloud service. That is useful for privacy-sensitive experiments, but it does not remove the normal responsibility to secure the computers, models and data on the network.
Because the project is still in beta, the sensible approach is to test it with non-critical workloads first and verify how requests are distributed on your own hardware before depending on it for a regular production workflow.
Reporting notes