ai-cloud
Bare Metal Provisioning for AI Cloud Providers
Automate bare metal provisioning across GPU infrastructure. vMetal provides one Machine API over infrastructure drivers, while vCluster assigns dedicated tenant workers through Private Nodes.
Trusted by the fastest-growing AI cloud providers
Problem
Why GPU Deployments Stall at Scale
Manual provisioning slows revenue, wastes capacity, and exposes tenants to unnecessary risk.
Slow Server Setup Kills Revenue
Provisioning delays keep GPU capacity idle instead of serving tenant workloads.
Manual Processes Introduce Errors
Hand-configured PXE boots, OS installs, and network configs create inconsistencies that are difficult to debug across large GPU fleets.
Machine and Cluster Workflows Diverge
Most provisioning tools stop at the OS layer, leaving platform teams to stitch together k3s, kubeadm, and cluster orchestration themselves.
Solution
Zero-Touch Bare Metal Provisioning Built for GPU Clouds
vMetal provides one Machine API above bare metal and VM drivers. After infrastructure setup, it automates supported provisioning workflows, and vCluster uses the resulting capacity for dedicated tenant Private Nodes. vCluster Labs software powers 100K+ GPUs.
From Racked Servers to Tenant Clusters
Connect machine lifecycle automation with independent tenant control planes and dedicated production workers, using supported infrastructure drivers and integrations.
Bare Metal
Zero-Touch GPU Server Provisioning
vMetal exposes one Machine API above bare metal and VM provisioning drivers. Registered inventory, images and credentials enable repeatable machine lifecycle workflows for machine provisioning. Network automation uses supported integrations such as Netris.
- Stable Machine API
- Bare metal and VM provisioning
- Driver-specific lifecycle automation
Bare Metal Kubernetes
Kubernetes Directly on Bare Metal
vCluster Standalone runs Kubernetes as a CNCF-certified binary on Linux, without an existing Kubernetes cluster. It supplies a Kubernetes foundation for machine provisioning; vMetal separately orchestrates machine and OS provisioning.
- CNCF-certified Kubernetes binary
- Runs directly on Linux
- No existing Kubernetes cluster required
Dynamic Scaling
Automatic GPU Node Provisioning
Karpenter-based Auto Nodes requests worker capacity according to configured policies. With the vMetal provider, Machine requests provision available infrastructure for machine provisioning; inventory, driver readiness and release rules determine actual capacity.
- Karpenter-based node management
- Supported infrastructure provider integration
- Inventory-aware capacity policies
Tenant Isolation
Production-Grade Tenant Cluster Isolation
Each tenant has an independent Kubernetes API, data store and RBAC boundary. Lightweight control-plane hosting reduces dedicated server requirements for machine provisioning; Private Nodes keep production workers tenant-specific.
- Independent tenant API and data store
- Tenant-scoped scheduling on Private Nodes
- No dedicated control-plane servers per tenant
Network Isolation
Hardware-Enforced Per-Tenant Networking
Tenant-owned CNI configuration and supported Netris integrations provide separate network controls for machine provisioning. Ethernet segmentation can use VLANs, VRFs and ACLs; InfiniBand isolation uses fabric partitions rather than Ethernet constructs.
- Tenant-owned worker network configuration
- Netris integration for supported fabrics
- Explicit segmentation and access policies
Why vCluster
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.
100K+
GPUs Powered
50+
GPU Clouds & F500s
<45
Days to Launch
30K
GitHub Stars
Get Started in 3 Steps
1
Schedule a Demo
Talk to our team about your stack
2
Deploy vCluster
Deploy vCluster on your infra in minutes
3
Onboard Your Tenants
Go live with a hyperscaler-grade tenant experience in days
FAQs
What is zero-touch bare metal provisioning and how does vMetal deliver it?
vMetal exposes a stable Machine API above infrastructure-specific drivers for bare metal and VMs. Drivers handle supported provisioning mechanics such as imaging, registration and cleaning. Operators configure inventory, credentials and images before automation runs. vCluster can then use provisioned machines as dedicated Private Nodes, connecting the infrastructure lifecycle to the tenant cluster that needs the capacity.
Do I need an existing Kubernetes cluster to use vMetal?
vMetal requires vCluster Platform and a connected Kubernetes cluster for its Metal3/Ironic provisioning components. If you are starting without Kubernetes, vCluster Standalone can bootstrap that foundation as a binary on Linux. Once infrastructure drivers, hardware inventory, images and credentials are configured, vMetal can automate supported provisioning workflows and supply machines for tenant Private Nodes.
How does bare metal provisioning connect to tenant cluster orchestration?
vCluster gives each tenant an independent Kubernetes API, data store and RBAC scope. Private Nodes dedicate worker capacity to that tenant, including its own CNI and storage configuration. vMetal orchestrates the machines underneath. This separates tenant administration and worker placement; shared infrastructure, application permissions and network policies still require an explicit security design.
What GPU fleets and infrastructure scales has this been proven at?
vCluster Labs software powers 100K+ GPUs and 1M+ CPUs, serving 50+ GPU clouds & Fortune 500s combined. In production, Lintasarta operates 170+ tenant clusters, while Boost Run completed its managed Kubernetes launch in under 45 days from the decision. These named deployments provide scale and launch examples for teams evaluating the platform for their own infrastructure.
How does Auto Nodes handle GPU capacity scaling on bare metal?
Auto Nodes works like Karpenter for physical servers. When tenants schedule workloads that need more GPU capacity, it requests new bare metal nodes through the vMetal Machine API. Operations teams no longer step in every time a tenant needs more GPUs, so capacity can grow without headcount growing alongside it.
Can this stack run in air-gapped or compliance-restricted environments?
Yes. The vCluster Platform supports air-gapped and FIPS deployment for environments with strict compliance requirements. The full stack, including bare metal provisioning, Kubernetes control plane binary, and tenant cluster orchestration, can be deployed in disconnected environments without requiring outbound internet access. This makes it suitable for government, defense, and regulated enterprise deployments that require isolated infrastructure.
Launch Your GPU Cloud on Bare Metal
See how vMetal and vCluster Platform take GPU servers from rack to production-ready tenant clusters.
