VMware Horizon VDI Alternatives

VMware Horizon spent a decade as the default VDI platform for enterprises that had standardised on VMware. The product was integrated with vSphere, broadly capable, and supported by an ecosystem of partners and tooling that made deployments tractable even for large estates. Under Broadcom, that default position has been weakened — Horizon was carved out and sold to KKR (renamed Omnissa), pricing and licensing have shifted, and the customers who used Horizon have started actively evaluating alternatives.

This article walks through the VDI alternatives that have meaningful enterprise traction in 2026, where each fits, what the migration paths look like, and how to think about the decision when Horizon is no longer the obvious choice.

The post-Broadcom Horizon situation

Horizon's transition out of Broadcom into Omnissa (KKR-owned) is the defining context for any current VDI discussion. The relevant developments:

Horizon was sold to KKR in early 2024 and now operates as Omnissa, an independent company. Omnissa continues to develop and support the product, but the integration with the rest of the VMware portfolio (vSphere, NSX, vSAN) is no longer guaranteed in the same way it was under VMware's unified ownership.

Licensing has been restructured. The former entitlements have been mapped to Omnissa-specific structures, and pricing has shifted, with several customer cohorts reporting meaningful increases. The licensing simplification that Omnissa promised has been partial in practice; many customers report that the new structures have new complexities.

The integration story with VMware-on-Broadcom has become more uncertain. Omnissa and Broadcom maintain operating relationships, but the deep co-engineering that previously existed has weakened. Customers planning to keep Horizon on Broadcom-owned vSphere face a multi-vendor model where neither vendor has an incentive to optimise for the joint footprint.

The customer base is actively shopping. Enterprises that ran Horizon as their VDI platform are evaluating alternatives at unprecedented rates, partly because of the pricing pressure and partly because the unified-vendor proposition that justified Horizon over alternatives has weakened.

The VDI alternatives landscape

The viable VDI alternatives fall into a few categories.

Citrix DaaS and Citrix Virtual Apps and Desktops

Citrix remains the largest competitor to Horizon and is the most frequently considered alternative. The product is mature, broadly capable, and has the ecosystem depth Horizon had. Key considerations:

• Strengths: deep feature set, established customer base, strong partner ecosystem, supports a wide range of hypervisor and cloud back-ends, mature management tooling.
• Weaknesses: licensing complexity comparable to or greater than Horizon, ownership changes (private equity acquisition completed in 2022) have introduced their own commercial uncertainty, pricing has trended upward.
• Best fit: large enterprises with existing Citrix experience, organisations with complex application delivery needs, environments where the hypervisor strategy is independent of the VDI choice.

Amazon WorkSpaces and WorkSpaces Web

AWS's managed VDI offering, available as both Windows desktops (WorkSpaces) and browser-delivered access (WorkSpaces Web). The managed-service model removes infrastructure management responsibility.

• Strengths: fully managed by AWS, monthly per-user pricing, integrates with AWS identity and networking, no on-premises infrastructure required.
• Weaknesses: tied to AWS infrastructure (regulatory and data-residency considerations matter), limited customisation versus self-managed alternatives, predictable cost only at predictable usage patterns.
• Best fit: organisations already on AWS, use cases with relatively standard desktop requirements, customers prioritising operational simplification over architectural control.

Microsoft Azure Virtual Desktop (AVD) and Windows 365

Microsoft's two-pronged VDI offering. AVD is the more configurable IaaS-like service, comparable to traditional VDI; Windows 365 is the fully managed Cloud PC offering.

• Strengths: tight integration with Microsoft 365, leverages Azure infrastructure, well-suited for Windows-centric estates, Microsoft licensing rights for Windows are clearer than under most alternatives.
• Weaknesses: tied to Azure (data-residency considerations), pricing can be unpredictable at scale, configuration complexity for non-standard use cases.
• Best fit: Microsoft 365 customers, Windows-heavy environments, organisations preferring Microsoft's ecosystem for desktop delivery.

Nutanix Frame

Nutanix's DaaS offering, originally designed for AHV but supporting multiple back-ends. Particularly relevant for customers who are also evaluating Nutanix as a vSphere alternative on the broader infrastructure side.

• Strengths: works across hypervisor and cloud back-ends, integrates with Nutanix's broader platform story, simpler operational model than traditional VDI.
• Weaknesses: smaller ecosystem than Citrix or Horizon, less mature feature set in some areas.
• Best fit: Nutanix customers, organisations seeking simpler VDI architectures, environments where the broader Nutanix story is also being adopted.

Parallels Remote Application Server (RAS)

An established Citrix/Horizon alternative with a focus on simpler licensing and operational models. Has grown its enterprise footprint significantly in the past two years.

• Strengths: simpler licensing, lower price point, supports multiple back-ends, established enterprise customer base.
• Weaknesses: smaller partner ecosystem, feature breadth narrower than Citrix or Horizon at the high end.
• Best fit: mid-market enterprises, organisations prioritising operational simplicity and lower cost.

Google Cloud Workstations and Chrome Enterprise

Google's offerings for cloud-delivered work environments. Workstations targets developer workloads; Chrome Enterprise extends Chromebook-based delivery for broader user populations.

• Strengths: well-suited for cloud-native workloads, integrates with Google Cloud and Workspace, lower complexity than full VDI.
• Weaknesses: not a direct VDI replacement for traditional Windows desktop use cases, ecosystem narrower than Microsoft and AWS.
• Best fit: developer-heavy organisations, organisations standardised on Google Workspace, use cases that don't require traditional Windows desktops.

Open-source and emerging options

Several open-source and emerging commercial options exist (Apache Guacamole-based stacks, Kasm Workspaces, Cameyo, etc.). These are typically suitable for specific use cases rather than as broad enterprise VDI replacements, but they have a role in particular scenarios.

The decision framework

The right alternative depends on several factors specific to the customer's environment.

Use case profile

VDI use cases vary widely — task workers with standardised desktops, knowledge workers with personalisation requirements, developers with high-performance workloads, contractor populations needing time-limited access, regulated populations needing strict isolation. The alternatives are not equally good across all use cases; the right product depends on which use cases dominate the customer's estate.

Existing infrastructure and cloud commitments

Customers with significant AWS commitments are naturally drawn to WorkSpaces; Microsoft-centric customers to AVD or Windows 365; Google-centric customers to Workstations. Customers without strong cloud commitments have more options but also more architectural questions to answer.

Hypervisor strategy

Customers staying on vSphere can run any of the products that support vSphere as a back-end (Citrix, Parallels, sometimes others). Customers moving to alternative hypervisors (Nutanix AHV, Proxmox) need products that support the target hypervisor.

Operational model

Some organisations want continued self-management; others want to offload operations to a managed service. Managed services (WorkSpaces, Windows 365, parts of AVD) suit organisations with limited VDI operational depth; self-managed alternatives suit organisations with established VDI capability.

Regulatory and data-residency requirements

VDI handles end-user computing data, which often has regulatory implications. Public cloud VDI may be inappropriate for some regulated workloads; on-premises or hybrid solutions retain control of data residency at the cost of operational complexity.

Cost model preferences

The pricing models vary substantially — per-user-per-month, per-concurrent-user, per-resource consumption, capital plus operational. Different models suit different customer financial preferences and consumption patterns.

Migration paths and timelines

VDI migrations are not trivial. The base patterns:

Like-for-like migration

Replace Horizon with the closest equivalent (typically Citrix or Parallels for self-managed deployments, WorkSpaces or AVD for managed). User experience changes minimally; back-end changes substantially. Timeline: 6-12 months for a mid-size enterprise; longer for complex deployments.

Cloud-shift migration

Replace on-premises Horizon with a cloud-managed alternative (WorkSpaces, Windows 365, Cloud PC). User experience may change; operational model changes substantially. Timeline: 9-18 months including identity and connectivity work.

Architectural reset

Use the migration as an opportunity to reconsider the VDI architecture — moving from one large pool to per-team Cloud PCs, or from heavy VDI to lighter remote application delivery, or from VDI to managed laptops with EDR. Timeline: 12-24 months, with significant user-experience changes.

Hybrid retention

Retain Horizon/Omnissa for some populations while migrating others to alternatives. Suitable when specific use cases are well-served by Horizon and others are not. Timeline: ongoing, with phased commitments.

The application compatibility dimension

VDI workloads typically run a mix of applications, and not all alternatives handle all applications equally. Areas to check:

• Custom applications with specific environment dependencies — these need testing on the target platform before commitment
• Graphics-intensive applications (CAD, simulation, design) — GPU support varies between alternatives
• USB and peripheral redirection — important for industries with specific hardware (scanners, signature pads, medical devices)
• Multimedia and unified communications — Teams, Zoom, and equivalent applications behave differently across VDI platforms
• Multi-monitor support — the number of monitors and resolutions supported varies
• Endpoint device support — zero clients, thin clients, mobile devices, BYOD scenarios all have different compatibility profiles

Application compatibility testing should be an early step in any VDI migration; surprises in this area can derail timelines and force re-evaluation of the alternative chosen.

The cost comparison

Direct cost comparison is difficult because the pricing models differ. Rough framing:

Self-managed VDI (Horizon, Citrix, Parallels) carries software licensing plus infrastructure plus operations costs. Total cost per user typically runs $30-80 per user per month at enterprise scale, depending heavily on the architecture and operational maturity.

Cloud-managed VDI (WorkSpaces, AVD, Windows 365) carries per-user-per-month pricing that includes infrastructure but excludes some operational costs. Total cost typically runs $40-100 per user per month, depending on configuration and usage patterns.

Lighter alternatives (Chrome Enterprise, RAS, Cloud Workstations) can run lower at $15-40 per user per month for the right use cases, but may not cover all the functionality of full VDI.

Comparing on like-for-like cost requires careful normalisation. The cheapest option per user is not always the cheapest after operations, identity, networking, and security are included.

Common mistakes in VDI migration

Choosing the alternative before understanding the use cases

VDI use cases vary enormously even within a single organisation. Choosing the alternative without an honest analysis of what the platform needs to support tends to produce surprises during migration.

Underestimating the identity and access work

VDI changes typically require identity-system updates, conditional-access policy changes, and endpoint configuration changes that can be larger than the VDI migration itself.

Skipping pilot and reference users

VDI is a user-experience platform; user feedback on a real pilot deployment is essential before broad migration.

Not negotiating the Horizon/Omnissa exit

The exit terms from the existing Horizon licence can be negotiated, particularly during the transition period. Customers who accept default exit terms typically overpay for the transition.

Locking into the new platform too quickly

Long-term commitments to a new VDI platform should be made after the pilot, not before. Initial commitments should preserve flexibility.

Treating VDI as a pure cost-saving exercise

VDI is operationally significant; cost-driven decisions that compromise the user experience or operational model produce productivity costs that exceed the licensing savings.

Frequently asked questions

Will Omnissa continue to develop Horizon?

Omnissa has committed to continued development and has shipped product updates since the carve-out. Long-term viability depends on commercial performance and KKR's strategic plans; signals are positive but not certain.

Can we keep Horizon on Broadcom-owned vSphere indefinitely?

Technically yes; the integration continues to work. The strategic question is whether two-vendor optimisation (Broadcom for hypervisor, Omnissa for VDI) is preferable to a single-vendor alternative or a cloud-managed model.

How long does a typical migration take?

9-18 months for a deliberate enterprise migration of 5,000-15,000 users. Smaller migrations can be faster; very large or complex migrations can take 24+ months.

Is Citrix actually cheaper than Horizon under Broadcom pricing?

Sometimes yes, sometimes no — depends on the deal structure. Citrix's own pricing has trended up since the private-equity acquisition. The comparison should be done with current quotes, not historical assumptions.

Can we move to cloud-managed VDI in phases?

Yes — phased migrations are common, with specific user populations or use cases moving first. The Horizon/Omnissa entitlement scales with active users, allowing the customer to reduce as users migrate.

What happens to existing VDI images during migration?

Images typically need to be rebuilt for the new platform; direct image migration is rarely supported. Image build is part of the migration effort.