Skip to content
Machines & local modelsstrong signalverified

NVIDIA's free PAIR beta sends local inference to whichever machine on your network is free

NVIDIA published the Personal AI Router at IFA 2026 on September 3, 2026. It is a free, open source tool for Windows, macOS, and Linux that finds compatible machines on your local network and routes each independent inference request to one that has capacity, so parallel agent subtasks stop queueing behind a single GPU. It works with Ollama and LM Studio, and supports GeForce RTX 20 Series and newer, RTX PRO workstation cards, DGX Spark, and Apple M4 silicon. What it does not do is pool memory, so a model that does not fit on one machine still does not fit.

By Redakcija WebAiRadarPublished 2 min readwritten by a model
Image: NVIDIA

Much of the appeal of running models locally disappears when four agent subtasks all queue behind the same graphics card. NVIDIA's answer, published at IFA 2026 on September 3, 2026, is a free, open source tool called Personal AI Router, or PAIR. It discovers compatible machines on the local network and routes each independent inference request to a system with capacity, adapting as devices join and leave.

What it does

PAIR gives your apps and agents a single local endpoint and proxies requests behind it. At launch it supports two backends you probably already run, Ollama and LM Studio, and it ships with both a graphical and a terminal interface on Windows, macOS, and Linux. Setup, as NVIDIA describes it, is installing the tool on each machine, pairing them on the same network, and pointing your app at the endpoint.

The privacy argument follows from the design rather than from a policy. NVIDIA says prompts, files, and agent context stay on your local network instead of going to a cloud inference service, and the tool needs no internet connection to operate. You only need one to download models.

  • GeForce RTX 20 Series GPUs and newer.
  • RTX PRO workstation GPUs, Turing architecture and newer.
  • NVIDIA DGX Spark.
  • Apple M4 silicon or newer.

What it does not do

This is the part worth reading twice before you plan around it. The machines stay separate systems handling parallel tasks, and PAIR does not combine them into one virtual GPU. A model that does not fit in the memory of a single machine on your network still does not fit; adding a second PC buys you throughput on independent requests, not headroom for a bigger model.

The rest of the fine print is ordinary beta fine print. The tool is in beta, its interface is English only, it asks for 8 GB of system memory or more, and NVIDIA recommends 20 GB of disk space.

What shipped alongside it

The same post carries inference numbers, and they are the vendor's own measurements rather than an independent benchmark. They arrive through the backends most people use locally, so you get them by updating rather than by changing anything.

  • llama.cpp: up to 1.9x higher throughput on a GeForce RTX 5090, from kernel optimizations, better speculative decoding, and faster prefill, according to NVIDIA.
  • vLLM: 1.2x on an RTX PRO 6000 Blackwell Workstation Edition and up to 1.4x on two clustered DGX Spark systems, according to NVIDIA.
  • NVIDIA RTX Spark Windows PCs arrive in October 2026.
PAIR doesn't combine them into one virtual GPU.
NVIDIA, PAIR FAQ

Sources

Related

LLAMA.CPP0.4.0four architectures, one new transport
Machines & local modelsmedium signal

llama.cpp 0.4.0 adds four model architectures, an Apple RDMA transport, and video flags

The 0.4.0 release landed on September 4, 2026, and it is a numbered version rather than one of the nightly builds. It adds initial support for Qwen3.8-Flash-Next, NVIDIA Nemotron-3-Puzzle-75B-A9B, DSpark on Nemotron 3.5, and nanbeige4.2-3B. Apple RDMA becomes an RPC transport, video arrives as command-line options, and the quantizer gains a memory ceiling. Two server defaults changed, and saved session state carries a new version number.

llama.cppverified

Machines & local modelsstrong signal

Hugging Face published 207 WebGPU kernels and a loader that pulls them from the Hub

The @huggingface/kernels package downloads one GPU operation from the Hub and runs it in a browser that supports WebGPU. All 207 kernels are Apache-2.0, and each one is published with its interface contract, correctness cases, and benchmark cases in the same repository. Hugging Face compared them with ONNX Runtime Web 1.30.0 on an Apple M4 GPU and reports a 2.57x geometric mean speedup across 809 comparable cases. The timings cover work on the GPU alone, for single operations rather than whole models.

Hugging Faceverified

LLM inference in C/C++. Contribute to ggml-org/llama.cpp development by creating an account on GitHub.
Machines & local modelsmedium signal

llama.cpp spent two days on long context, and the gains landed on three different backends

Between August 29 and 31, 2026, llama.cpp shipped a run of changes that all point at the same place: the part of inference that gets slower as the context grows. Vulkan, CUDA and the Metal and OpenCL paths each got their own fix, with numbers the authors published. Three crashes were closed alongside them. None of it needs a flag; it arrives with the next build.

llama.cppverified