Supported Providers
On this page
Modelplane is built on Crossplane and shares its infrastructure providers, so the set of clouds and neoclouds it reaches grows alongside Crossplane itself. This page shows where Modelplane runs today and where it’s headed.
A provider can show up here in three ways:
Note
- Provisioning supported. Modelplane creates and manages the whole cluster
from an
InferenceCluster, selected throughprovisioning.provider. GKE and EKS work this way today. - Bring your own supported. Register a cluster you already run with
source: Existing. This works on any provider whose Kubernetes meets Modelplane’s requirements (Dynamic Resource Allocation and a recent Kubernetes version), so you can run on the providers below now, ahead of native provisioning. - Crossplane provider exists. A Crossplane provider is published for the cloud. That provider is the path by which native provisioning lands, so it marks where Modelplane can grow next.
Clouds and neoclouds
Listed alphabetically, spanning hyperscalers and GPU-specialist neoclouds. Each runs a managed Kubernetes service with GPU node pools, so the bring-your-own path covers them all today. Where a Crossplane provider exists, it’s the path to native provisioning.
NVIDIA
Trainium
AMD
TPU
Note
On-premises and bare metal. Bring an on-prem cluster the same way as any
other: stand up Kubernetes on your own hardware (like NVIDIA DGX BasePOD
or SuperPOD) with NVIDIA Base Command Manager, Run:ai, or your own tooling, then
register it with source: Existing. Provisioning it for you is on the roadmap
too. Modelplane can drive NVIDIA Base Command Manager or other bare-metal
Kubernetes provisioners through Crossplane, the same pattern it uses in the
cloud.
Tip
Don’t see your cloud or neocloud, or want to be added? Open an issue and we’ll track it.