Give tenants a turnkey UI and CLI, or put your own portal and brand in front of vCluster APIs. Private Nodes are the production default for paying tenants, with a dedicated control plane and RBAC for each tenant cluster.
Manual tenant provisioning slows onboarding and makes policy harder to apply consistently.
Ticket-based provisioning adds avoidable handoffs between customers and infrastructure teams.
Namespace-only designs share control-plane and node-level components, which is unsuitable for untrusted tenants.
Building a separate management stack for every tenant increases operational work and fragments policy.
vCluster Platform gives tenants a self-service path to approved cluster products. Each production tenant receives Private Nodes and an isolated control plane, while operators retain control of templates, access, and capacity.
vCluster combines self-service cluster delivery with hard tenant isolation and centralized fleet operations.
Tenants create approved cluster products through the built-in UI and CLI, or through a custom portal backed by vCluster APIs.
Each tenant cluster gets its own virtualized Kubernetes control plane, API server, and RBAC boundary.
Private Nodes dedicate worker capacity, networking, and storage to each production tenant cluster.
Tenants receive cluster-admin inside their own environment, including control of CRDs and RBAC, without access to the control plane cluster.
Manage tenant clusters through one UI, CLI, and API with templates, quotas, policy, SSO, and fleet observability.
This isn’t a side project. Behind every vCluster deployment is 5+ years of deep K8s engineering, security hardening, and battle-tested infrastructure work at massive scale.
Talk to our team about your stack
Deploy vCluster on your infra in minutes
Go live with a hyperscaler-grade tenant experience in days
Self-service tenant cluster provisioning lets customers create approved cluster products through a portal, CLI, or API. vCluster Platform applies templates, access rules, and capacity policy without routing every request through the infrastructure team.
Each tenant cluster gets its own virtualized control plane and RBAC boundary. Private Nodes are the production default for external tenants and assign dedicated worker nodes with tenant-scoped networking and storage.
The platform can offer managed Kubernetes, Slurm, Run:AI, Ray, and other cluster products according to the templates you publish. Run:AI remains responsible for its scheduling capabilities, and Slurm remains responsible for Slurm scheduling.
vCluster provides a turnkey tenant UI and CLI, plus APIs for teams that want to build their own customer experience. Templates and policy let operators standardize what tenants can create.
Yes. vCluster Platform supports API-driven workflows and integrates with tools such as Terraform and Argo CD, so teams can manage tenant cluster definitions through established automation.
One vCluster Platform instance can manage connected control plane clusters across regions and infrastructure environments. Tenants use the same self-service experience while operators manage policy, capacity, and access centrally.
See how vCluster Platform delivers isolated tenant clusters on your GPU infrastructure.
