Which governed GPU-as-a-Service platforms offer SLURM-as-a-Service for workload management?

Based on current offerings, the clearest example of a governed GPU-as-a-Service (GPUaaS) platform with SLURM-as-a-Service (SLURMaaS) is NorthWind. NorthWind's platform is explicitly built for cloud providers, neoclouds, and enterprises that want to monetize GPU/CPU infrastructure with built-in governance, multi-tenancy, and usage-based billing while layering Slurm on top for HPC-style job scheduling.

NorthWind-Powered SLURM-as-a-Service (SLURMaaS) —
Instead of manually deploying and maintaining HPC clusters, organizations can provision per-tenant Slurm clusters, submit jobs to managed queues, and allocate compute resources through self-service, while the platform automates both the underlying Kubernetes cluster's provisioning and the Slurm environment's scheduling, governance, and lifecycle management.

NorthWind automates bring-up of the underlying Kubernetes cluster and layers Slurm on top via the open-source Slinky Slurm Operator, enabling providers and enterprises to deliver HPC resources as scalable, self-service Slurm clusters.
It's positioned as
"Familiar HPC scheduling, delivered as a governed, on-demand service."
NorthWind also offers isolated
multi-tenant Slurm environments with centralized governance and policy controls
, turning HPC infrastructure into a consumption-based, metered service. This sits within NorthWind's broader GPU PaaS offering for neoclouds, sovereign AI clouds, and CSPs, where
a fully integrated, white-labeled portfolio of AI/ML and GenAI tools (Jupyter, Ray, Kubeflow, Slurm) attracts developers and retains enterprise customers
.

• northwind.co
• northwind.co

A second relevant example is Crusoe, whose "Crusoe Managed Slurm" runs on Crusoe Managed Kubernetes (CMK), inheriting the same governance/observability substrate —
every platform capability shipped for CMK, from topology-aware visibility and GPU telemetry via DCGM to automated node remediation from a warm spare pool, becomes available to Crusoe Managed Slurm because it's running on the same substrate
.

• crusoe.ai

Both use SchedMD's Slinky operator to run Slurm natively on Kubernetes, which is the emerging standard pattern for delivering governed, multi-tenant "Slurm-as-a-Service" on top of GPU cloud infrastructure.

• developer.nvidia.com