NVIDIA Open-Sources Run:ai and AI Factory Infrastructure at OCP Summit

KAI Scheduler, one of Run:ai's four components, has quietly been open source since April 2025 under Apache 2.0 as a CNCF Sandbox project ^[3]. What changed on October 13, 2026 is the release of the other three pieces as a single platform: the GPU Fractioning Operator, which replaces Run:ai's prior proprietary fractional-GPU code with CUDA 13.4-native fractioning enforced directly by the CUDA driver ^[2]; KAI Resource Management; and Workload Map, a standalone Go library that treats Kubernetes workload types like PyTorchJob and RayCluster as first-class objects without itself scheduling anything ^[2]. NVIDIA's own announcement confirms that no paid Run:ai subscription or NVIDIA support entitlement is required to use any of the newly open components ^[1].

The framing that best explains NVIDIA's motive is the idea of closing the scarce layer while opening the abundant one ^[4]: orchestration software is easy to replicate, so NVIDIA gives it away, while GPUs and paid enterprise support stay scarce and monetized. The competitive backdrop reinforces this - Run:ai's prior commercial list price ran about $2,600 per GPU per year, while free alternatives like Kueue already offered comparable quota-borrowing features, making the paid license increasingly hard to defend ^[5]. Giving away the code also lets cloud partners package and test it without licensing friction ^[5], while NVIDIA keeps the GPUs themselves, and paid enterprise support, as the layer it still monetizes ^[4]. The payoff for partners is already measurable: Nebius reports that fractional GPU allocation can deliver 77% of full-GPU throughput while supporting 86% of the concurrent users a dedicated allocation would, with co-located models pushing combined throughput past 350,000 tokens per second ^[3].

NVIDIA didn't open-source Run:ai in isolation - it landed inside a broader hardware disclosure at the OCP Global Summit in San Jose on October 12-13, 2026, where NVIDIA contributed Vera Rubin rack and compute-tray designs to the Open Compute Project through the MGX 1.2 architecture, alongside new networking and power partnerships with Meta, Google, Cisco, and Visionbay ^[6]. NVIDIA framed the hardware side explicitly as a deployment-speed problem, stating the real bottleneck for the industry is how fast the world can manufacture and deploy AI factories ^[6]. NVIDIA also touted that its new Vera CPUs run roughly twice as fast as the prior Grace generation across several workloads, including a 1.8x gain on Terminal-Bench, a benchmark built around agentic tool-use tasks ^[6]. Pairing the software giveaway with open rack and networking specs - MGX 1.2's 250 kW racks, Cisco's USFP optics, Spectrum-6 switches - turns one week into a full-stack open-standards pitch rather than a single product announcement ^[7].

Run:ai's own founders said at the time of NVIDIA's 2024 acquisition that they wanted the software eventually open-sourced to extend its reach beyond NVIDIA GPUs ^[9], and NVIDIA completed that acquisition in December 2024 after an eight-month regulatory review ^[10]. But the goodwill reading sits uneasily next to NVIDIA's separate December 2025 acquisition of SchedMD, maker of the Slurm scheduler used on an estimated 60% of the world's supercomputers ^[8]. Analysts quoted on that deal are explicitly wary of NVIDIA's expanding footprint across GPU scheduling software generally - one noted that Slurm's open-source foundation offers safeguards such as transparent code, forking ability, and community governance, while another warned that the skepticism that NVIDIA may prioritize its own hardware in future software updates is a feasible outcome ^[8]- a caution that applies just as easily to a newly-open Run:ai as it does to Slurm.

The strongest external validation for NVIDIA's open-standards framing didn't come from NVIDIA at all - it came from AMD. In a keynote delivered at the same OCP Global Summit, AMD CEO Lisa Su argued that no single company has every answer and that pooling the best of multiple companies is how the industry moves faster, an argument for open collaboration that lines up with NVIDIA's own rationale for handing over Run:ai. NVIDIA's own framing of the stakes leans on efficiency economics rather than altruism: in material describing its DSX AI Factory platform, the company ties AI factory revenue directly to power efficiency, arguing that every unused watt is lost revenue. Grassroots reaction lagged behind the corporate messaging. In the announcement's first day, dedicated discussion of the OCP news stayed close to zero engagement on Reddit, and the only Run:ai-adjacent post to draw real comments was a KAI Scheduler how-to in r/kubernetes focused on a different use case than the announcement itself - a sign the practitioner audience most likely to actually deploy these tools hadn't caught up with the news yet.