Skip to content

ADOPTERS.md

Latest commit

 

History

History
55 lines (38 loc) · 4.06 KB

ADOPTERS.md

File metadata and controls

55 lines (38 loc) · 4.06 KB

KAI Scheduler Adopters

This document lists organizations that have adopted KAI Scheduler — either to run their own workloads on Kubernetes, or to integrate it into the products and services they offer.

If your organization is using KAI Scheduler, we would love to have you listed here! Check out Add Your Organization below to get started.

Adoption Phases

  • Evaluation: Evaluating KAI Scheduler for fit against infrastructure and feature requirements.
  • Staging: Adopted; rolling out in pre-production or staging environments.
  • Production: Running KAI Scheduler in production.

Organization Types

  • End User: Uses KAI Scheduler to manage internal workloads or services.
  • Platform / Provider: Integrates KAI Scheduler into a product, managed service, or platform offered to customers.

Adopters

Listed alphabetically.

Organization Contact (GitHub) Reference Phase Type
Cantina @sam-huang1223 KubeCon EU 2026: GPU Reservations Production End User
Lightning AI @tchaton KubeCon EU 2026: GPU Reservations — Platform / Provider
NVIDIA Run:ai — KAI was originally developed within the Run:ai platform and continues to be packaged and delivered as part of the NVIDIA Run:ai platform, used in production by enterprises across financial services, education, healthcare, defense and more Production Platform / Provider
OSMO — A platform for scaling Physical AI workloads across heterogeneous compute — unifying training GPUs, simulation clusters, and edge devices. See KAI Scheduler configuration. Production End User & Platform / Provider

Integrations

Projects that ship a KAI Scheduler integration. Listed alphabetically.

Project Link
Elotl Integration
Kubeflow Integration
KubeRay Integration
NVIDIA Cloud Functions (NVCF) NVCF integration
NVIDIA Dynamo Dynamo integration
vCluster Integration
ZenML Integration

Add Your Organization

Are you using KAI Scheduler? We'd love to hear from you. Open a Pull Request against this file (ADOPTERS.md) adding a row with:

  • Organization name
  • Contact — GitHub handle of someone we can reach out to
  • Reference — link to a blog post, talk, integration, or short description of your use case (optional but appreciated)
  • Phase — Evaluation, Staging, or Production
  • Type — End User, Platform / Provider, or both

If you'd prefer not to be listed publicly, we're happy to hear from you privately instead — see MAINTAINERS for contact details.

This list is community-maintained. Entries may be updated or removed if they become stale; if your organization's status changes, please open a PR.