On October 13, 2026, NVIDIA released the full Run:ai GPU orchestration platform as open source, inside its new DSX AI Factory GitHub organization. Most coverage stopped at "NVIDIA open-sources Run:ai." The details matter more than the headline, so here is what shipped, why platform teams care, and what the announcement leaves out.
What happened
NVIDIA published the complete Run:ai platform code plus four components you can adopt on their own:
- KAI Scheduler: the Kubernetes-native scheduler behind Run:ai. Gang scheduling, fair-share and quotas, topology-aware bin-packing, GPU sharing (MIG, MPS, time slicing, HAMi) and Dynamic Resource Allocation support. Apache 2.0 and a CNCF Sandbox project.
- GPU Fractioning Operator: wires CUDA-native GPU fractions into Kubernetes, with a per-pod metrics exporter. It is scheduler-agnostic.
- KAI Resource Management: projects, departments, hierarchical quotas and node pools.
- Workload Map: a Go library that describes PyTorchJob, RayCluster, JobSet, KServe and custom CRDs once, so tools can schedule and observe them without hardcoding each type.
A Helm-installable "Community Product" build is also on NVIDIA NGC. Eight partners, including Crusoe, Mirantis, Nebius, Rafay, Spectro Cloud and vCluster, announced integrations the same day.
Why people care
GPU time is the most expensive line on most AI infrastructure bills, and plain Kubernetes was not designed to share GPUs fairly between teams. Until now, the org layer (who gets what share of the cluster) and fractional GPUs were the paid parts of Run:ai. Both are now code anyone can read, fork and run.
What could change
- Smaller AI clouds and internal platform teams get a production-tested quota and fair-share layer without a commercial contract. NVIDIA's own example: guarantee 50% of a cluster to research without letting any other team grab the rest.
- Fractional GPUs for notebooks and small models become easier to justify, because sharing no longer depends on a proprietary driver hook.
- Tooling vendors may converge on Workload Map instead of writing a private integration per CRD. That one is a prediction, not a fact: watch its ADOPTERS file.
What most coverage misses
- The fractioning code was retired, not opened. NVIDIA says its proprietary fractional-GPU implementation has been retired in favour of native fractions in CUDA 13.4. The new operator is the Kubernetes glue for that driver feature, so check your CUDA and driver versions before planning around it.
- Free does not mean supported. The NGC Community build needs no Run:ai subscription, but NVIDIA states that enterprise support is not included, and downloading it means accepting NVIDIA's software license terms on top of the open source licenses.
- KAI Scheduler was already open. It went Apache 2.0 earlier; the genuinely new code is the platform layer, resource management, Workload Map and the operator.
- You do not need the whole stack. NVIDIA says KAI Scheduler can run in an existing cluster alongside your current software, and Workload Map works offline on unstructured objects.
Facts vs predictions
Facts: the repositories, the four components, the CUDA 13.4 change, the NGC support terms and the partner list are all in NVIDIA's technical blog. Predictions: wider adoption by smaller clouds and convergence on Workload Map. Nobody has public adoption numbers yet.
Where to start
If you run shared GPU nodes today, start with KAI Scheduler alone in a staging cluster, then try the fractioning operator on notebook workloads once your nodes are on a CUDA 13.4 capable driver.
Sources: NVIDIA Technical Blog, Oct 13, 2026 · dsx-ai-factory/run-ai on GitHub
Which part would you actually adopt first: the scheduler, the quotas or the GPU fractions?
This post was drafted with AI assistance and reviewed and edited by the Clydara team.
Top comments (0)