Proxmox for Cloud Service Providers

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're either paying through the nose to do it or counting down the days until your partner agreement ends. This page is for you.

If you're an MSP running managed hosted platforms and you're not yet selling self-service IaaS, you might want our MSP page instead — CSP is the next evolution from that shape, but the playbook is different.

What actually happened

• VCSP shut down in 2024. The VMware Cloud Service Provider program — the per-VM, usage-billed model that made multi-tenant cloud economically viable on VMware — was terminated. Existing partners were rolled into commercial subscriptions at a fraction of the discount and none of the operational fit.
• Multi-tenant licensing on VCF is structurally hostile. VMware Cloud Foundation assumes single-customer deployments. Running multiple tenants on a shared cluster requires either compliance gymnastics or per-tenant cluster builds that destroy your hardware economics. The pricing model no longer matches how a cloud is built or sold.
• 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. That's not the last increase you'll see — it's the start of a trajectory.

Why this is existential, not just expensive

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 your business model is no longer yours to control. The next move belongs to Broadcom, not you. Continuing to invest in a platform built around that vendor relationship is a strategic decision most CSPs aren't making consciously — they're defaulting into it because migration feels bigger than the next renewal cycle.

Don't bet your business on a vendor that's actively curtailing the model you sell on.

Proxmox is the operationally honest answer

Proxmox VE wasn't designed as "the VMware alternative" — it's been a multi-tenant cloud platform in its own right for over a decade. Service providers run multi-thousand-VM Proxmox estates today in Europe and increasingly in Australia. The economics aren't theoretical:

• Per-socket subscription with no order minimums, no per-feature uplifts, no per-tenant multipliers. Your margin scales with hardware, not with tenant count.
• Native multi-tenancy primitives — resource pools, role-based access, SDN VLANs/VXLANs, per-tenant Ceph storage pools, isolated backup repositories. Built into 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 — included free at the platform level, charge it back as a tier feature.
• Open source. No audit risk, no surprise licensing change can end your business overnight. The platform belongs to the community, not to a single acquirer.

One CSP's numbers

What a CSP migration actually looks like

Migrating a multi-tenant cloud is operationally different to migrating an enterprise's internal workloads. Your customers cannot experience disruption; your billing system has to keep working; your support team has to be able to operate both platforms during the transition.

1. Discovery. Tenant mix, workload profiles, current billing model, customer SLAs, regulatory constraints, sovereign data requirements.
2. Target architecture. Proxmox cluster topology designed for your tenant density and isolation requirements. Ceph storage layout. SDN structure. PBS configuration. Tenant onboarding API design.
3. 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.
4. Pilot tenant. Move a friendly customer first, validate the operational and billing flows, refine runbooks.
5. Batched cutover. Migrate tenants in scheduled groups during agreed maintenance windows. Customer-by-customer comms.
6. Decommission VMware. Once the last tenant is across, retire the VMware estate. Salvage value for hardware feeds back into the business case.

Common objections, honestly addressed

"Our customers chose us because we're on VMware."

Rarely true in practice. Customers chose you because you delivered 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 — that's why this is an engagement, not a DIY project. We've done 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 — production CSPs do this today without subscriptions. The structural vendor risk that VMware now represents simply doesn't exist with Proxmox.

Talk to us before your next renewal

The single biggest accelerant for a CSP migration is renewal timing. Every cluster moved before its VCF renewal is one less subscription you re-up. If your renewal is in the next 12 months, the conversation needs to happen now.

Discovery calls are free and engineering-led — not an SDR triage call. 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.

Book a discovery call Model the licensing delta