Broadcom’s acquisition of VMware didn’t just raise prices; it broke the math that most MSPs built their managed services practice on. If your margins depended on VMware Cloud Service Provider (VCSP) program pricing, you’ve probably already done the calculation and the numbers don’t work anymore.
But the real problem isn’t the cost increase. It’s that the VCSP displacement exposed a deeper vulnerability:
Most MSPs are reselling someone else’s platform instead of owning their own.
The difference matters enormously when the upstream vendor decides to change the rules overnight.
This guide is for MSPs who want to rebuild their practice. Not just replace a hypervisor, but build a private cloud managed service practice they actually own. We’ll cover how to price multi-customer services, structure SLAs around a hosted management plane, and use multi-tenant RBAC to segment customers at scale. The goal isn’t just to get off VMware. It’s to build recurring revenue with predictable margins and infrastructure you control.
Price It Like a Product, Not a Project
The first shift most MSPs need to make isn’t technical; it’s conceptual. Infrastructure has to become a product with defined tiers, predictable costs, and margins you can model in a spreadsheet before you sign a single customer.
Platform9 Private Cloud Director (PCD) uses per-core, single-SKU pricing. That sounds like a small detail, but it changes everything about how you build service packages. Your cost input is linear: more cores means proportionally more cost. There’s no SKU complexity and no surprise line items. That means you can build a service catalog around tiers such as Bronze, Silver, and Gold tiers, or Starter, Growth, and Enterprise. Each tier is differentiated by compute quota, storage allocation, and HA level. With this model you’ll know exactly what each tier costs you before you set a price.
One structural advantage worth understanding: the Platform9 management plane runs in Platform9’s cloud, included in the per-core price. In a traditional deployment, management infrastructure eats a chunk of your physical capacity.
Now every core you own runs customer workloads. That’s not just an architectural detail; it’s billable resources you’re not leaving on the table.
The practical result: you can offer customers 12–36 month contracts with predictable pricing, because your own cost structure finally supports it. For MSPs competing against public cloud on price, predictability is often a stronger selling point than the number itself.
Tenant Isolation Your Customers Can Actually See
Multi-tenancy is table stakes for any MSP platform. But “multi-tenant” can mean a lot of things, and your customers, especially those in regulated industries, will question your offering. The answers need to meet the most stringent needs.
In Private Cloud Director, each customer gets their own domain — the hard-isolated identity boundary that contains their users, groups, and tenants. Inside their domain, each customer has one or more tenants (often one per workload environment such as dev, staging, or prod), each with enforced resource quotas across compute, storage, and networking. These aren’t soft guardrails. Quotas are enforced at the platform level, and one customer’s domain cannot see another customer’s identities, tenants, or resources. Self-service provisioning lets your customers deploy VMs, create networks, and manage security groups within the boundaries you define without ever touching another customer’s environment.
Network isolation is built in via OVS/OVN software-defined networking, with per-tenant distributed routing, DHCP, IPAM, and microsegmentation. There’s no separate NSX license. Enterprise SSO via SAML 2.0 is configured per domain, so giving each customer their own domain lets them federate with their own identity provider — Okta, Microsoft Entra ID for example — inheriting their existing MFA policies.
For MSPs who want to present the platform as their own service rather than a vendor product, the portal UI can be customized to reflect your branding. Your portal, your identity; the Platform9 name doesn’t have to be what your customers see.
What You Can Actually Commit To in an SLA
SLAs are where MSP practices can get into trouble. Committing to uptime numbers without understanding the underlying platform’s failure modes is how margins evaporate in incident credits.
Platform9’s core HA infrastructure, offering VM High Availability clustering and Dynamic Resource Rebalancing, gives you the foundation to make real commitments. VM HA automatically restarts VMs on surviving hosts when a host fails. Dynamic Resource Rebalancing continuously redistributes workloads to prevent resource contention. These are the two capabilities that make the difference between an SLA you can defend and one you’re hoping doesn’t get tested.
The hosted management plane introduces a consideration worth understanding: your customer-facing SLA has a dependency on the Platform9 SaaS management plane’s availability. Are you trading a non-billable asset you control for a managed service you can’t? Private Cloud Director’s hosted management plane has a 99.9% uptime SLA. Combined with Platform9’s proactive monitoring and support you can offer this to your customers with full confidence in reliability.
For backup and DR, Private Cloud Director integrates directly with Veeam, Rubrik, Commvault, and Cohesity among others. How you structure those integrations within your service tiers is a design decision: bundling backup as a managed add-on at a per-VM rate is a common approach, since it converts a cost center into an upsell with its own margin.
Onboarding a Customer Without a Month-Long Project
The economics of MSP migration are simple: every hour your team spends moving VMs is an hour you’re not billing for something else. A migration project that takes six weeks doesn’t just delay revenue—it often costs more than a year’s worth of the margin improvement you were migrating to capture.
vJailbreak is Platform9’s automated migration tooling, and it’s designed specifically for this problem. For customers coming off VMware vSphere, vJailbreak handles the complete migration path: snapshot, copy, convert, and boot, while the source VMs keep running. Warm migration with change block tracking means the actual cutover window is measured in minutes, not hours. Customers don’t see a maintenance window because there effectively isn’t one.
For net-new customers who aren’t migrating from VMware, the onboarding path is different but equally important to have documented before your sales team starts quoting. A standardized onboarding playbook defining ownership and responsibilities: what the platform team does, what the customer is responsible for, what the cutover checklist looks like, is what separates an MSP practice from a one-off professional services engagement. The goal is a consistent, repeatable motion you can hand to a junior engineer.
If onboarding a new customer requires your most senior infrastructure person for three weeks – you’ve built a services practice, not a managed services product.
The Practice You Actually Own
The MSPs who will come out of the Broadcom displacement in the best position aren’t the ones who found the cheapest replacement hypervisor. They’re the ones who used the disruption as a forcing function to rebuild their practice on infrastructure they control, with economics they understand.
Private Cloud Director is designed to support that model: per-core pricing you can forecast, tenant isolation your customers can trust, migration tooling that keeps your labor costs from eating your margins, and a management plane that doesn’t waste capacity on itself.
If you’re ready to scope what a Platform9-based practice looks like for your customer base, check out our Service Providers page to learn more about our managed infrastructure platform.
