For CSPs
Proxmox for Cloud Service Providers
For CSPs dropped from the VCSP program, or still in it and expecting the next round of cuts: how to move a multi-tenant cloud from VMware to Proxmox VE.
Cloud Service Providers were the first casualty of the Broadcom era at VMware. The VCSP program that your entire business model was built on no longer exists in any recognisable form. If you're still running tenant workloads on VMware, you are either paying far more to do it or waiting for your partner agreement to end.
If you're an MSP running managed hosted platforms and you're not yet selling self-service IaaS, our MSP page is a better fit. The CSP move comes later and works differently.
What Broadcom changed
- VCSP shut down in 2024. The VMware Cloud Service Provider program, the per-VM, usage-billed model that made multi-tenant cloud viable on VMware, was terminated. Existing partners were moved onto commercial subscriptions with much smaller discounts and a licensing model that doesn't fit how a cloud is sold.
- VCF licensing works against multi-tenancy. VMware Cloud Foundation assumes single-customer deployments. Running multiple tenants on a shared cluster means either complex compliance arrangements or per-tenant cluster builds that waste hardware.
- The remaining partner pool is tiny and shrinking. Broadcom kept a small group of "Pinnacle" and "Premier" partners: the global hyperscalers and a handful of enterprise regionals. Most established cloud providers were not invited, and that pool has continued to shrink each year as Broadcom tightens criteria and exits unprofitable accounts.
- Pricing has moved mid-cycle. The per-core list price for VCF went from US$350 to US$400 partway through what was effectively a forced three-year migration window. There is no sign it will be the last increase.
Why it hits CSPs hardest
For an SME, a VMware renewal is a line-item conversation. For a CSP, your hypervisor is your product. If your platform vendor:
- Removes the licensing model your pricing was based on,
- Forces architectures that destroy your hardware economics,
- Reserves the future of the platform for a closed list of partners you're not on,
- And raises prices mid-contract,
then Broadcom controls the next move in your business. Many CSPs keep investing in VMware without deciding to, because a migration feels bigger than the next renewal. That is a decision too, and it is worth making deliberately.
Why Proxmox fits a CSP
Proxmox VE has been used as a multi-tenant cloud platform for over a decade, well before it became a common VMware replacement. Service providers run Proxmox estates of several thousand VMs today in Europe, and increasingly in Australia.
- Per-socket subscription with no order minimums, per-feature uplifts or per-tenant multipliers. Licensing cost follows your hardware, so adding tenants doesn't add licence cost.
- Native multi-tenancy. Resource pools, role-based access, SDN VLANs/VXLANs, per-tenant Ceph storage pools and isolated backup repositories are all in the base platform.
- REST API for everything. Pairs naturally with portals like MultiPortal for self-service tenant onboarding, billing integration, and white-labelled customer UX.
- Proxmox Backup Server for per-tenant deduplicated, encrypted, immutable backups. It's free at the platform level, so you can sell it as a tier feature.
- Open source. There are no licence audits, and a licensing change can't shut your business down overnight. The code is community-owned, so no single acquirer controls it.
What the numbers look like for a CSP
Illustrative scenario
40 VMware hosts. 400 tenant VMs. US$448k a year in VCF licensing.
A worked example, built from environments of this size, of a provider moving its customer-facing platform from VMware Cloud Foundation to Proxmox VE and Ceph in phased batches, with every cost shown at list price and at Broadcom's discounted 3-year commit pricing.
Read the scenario →Illustrative scenario based on real-world environments, not a named client.
What a CSP migration looks like
Migrating a multi-tenant cloud is operationally different to migrating an enterprise's internal workloads. Customers can't see disruption, billing has to keep working, and your support team has to run both platforms during the transition.
- Discovery. Tenant mix, workload profiles, current billing model, customer SLAs, regulatory constraints and data sovereignty requirements.
- Target architecture. Proxmox cluster topology designed for your tenant density and isolation requirements, covering the Ceph storage layout, SDN structure, PBS configuration and tenant onboarding API.
- Portal & automation integration. Connect your existing customer portal (or a new one) to the Proxmox API. Map your billing entities to Proxmox resource pools and tagging. Validate tenant provisioning end-to-end.
- Pilot tenant. Move a friendly customer first, validate the operational and billing flows, refine runbooks.
- Batched cutover. Migrate tenants in scheduled groups during agreed maintenance windows, with communications for each customer.
- Decommission VMware. Once the last tenant is across, retire the VMware estate. Salvage value for hardware feeds back into the business case.
Common objections
"Our customers chose us because we're on VMware."
In practice this is rarely the reason. Customers chose you for reliable, well-supported cloud services in Australia. Almost none of them care what hypervisor sits underneath, as long as their VMs run and their backups work. The handful that do are also negotiating with their own VMware costs and may welcome the platform change.
"We don't have the engineering capacity for a migration this size."
Most CSPs don't, which is why we run it as an engagement. Our engineers have run multi-host, multi-tenant migrations from initial discovery through full decommissioning. Your team focuses on customer comms and operational continuity; we focus on getting the platform built and tenants moved without incident.
"What if Proxmox gets acquired and the same thing happens?"
The base platform is open-source (AGPL). Proxmox Server Solutions GmbH owns the trademark and subscriptions, but the codebase belongs to the community. In a worst-case acquisition scenario, the platform can fork and continue. You can also self-support indefinitely; some production CSPs run without subscriptions today. That kind of single-vendor risk is much smaller with Proxmox.
Already running Proxmox, or about to?
Once the platform decision is made, the work shifts to building and running it well. Our MSP & CSP platform consultancy covers hosting platform design, retained senior-engineer hours for architecture, design and upgrade planning, and the migrations that move your tenants onto it.
Talk to us before your next renewal
Renewal timing matters more than anything else in a CSP migration. Every cluster moved before its VCF renewal is one fewer subscription to renew. If your renewal is in the next 12 months, the conversation needs to happen now.
Discovery calls are free and run by an engineer. Tell us about your platform, your renewal timing, and where the pain is, and we'll come back with a realistic picture of what moving off VMware looks like for your business.