vMetal exposes bare metal servers and VMs through one stable Machine API. Interchangeable compute and network drivers handle provisioning and lifecycle operations, while vCluster turns that capacity into tenant cluster products.
GPU server provisioning becomes difficult when every infrastructure stack exposes a different lifecycle and API.
Selling raw compute alone gives customers no consistent machine or tenant cluster experience.
Manual OS installation, network setup, and cluster registration slow the path from available hardware to usable capacity.
Air-gapped and regulated environments need machine provisioning that runs on infrastructure the operator controls.
vMetal presents one stable Machine API for physical and virtual servers. Infrastructure drivers handle provisioning, and released capacity returns to inventory for reuse.
vMetal provides the Machine API and lifecycle layer. vCluster consumes those Machines as tenant cluster capacity.
With the Metal3 driver, vMetal provisions a bare metal server, installs the selected OS image, applies network configuration, and tracks the Machine lifecycle through one stable API.
Auto Nodes can create and delete Machine requests to maintain Private Node capacity for tenant clusters.
vCluster consumes provisioned Machines as Private Nodes, assigning dedicated worker capacity to one production tenant cluster at a time.
When Netris is configured with Metal3, separate network environments can receive hardware-backed L2 isolation.
vCluster Platform supports air-gapped deployments and FIPS features on supported plans for infrastructure operated in controlled environments.
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
vMetal is the physical and virtual Machine provisioning and lifecycle layer of vCluster Platform. A Machine is a claim on one server, and the selected driver handles the infrastructure-specific provisioning work behind a stable API.
vMetal is designed for infrastructure that the operator controls, including on-premises bare metal. Air-gapped and FIPS requirements should be implemented through the supported vCluster Platform deployment options and the selected infrastructure drivers.
vMetal provisions Bare Metal Machines and Virtual Machines. vCluster consumes that capacity through Private Nodes and turns it into managed Kubernetes, Slurm, Ray, inference, and other tenant cluster products.
Auto Nodes is a vCluster consumption workflow. It creates and deletes Machine requests through vMetal to maintain configured Private Node capacity based on static counts or supported resource requirements.
Provisioning time depends on server state, the selected driver, OS image, network setup, and startup automation. vMetal keeps the request and lifecycle model consistent across those infrastructure choices.
With the Metal3 and Netris integration configured, separate network environments can provide hardware-backed L2 isolation. Metal3 without that integration can also run on a flat network, so the network mode must be selected deliberately.
See how vMetal and vCluster handle GPU server provisioning end to end.
