Finding the right best VMware Horizon alternative for MSPs starts with understanding why so many managed service providers are walking away from it in the first place. IIf you built your VDI on VMware Horizon, November 2023 changed the math. That’s when Broadcom finalized its $69 billion acquisition of VMware and began reworking the licensing model in ways that hit MSPs particularly hard.
Perpetual licenses: gone. Smaller SKUs: eliminated. Bundles restructured into larger packages most MSPs didn’t need. Many partners reported cost increases of 3x to 5x on what they’d been paying before the acquisition closed.
Some MSPs absorbed it. Some passed the cost to clients and lost the contract. Others started looking for a VMware Horizon alternative for their MSP practice, which is probably why you’re reading this.
This isn’t about whether Horizon is good software. It’s about whether it fits the way MSPs actually operate and how to find the best VMWare Horizon alternative for MSPs.
VMware Horizon wasn’t designed with MSPs in mind. That’s not a criticism of the product. It was built for large enterprises with dedicated infrastructure teams managing a single-tenant environment. MSPs took that architecture, bent it sideways, and tried to serve 20 different clients with it.
For a while, the economics worked. Perpetual licenses had predictable costs. You could size a deployment, know your overhead, and build margin into your service offering.
That changed fast after Broadcom.
Broadcom’s strategy with major software acquisitions has followed a consistent pattern: move to subscription-only licensing, consolidate product tiers, and concentrate on larger enterprise accounts where revenue is easiest to extract.
For VMware partners, that meant the end of perpetual licensing in early 2024. SKUs got folded into larger bundles. MSPs who only needed specific components were suddenly paying for features they’d never deploy. Support contracts were restructured. The partner program changed in ways that made smaller MSPs less of a priority.
The result: MSPs who had built client offerings around Horizon found themselves repricing mid-contract or absorbing losses to protect existing relationships.
Even before Broadcom, Horizon had scale problems for the MSP model. The architecture requires vSphere and vSAN for on-premises deployments, or significant Horizon Cloud configuration for hosted versions. You need qualified VMware engineers to set it up and keep it running.
For an MSP with 5 to 15 technical staff, that’s a meaningful skill dependency. Every major version update is a training event. Every new client onboarding is an infrastructure exercise.
The licensing model also wasn’t built for multi-tenancy at the billing level. You were managing separate agreements, separate support tickets, and separate renewal timelines per client. That overhead doesn’t disappear. It compounds. And overhead at scale destroys margin.
Enterprise VDI and MSP VDI look similar on paper. They’re not the same problem.
An enterprise VDI buyer is optimizing for one workforce. An MSP is building an offering they can deliver across dozens of different clients, at different sizes, with different application stacks, different compliance requirements, and different budgets. The platform has to flex for all of that without doubling your operational burden.
The right platform gives you a single pane of glass across all client environments. You should be able to provision a new client, assign resources, set access policies, and manage users without leaving the admin console. Each client’s environment stays isolated, but your team isn’t logging into separate portals for every account.
Anything that adds per-client login friction is a time cost. If your team spends 20 extra minutes per client per week on administrative tasks and you have 30 clients, that’s 10 hours a week burned on friction. That’s a quarter of an FTE, gone.
Clients trust MSPs partly because MSPs translate complicated technology costs into predictable monthly line items. That only works if your own costs are predictable first.
Per-VM, flat-rate pricing is what makes the MSP math work. You know what each client’s environment costs before you quote them. You know your margin before the conversation. No surprise licensing reconciliations at renewal time.
Per-named-user pricing creates the opposite problem. Client headcount changes constantly. People join, leave, go part-time, change roles. With per-user billing, every HR event at your client’s company is a billing event at yours. That’s not a manageable service.
If you’re scaling a managed desktop practice and Horizon’s pricing no longer works, see how our MSP partner program structures pricing and support for multi-client environments.
This comparison gets oversimplified constantly. “Horizon is more customizable." “DaaS is easier." Both of those statements are accurate. Neither is the full picture.
The real trade-off is control versus operational cost. Horizon gives you more configuration depth. You can tune it for specific workloads, integrate it with on-premises infrastructure, and manage it at a granular level. That control has a price: infrastructure overhead, licensing complexity, and technical staffing requirements.
DaaS moves the infrastructure burden to the provider. You’re not managing hypervisors, storage, or networking. You’re managing client environments on top of someone else’s infrastructure layer. Less control over the stack. Significantly lower operational cost. For MSPs managing dozens of clients, that trade-off is usually worth making.
| Factor | VMware Horizon | DaaS (e.g., V2 Cloud) |
| Setup time | Days to weeks | Under 20 minutes |
| Infrastructure required | Yes (vSphere, vSAN, or Horizon Cloud) | No |
| Multi-tenant management | Possible, but complex | Built-in |
| Licensing model | Subscription bundles (post-Broadcom) | Per VM, flat-rate |
| Technical expertise needed | VMware-certified engineers | No certifications required |
| Support included | Separate support contract | 24/7 included in all plans |
| Uptime SLA | Varies by deployment | 99.95% |
| Contract flexibility | Annual minimum | No long-term contracts |
| BYOD and remote device support | Requires endpoint config | Works on any device with internet |
| HIPAA-compliant option | Enterprise configurations | Available |
What this means: If your MSP has the VMware expertise, the infrastructure, and clients with complex enough requirements to justify it, Horizon is defensible. If you don’t have all three of those things, DaaS is almost always the better operational fit.
The worst thing you can do is pick a replacement based on a vendor demo that only shows the best-case scenario.
Test multi-tenancy at your real scale. Don’t demo with one client environment. Set up 3 or 4 simultaneously and see how the admin console handles it. Can you switch between clients cleanly? Can you push policy changes across accounts without repeating the same steps manually?
Provision your real applications, not the vendor’s demo apps. “Deploys in minutes" means nothing if your client’s line-of-business application takes hours to configure in the new environment. Test the full onboarding process from scratch, not just desktop spin-up time.
Test support under pressure. This is where MSP relationships actually break. When a client’s environment goes down at 9 AM on a Monday, how fast does your vendor respond? Don’t accept “24/7 support" as an answer. Ask for the actual escalation path, average first-response time, and whether support is included or a separate contract.
Run the pricing numbers at your client mix extremes. Some DaaS platforms are priced well for small clients but get expensive at the high end, or vice versa. Build out the actual model for your smallest and largest accounts before committing.
Ask specifically about migration tooling. A good alternative doesn’t just give you a destination. It helps you get there. Ask whether the vendor provides documentation, migration scripts, or assisted onboarding. The answer tells you a lot about how they treat MSP partners.
The MSP market has specific requirements that generic VDI platforms weren’t designed to meet. What you’re looking for is a platform where multi-client operations are a first-class use case, not something you’re hacking together from enterprise features.
Multi-tenant management built into the product means you’re not duct-taping separate deployments together. Flat-rate per-VM pricing means client headcount changes don’t create billing headaches. And fast onboarding means a new client is a conversation, not a project.
At V2 Cloud, we deploy cloud desktop environments in under 20 minutes. For an MSP, that’s the difference between onboarding a client in a single call versus scheduling a week-long setup project. We also include 24/7 support on every plan, no separate contract required. When a client calls you at 11 PM with a desktop issue, there’s actually someone to escalate to.
The cloud VDI architecture also handles BYOD-heavy environments well. If your clients have employees on personal devices, mixed operating systems, or staff in different regions, a Desktop as a Service model works without requiring endpoint management on every machine.
For MSPs who want to offer a fully managed desktop experience, our V2CloudCare option extends that further: a managed cloud desktop layer you can incorporate directly into your service stack.
Moving clients off Horizon doesn’t have to be a six-month project. Talk to one of our cloud experts about how MSPs structure migrations without disrupting existing service agreements.
It depends on your existing investment and client profile. If you’re already certified, have the infrastructure in place, and serve enterprise clients with genuinely complex requirements, the switching cost may outweigh the pricing increase. For MSPs managing SMB clients without deep VMware expertise on staff, the post-Broadcom cost structure is difficult to justify against simpler alternatives.
Horizon is a VDI platform that requires you to manage the underlying infrastructure: compute, storage, networking, and licensing. DaaS shifts that infrastructure layer to a cloud provider. You manage client environments on top of a provider-managed layer. The trade-off is less configuration control in exchange for significantly lower operational overhead.
Yes, if the platform was built for it. Multi-tenant management varies significantly between DaaS providers. Look for platforms where client environments are logically isolated but manageable from a single admin console, not separate portals per account. Ask vendors specifically whether multi-tenancy is native to the product or built on top of it.
That depends on how many clients you’re moving, the complexity of their application stacks, and whether the destination platform provides migration support. Simple environments can migrate in days. More complex deployments take longer. Most MSPs phase migrations across new client onboardings rather than doing a hard cutover for existing clients.
Three factors matter most: multi-tenant management capability, pricing structure (per VM or per resource, not per user), and whether support is included without a separate contract. Secondary factors include deployment speed, BYOD compatibility, and what the vendor’s MSP partner program actually includes in terms of margin, tooling, and onboarding support.
The better DaaS platforms do. Not all of them. Ask specifically whether multi-tenant admin is native or requires separate instances, and whether you can manage billing, users, and resources across clients without logging into separate environments. A platform that requires separate portals per client is still costing you the administrative overhead you’re trying to eliminate.
Pricing structures vary by provider. Flat-rate per-VM pricing is the most manageable for MSPs because your costs stay stable regardless of how often a client’s headcount changes. Our pricing is per VM, sized by workload type, with no hidden fees and no long-term contract required. Multiple users can share a single VM, which changes the math considerably for smaller client accounts.
Your V2 CloudCare team — real people, on the line.
