Zero Touch Provisioning for AI Cloud Scale
Automate registered GPU servers after driver setup. vMetal turns Machine requests into provisioned infrastructure, and vCluster assigns dedicated tenant workers through Private Nodes.
Automate registered GPU servers after driver setup. vMetal turns Machine requests into provisioned infrastructure, and vCluster assigns dedicated tenant workers through Private Nodes.
Every hour spent on manual setup is revenue your GPU infrastructure is not generating.
Manual OS installation and network setup delay the point when registered GPU servers can accept customer workloads.
Building provisioning pipelines in-house requires significant engineering investment before a single tenant workload runs.
Manual network configuration and OS installation introduce inconsistencies that cause outages and compliance failures at the worst moments.
After hardware registration and driver configuration, vMetal automates supported provisioning workflows through one Machine API. vCluster uses that capacity for tenant clusters with dedicated Private Nodes. vCluster Labs software powers 100K+ GPUs.
Automate every layer from physical server provisioning to isolated tenant Kubernetes environments running production AI workloads.
vMetal exposes one Machine API above bare metal and VM provisioning drivers. Registered inventory, images and credentials enable repeatable machine lifecycle workflows for server provisioning. Network automation uses supported integrations such as Netris.

vCluster Standalone runs Kubernetes as a CNCF-certified binary on Linux, without an existing Kubernetes cluster. It supplies a Kubernetes foundation for server provisioning; vMetal separately orchestrates machine and OS provisioning.

Karpenter-based Auto Nodes requests worker capacity according to configured policies. With the vMetal provider, Machine requests provision available infrastructure for server provisioning; inventory, driver readiness and release rules determine actual capacity.

Tenant-owned CNI configuration and supported Netris integrations provide separate network controls for server provisioning. Ethernet segmentation can use VLANs, VRFs and ACLs; InfiniBand isolation uses fabric partitions rather than Ethernet constructs.

Use supported workload templates for server provisioning, including the NVIDIA Run:AI partner integration. Configure GPU, network and storage prerequisites, and validate the selected template for Private Nodes before offering it to production customers.

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 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.
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.
Private Nodes give a tenant its own worker networking configuration. Supported Netris integrations can add Ethernet segmentation through VLANs, VRFs and ACLs on compatible infrastructure. These controls require explicit setup and do not reserve all fabric bandwidth. InfiniBand uses partition keys and fabric management rather than Ethernet segmentation; design the relevant fabric controls alongside tenant cluster access policies.
Auto Nodes extends zero touch provisioning to scaling. It works like Karpenter for bare metal, provisioning more GPU servers through the vMetal Machine API when tenants schedule workloads that need capacity. New nodes join without operator involvement, so demand doesn't turn into a provisioning backlog.
Boost Run went from decision to production launch in under 45 days for its managed Kubernetes service. That is a customer example rather than a promised implementation time. Your launch depends on machine inventory, driver configuration, networking, storage, templates and service integrations. vMetal and vCluster connect machine orchestration with tenant cluster delivery, reducing the infrastructure workflows you need to build yourself.
vCluster supports air-gapped and FIPS deployment environments. The provisioning stack can operate in disconnected data centers where servers cannot reach external package repositories or registries. This makes zero touch provisioning viable for regulated industries and government data centers that require network-isolated infrastructure without sacrificing automation.
See how vMetal delivers zero touch provisioning from rack to production Kubernetes.