Before you compare Horizon Cloud against on-premises Horizon, you need the one fact that reframes the entire decision: Horizon is not a VMware product anymore. In 2024, Broadcom divested VMware’s End-User Computing division, and the desktop virtualization platform now belongs to an independent company called Omnissa. The software you are evaluating is Omnissa Horizon, and both the on-premises and cloud editions have moved to subscription licensing under new ownership. Any comparison written before mid-2024, including the one this article used to be, is describing a product that no longer exists under that name.
That ownership change is not a footnote. It reset the licensing model, the roadmap, and the branding all at once, and it landed right as the market tilted decisively toward desktops delivered as a service. So the real question is no longer just cloud versus on-premises. It is how to get the control of on-premises Horizon and the flexibility of Horizon Cloud without betting your desktop estate on a licensing model still settling into place. This guide brings the comparison current and shows where a managed private cloud fits between the two.
What Changed: VMware Horizon Is Now Omnissa Horizon
Horizon is virtual desktop and application software. It connects endpoint devices, from laptops to thin clients to phones, to virtual desktops and published apps running in a data center or cloud, so the compute lives centrally and only pixels travel to the user. That core has not changed. Almost everything around it has.
In February 2024, KKR agreed to acquire VMware’s End-User Computing business from Broadcom for roughly $4 billion. The division was rebranded Omnissa, and the deal closed on July 1, 2024, creating an independent company with around 26,000 customers. Omnissa now owns Horizon along with Workspace ONE for endpoint management, App Volumes for application delivery, and the digital employee experience tooling that used to sit under VMware EUC.
The product names to use going forward are precise. The on-premises edition is Omnissa Horizon 8, whose latest release, Horizon 8 2512, shipped in December 2025 and added support for Nutanix AHV among other changes. The cloud-delivered edition is Omnissa Horizon Cloud, a software-as-a-service control plane. Omnissa has also introduced a next-generation Horizon control plane and a Universal Broker that presents both on-premises and cloud desktops to users under a single URL. If your notes still say “VMware Horizon View” or “VMware Horizon Cloud on Azure” as if Azure were the only option, they are two product generations behind.
Horizon Cloud vs On-Premises Horizon: The Real Differences
The two models differ most in who runs the management plane and where the desktops physically live. Everything else follows from those two choices.
With on-premises Omnissa Horizon 8, you run and patch the full management stack yourself, the connection servers, brokering, and databases, on VMware vSphere infrastructure you own. You control every layer, integrate tightly with vSphere, vSAN, and NSX, and keep data inside your own walls. The trade is capital cost, hardware refresh cycles, and the operational burden of keeping the whole stack current and secure.
With Omnissa Horizon Cloud, the management and control plane is always cloud-hosted and operated by Omnissa. You manage the desktop workloads, not the plumbing that brokers them. Crucially, the desktops themselves can run in more than one place: Horizon Cloud spans Microsoft Azure, Amazon WorkSpaces Core, on-premises vSphere, and OpenStack, so the control plane stays SaaS while the desktops sit wherever your latency, cost, and data-residency needs dictate. On-premises Horizon 8 pods can even connect up to the cloud control plane through a Horizon Edge Gateway to consume SaaS services like Universal Broker and image management, which is how the two worlds now blend.
One thing that does not change with the deployment model is the end-user experience. Horizon delivers desktops over the Blast Extreme display protocol, tuned for everything from a call-center thin client to a designer pushing a GPU workstation over a home connection. Whether the desktop is brokered from your data center or a cloud control plane, the user sees the same session, the same peripherals, and the same performance profile. That consistency is part of why the cloud-versus-on-premises choice can be made on cost and control rather than on user experience: you are moving where the desktop runs and who manages it, not what the person in front of it actually gets.
| Dimension | Horizon Cloud (DaaS) | On-premises Horizon 8 |
|---|---|---|
| Management plane | Cloud-hosted, run by Omnissa | You run and patch the full stack |
| Where desktops run | Azure, AWS WorkSpaces Core, vSphere, OpenStack | Your own vSphere data center |
| Cost model | Subscription, consumption-based, no upfront | Capital-heavy, term or subscription licenses |
| Scaling | Allocate and power down on demand | Provision hardware ahead of need |
| Control and data locality | Shared control plane, flexible desktop placement | Maximum control, tight vSphere/NSX integration |
| Best fit | Hybrid work, seasonal scale, exiting data-center ops | Regulated, latency-sensitive, GPU, air-gapped |
Cost: Capital Certainty vs Consumption Flexibility
The financial picture is where most decisions actually turn. On-premises Horizon is a capital story. You buy hardware, licenses, power, and cooling sized for your peak, and that capacity sits idle when demand dips. For a workforce with steady, predictable desktop counts, that can be efficient. For anyone with seasonal swings, retail teams staffing up for holiday demand, a firm running enrollment periods, a business absorbing an acquisition, the idle capacity is pure waste.
Horizon Cloud flips that to consumption. You create desktops when you need them and power them down when you do not, with built-in automation to deallocate session hosts and schedule power-off overnight, on weekends, and over holidays. There is no upfront hardware and no capacity you pay to leave dark. The trade is that a per-desktop monthly fee, run continuously at scale, can exceed the amortized cost of owned infrastructure for a stable, always-on population. The honest answer is that neither model wins universally. Steady and predictable favors ownership. Variable and bursty favors consumption. Most organizations land on a mix, which is exactly why the industry moved toward a single control plane that can broker both. The discipline that pays off is modeling your real usage pattern first, the number of concurrent desktops by hour and by season, then pricing each model against that curve rather than against a vendor’s headline per-desktop rate. A desktop that runs eight hours a day, five days a week costs very differently under consumption billing than one left powered on around the clock, and that single detail often decides the whole comparison.
Why This Decision Matters More in 2026
Two forces have raised the stakes. The first is the licensing upheaval from the Broadcom split and the Omnissa spinoff, which ended the old perpetual VMware EUC licensing and pushed everything to subscription. Organizations on legacy contracts had to migrate, and the cost and terms of desktop virtualization are being renegotiated across the board.
The second is that the market has clearly chosen the delivery model. Gartner projects that desktop-as-a-service spending will grow from $4.3 billion in 2025 to $6.0 billion in 2029, and that by 2027 virtual desktops will be cost-effective for 95% of workers, up from 40% in 2019. Net-new desktop virtualization is now almost exclusively DaaS, with on-premises deployments either migrating to cloud delivery or adopting a cloud control plane for all but specialized cases. Microsoft’s own documentation now describes Omnissa Horizon as a cloud service delivering desktops on Azure, a sign of how thoroughly the branding and the model have shifted. The direction of travel is not subtle, and planning a fresh on-premises-only deployment in 2026 means swimming against it.
Which Model Fits Which Workload
The right answer is rarely the same for the whole company. It is usually per workload and per team. A few patterns hold up well.
- Regulated and data-sovereign workloads favor on-premises or a managed private cloud. Healthcare, finance, and legal teams that must prove where data lives and who can reach it get the cleanest compliance story when the desktops sit on dedicated infrastructure with clear residency.
- GPU and latency-sensitive workloads such as CAD, engineering, media, and design want dedicated performance and low, consistent latency. These do well on private cloud with GPU-accelerated desktops rather than on shared, variable public-cloud capacity.
- Seasonal and variable teams are the classic case for consumption-based Horizon Cloud. Retail scaling for the holidays, tax and audit firms in busy season, schools during enrollment, all benefit from spinning desktops up and powering them down without paying for idle hardware the rest of the year.
- Distributed and hybrid workforces that need consistent access from anywhere lean toward a cloud control plane, which brokers users to the nearest desktop capacity and centralizes management across sites.
- Mergers and rapid change favor the flexibility to stand up desktops quickly for a newly acquired group without a hardware project, then rationalize later.
Notice how many of these want two things that used to be in tension: the control and performance of dedicated infrastructure, and the flexibility to scale without a capital cycle. That combination is exactly what the managed private cloud model is built to deliver.
What the Ownership Change Means for Your Migration
If you are already running an older VMware Horizon deployment, the Omnissa transition adds a few concrete things to plan for. Legacy VMware EUC entitlements had to move to Omnissa contracts, so the first step is confirming your current licensing position and what renewal now looks like under subscription terms. Do not let an old perpetual-era assumption drive a 2026 budget.
Architecturally, the good news is that Omnissa built the transition to be gradual. Universal Broker can present existing on-premises Horizon 8 pods and cloud desktops to users under one URL, and a Horizon Edge Gateway lets an on-premises pod consume cloud control-plane services like image management and monitoring without a rip-and-replace. That means you can modernize in stages: keep desktops where they perform best today, adopt the SaaS control plane for management, and shift workloads to consumption where the economics favor it. The wrong move is to treat this as a forced, all-at-once cloud migration. The right move is to use the ownership change as the prompt to review your desktop strategy deliberately, workload by workload, and to decide who should carry the underlying platform.
For many mid-market teams, the conclusion of that review is that they do not want to run desktop-virtualization infrastructure at all. They want the desktops, the control, and the compliance, delivered and managed for them. That is where the third path comes in.
The Middle Path: Managed DaaS on a Private Cloud
The cloud-versus-on-premises framing hides a third option that resolves the tension for a lot of businesses. You can run Omnissa Horizon on vSphere inside a managed private cloud, delivered to you as a subscription desktop-as-a-service, and optionally attach the Omnissa control plane on top. That gives you the control, performance, and data locality of on-premises Horizon with the consumption economics and offloaded operations of the cloud, and none of the burden of owning the data center.
This is exactly what IT Vortex delivers. Our Desktop as a Service (DaaS) runs on VMware-powered private cloud hosting, so your virtual desktops get dedicated, high-performance infrastructure and clear data residency, billed as a predictable subscription instead of a capital project. Because the same platform underpins our broader VMware cloud services and is wrapped in a fully managed service, you get the licensing, patching, security, and lifecycle work handled for you. GPU-accelerated desktops for design and engineering workloads, seasonal scale for variable teams, and regulated-industry data control all fit the same model.
Here is the point to carry out of this comparison. The old question, cloud or on-premises, assumed you had to own one or the other. You no longer do. Horizon changed hands, changed names, and changed licensing, and in the same stretch the market decided that desktops are something you consume, not something you build. The winning move for most mid-market organizations is not to pick a side but to get on-premises-grade control delivered as a managed, subscription service. That way the platform change happening around you becomes someone else’s operational problem, and you just get working desktops. Talk with IT Vortex about delivering Omnissa Horizon desktops from a managed private cloud built for your workloads.
Horizon Cloud vs On-Premises: Frequently Asked Questions
Is VMware Horizon still called VMware Horizon?
No. Broadcom divested VMware’s End-User Computing division to KKR, and the deal closed on July 1, 2024. Horizon is now owned by an independent company called Omnissa, so the correct names are Omnissa Horizon 8 for the on-premises edition and Omnissa Horizon Cloud for the cloud-delivered edition.
What is the difference between Horizon Cloud and on-premises Horizon?
With on-premises Horizon 8 you run and patch the entire management stack on your own vSphere infrastructure. With Horizon Cloud, Omnissa hosts and operates the management control plane as a service, while your desktops can run in Azure, AWS WorkSpaces Core, on-premises vSphere, or OpenStack. On-premises maximizes control and data locality; Horizon Cloud offloads operations and bills on consumption.
Is Horizon Cloud cheaper than on-premises?
It depends on your demand pattern. Horizon Cloud avoids upfront hardware and lets you power desktops down when they are idle, which wins for seasonal or variable workforces. For a large, steady, always-on population, the amortized cost of owned infrastructure can be lower. Many organizations use a hybrid, or a managed DaaS, to balance the two.
Can I run Omnissa Horizon in a managed private cloud?
Yes. Horizon 8 runs on vSphere, so a provider can host it in a managed private cloud and deliver it as a subscription desktop-as-a-service. You get on-premises-grade control, performance, and data residency without owning the data center, and the provider handles licensing, patching, and lifecycle management. This is how IT Vortex delivers DaaS.
