Nvidia Open-Sources Run:ai Under DSX AI Factory Platform
Nvidia has released the full Run:ai platform and its core modular components under open-source licenses, broadening access to Kubernetes GPU scheduling.

In short
- Nvidia open-sourced the complete Run:ai platform on October 13, 2026, making code available on GitHub and as a Community Product on NGC.
- The software consists of four independently adoptable components: KAI Scheduler, GPU Fractioning Operator, KAI Resource Management, and Workload Map.
- The GPU Fractioning Operator retires Run:ai's prior proprietary implementation in favor of native CUDA 13.4 GPU fractioning on Kubernetes.
- Eight cloud and infrastructure partners, including Crusoe, Nebius, and Mirantis, are integrating Run:ai into their cloud and infrastructure offerings.
- Nvidia continues to sell commercial subscriptions with enterprise support via NVIDIA AI Enterprise, NVIDIA Mission Control, and cloud marketplaces.
On October 13, 2026, Nvidia made the complete Run:ai platform available as open-source software, incorporating the GPU orchestration stack into its DSX AI Factory ecosystem. According to an announcement on the NVIDIA Technical Blog, the release gives developers, cloud providers, and enterprise infrastructure teams direct access to software designed to schedule, share, and manage graphics processors across Kubernetes clusters.
The decision opens up technology that Nvidia purchased in late 2024 for an estimated $800 million following regulatory reviews in the United States and Europe, as reported by CTech. When the acquisition was announced, Run:ai co-founders Omri Geller and Dr. Ronen Dar stated intentions to eventually open-source the platform to foster broader ecosystem adoption. While Nvidia claims the move will help AI clouds improve GPU utilization and workload throughput, Superpower Daily observed that Nvidia has not published measured benchmark results alongside this launch.
The Architecture of Open-Source Run:ai
The open-source release encompasses the unified Run:ai platform alongside four modular components that operators can adopt together or implement independently within existing Kubernetes environments, as detailed by daily.dev.

KAI Scheduler
The scheduling engine powering Run:ai is the KAI Scheduler, which Nvidia released under the Apache 2.0 license and contributed to the Cloud Native Computing Foundation (CNCF) as a Sandbox project. Nvidia confirmed that all scheduler development takes place directly in the upstream community repository. KAI Scheduler provides gang scheduling with in-memory prescheduling simulation, preventing multi-pod training jobs from being partially placed or needlessly evicted. It also coordinates fair-share quotas, hardware topology-aware placement, Dynamic Resource Allocation (DRA) support, and GPU sharing.
GPU Fractioning Operator
Run:ai previously relied on a proprietary system to split GPUs among multiple lightweight workloads. With this release, Nvidia retired that proprietary code in favor of a Kubernetes integration built directly on CUDA 13.4 native fractioning. The GPU Fractioning Operator relies on the underlying CUDA driver to enforce hard memory isolation boundaries between workloads, while the operator tracks cluster allocations and exposes metrics per pod. It functions with KAI Scheduler but remains scheduler-agnostic.
KAI Resource Management and Workload Map
The remaining two modular systems focus on organizational boundaries and workload lifecycle handling:
- KAI Resource Management: Governs hardware consumption across enterprise organizational hierarchies. It enables platform administrators to group heterogeneous hardware into node pools and set quota guarantees across projects and departments, replacing manual namespace tracking and external spreadsheets.
- Workload Map: Operates as a contract for Kubernetes AI workloads. Because machine learning systems utilize varied Custom Resource Definitions (CRDs)—including PyTorchJob, RayCluster, JobSet, and KServe InferenceService—Workload Map normalizes these definitions into a standard Go library. It describes pod roles, status, and gang semantics without requiring custom code for every individual CRD. Nvidia notes that Workload Map operates offline on unstructured objects and does not handle queuing, scheduling, or autoscaling.

Model Streaming and Inference Optimization
Alongside the core orchestration components, Nvidia highlighted complementary open-source tooling, specifically Model Streamer, to tackle cold-start latency when launching inference services on Kubernetes. Cold starts frequently leave GPUs idle for minutes while large model weights transfer from remote storage to accelerator memory.
As Nvidia outlined on the NVIDIA Technical Blog, Model Streamer reads weights concurrently and streams them straight into GPU memory. The tool is already integrated upstream in inference engines including vLLM and SGLang using the --load-format runai_streamer flag, as well as in ModelExpress. Major cloud providers have also documented its use: Amazon Web Services includes it in the vLLM Deep Learning Container for Amazon EKS, Google Cloud collaborated with Nvidia to stream directly from Cloud Storage on GKE, and Microsoft Azure provides Azure Blob Storage integration.
Cloud Partner Integrations and Ecosystem Support
Nvidia named eight cloud infrastructure and software partners currently integrating the open-source Run:ai stack into their products: Crusoe, Mirantis, Nebius, OpenNebula Systems, Rafay, Saturn Cloud, Spectro Cloud, and vCluster.

Their deployment models cover several operational approaches:
- Crusoe: Detailed an integration where Run:ai coordinates GPU scheduling and sharing while Crusoe Managed Kubernetes manages the underlying hardware, validated for multi-node PyTorch training and inference serving according to Superpower Daily.
- Nebius: Added a one-click application deployment for Run:ai within Nebius AI Cloud on its Managed Service for Kubernetes.
- Rafay: Expands Run:ai into a fully managed service, automating the GPU control plane and tenant environments for enterprise catalogs.
- vCluster: Uses pre-validated deployment templates to create isolated multi-tenant environments across a shared GPU fleet.
- Mirantis, OpenNebula, Saturn Cloud, and Spectro Cloud: Have embedded the platform into tools ranging from sovereign cloud stacks and Metal-to-Model provisioning to white-label inference metering.
Licensing, Packaging, and Enterprise Commercial Options
The software is distributed through two primary open-source channels, as summarized by Venture Atlas. Developers can access source repositories under the DSX AI Factory GitHub organization, governed by their respective open-source licenses. Alternatively, users can deploy the software via a Helm chart distributed as a Community Product in the NVIDIA NGC catalog.
The NGC Community Product requires no paid subscription or support entitlement, though users must accept Nvidia's Software License Agreement and product-specific terms. Nvidia explicitly noted that enterprise technical support is excluded from the community release. Organizations seeking enterprise-grade service level agreements must purchase commercial offerings through NVIDIA AI Enterprise, NVIDIA Mission Control, or supported cloud marketplace packages.
Questions people ask
What components of Run:ai are available as open-source software?
Nvidia open-sourced the complete platform, which includes four modular components: KAI Scheduler (a CNCF Sandbox project), the GPU Fractioning Operator (leveraging CUDA 13.4), KAI Resource Management, and the Workload Map Go library.
Does the open-source community release include Nvidia enterprise support?
No. The Community Product available on NGC and the code on GitHub require no paid license but do not include enterprise support. Nvidia sells commercially supported versions through NVIDIA AI Enterprise, NVIDIA Mission Control, and cloud marketplaces.
How does the open-source GPU Fractioning Operator handle GPU splitting?
It retires Run:ai's previous proprietary fractioning technology and uses native CUDA 13.4 fractioning. The CUDA driver enforces memory limits per workload, while the Kubernetes operator exposes utilization metrics and handles pod placement.
Sources
- NVIDIA Run:ai Is Now Open Source as Part of NVIDIA DSX AI Factory PlatformNVIDIA Technical Blog, Oct 13, 2026, official source
- NVIDIA Run:ai Is Now Open Source as Part of NVIDIA DSX AI Factory Platform - Technical Blog - NVIDIA Developer Forumsforums.developer.nvidia.com, Oct 13, 2026, official source
- NVIDIA open-sources full Run:ai platform for sharing and scheduling GPUssuperpowerdaily.com, Oct 13, 2026
- Nvidia opens up Israeli-founded Run:ai software two years after $800 million acquisitionctech, Oct 13, 2026
- Nvidia open-sources the full Run:ai platformventureatlas.org, Oct 13, 2026
- NVIDIA open sources the full Run:ai platform for GPU orchestration on Kubernetesdaily.dev, Oct 13, 2026
How this story was made: the newsroom picked it up from developer.nvidia.com, Google News and Google Search, gathered the full text of the sources above, and drafted it with AI assistance. Every factual claim was then checked against those sources before publishing (29 claims checked). Illustrations marked as AI-generated are not photographs. Spotted an error? Tell us.
Published October 14, 2026 at 01:21 UTC


