Tech Blog by vClusterPress and Media Resources

Introducing Private Customer Clouds: A Cloud for Every Customer, on the Metal You Already Sell

Nov 19, 2026
|
6
min Read
Introducing Private Customer Clouds: A Cloud for Every Customer, on the Metal You Already Sell

Most AI Clouds already run a real business on bare metal. A customer signs a contract for a block of GPUs, the provider racks and provisions the machines, and the customer takes it from there. It works, and it pays.

What it doesn't do is scale gracefully. Behind most offtake deals sits a pile of scripts, SSH keys, switch tickets and spreadsheets. Onboarding a new customer is a project. Moving machines between customers when a contract ends is a teardown and rebuild. Every new site or GPU generation means more people doing the same work by hand. And customers who signed for bare metal increasingly expect it to behave like a cloud: self-service, their own images, their own clusters, no ticket queue.

Today we're introducing private customer clouds in vCluster Platform, now in limited availability. It's a new abstraction that lets a provider carve out a private cloud for each of its customers, on the hardware it already owns and already sells. Same metal, same control plane, one step up. Read the full announcement.

What's new: the tenant

The release introduces the tenant as a first-class object in vCluster Platform. A tenant is one of the provider's customers, and it owns the resources the provider assigns to it: machines, network environments and OS images.

That one change reshapes how the platform works for both sides:

  • The provider sees every machine, network and image across the data center in one inventory. It defines a customer once, grants that customer the machines, networks and images it’s entitled to, and sets limits on how much capacity it can claim.
  • The customer gets a self-service environment scoped to exactly what it was given. It provisions machines and clusters, picks the OS to use and attaches a network, without filing a ticket.

The provider defines the managed services each customer can use, and the customer chooses which of its own machines power them. Everything beneath a tenant inherits its boundary: every machine, network, image and cluster the customer uses stays inside it.

Sell the contract and the idle machine

Offtake is how most of this market buys, so private customer clouds start there.

Every machine in the inventory is either reserved to one customer for the length of its contract or left on-demand for customers to claim from a shared pool. Reserved capacity lets a provider sell the long-term contract on day one. On-demand capacity puts machines to work between contracts instead of sitting idle.

When a contract starts or ends, moving a machine to another customer is a reassignment, not a teardown and rebuild. The machine is cleaned, moved onto the right network and handed over in hours rather than days or weeks. That changes the math on shorter terms and smaller customers, which are now more economical to serve.

The same reserved and on-demand model applies to VMs, so a provider can offer them on shared capacity or on a customer's own reserved machines, from the same inventory.

Customers serve themselves

Inside its tenant, a customer runs its own cloud, behind its own branding and UI settings, without a separate install. It can:

  • Provision machines from the capacity it holds, booting the certified golden images the provider publishes, or its own images where the provider allows it
  • Re-provision a machine it owns with a different image or network, without waiting on the provider
  • Organize its teams into projects with their own members and roles
  • Self-serve clusters of different types, and choose which machines power them.
  • Add its own SSH keys and connect directly

The provider stays in control of what each customer is entitled to, and the customer gets the speed of doing everything else itself. That’s the demand AI Clouds like Corvex are seeing. “Customers who commit to dedicated capacity want to run it themselves. Their platform teams want to divide capacity among internal groups and give developers a fast path to compute. vCluster Platform v5.0 gives our customers a self-service environment of their own on dedicated hardware,” said Seth Demsey, CEO of Corvex.

More control for the customer, without more exposure for the provider

Giving customers self-service only works if the boundaries between them hold. Private customer clouds draw those boundaries at the infrastructure layer:

  • Machines: each customer runs on its own machines, whether they’re used as bare metal or as nodes in its own clusters.
  • Network: each customer gets its own virtual network. When a machine changes customers, it is moved back to the pool on a managed network. When it boots for its new customer, it joins the customer's network, so no one has to reconfigure the network by hand.
  • Control plane: every tenant cluster gets its own control plane, run by vCluster.

A customer provisioning its own machines can only reach what it was assigned.

One API over the tools you already run

No provider runs a single, uniform fleet for long. New GPU generations arrive with new provisioning tools, new sites come online, and what's already delivered keeps running. Every new GPU order is a chance to standardize what comes next, without ripping out what's in place.

vMetal, the infrastructure orchestrator beneath vCluster Platform, presents every machine in one inventory, whichever driver provisions it. Providers keep the provisioning tools they already run, whether Metal3 or NVIDIA Infra Controller (NICo), and each machine carries the same set of attributes to the provider and to its customers either way.

On top of that inventory, providers choose how their customers experience it:

  • A console on day one. The vCluster Platform console works out of the box for providers and their customers.
  • Their own portal later. Every tenant, machine, image and network is an API object, in the same API the console uses. Providers who want a custom portal build it on the same API.

More than Kubernetes

vCluster started by giving every tenant its own control plane, so teams could share infrastructure without sharing a cluster. Private customer clouds take that same tenant boundary down the stack, from the control plane to the machine, the network and the image.

That makes Kubernetes one of the things a provider can sell on the platform, not the only one. A customer can rent bare metal and never ask for a cluster. Another can start with machines and add clusters when it needs them. Both sit on the same platform, inside the same tenant, so moving up from raw capacity to managed services is a configuration change, not a re-platforming project. Services like NVIDIA Run:ai, Dynamo and Saturn Cloud deploy into a customer's tenant clusters as Stacks, so a provider can offer more than raw capacity without building each service by hand, including custom inference solutions.

For existing vCluster users, tenant mode can stay off until you're ready.

What's next

This release puts the core objects in place: tenants, machines, network environments and images, under one inventory and one API.

As private customer clouds move toward general availability, every machine will be validated before it reaches a customer, through burn-in testing and hardware profiling that checks its BIOS settings against a golden template. Providers will be able to give each customer its own storage, choosing a tier and size. Early versions are already in testing with customers.

From there, the platform can start fixing problems itself, like swapping a failed machine out of a customer’s pool. The longer arc is a platform that sees compute, network and storage together, so an AI Cloud can manage its whole fleet the way a hyperscaler does. Private customer clouds are the first step.

Get started

Share:
Get started with the
#1 platform for AI infra.

Trusted by today’s fastest-growing AI cloud builders.

Ready to take vCluster for a spin?

Deploy your first tenant cluster today.