Omnissa Horizon (VMware Horizon) Pricing Explained [2026 Guide]
What Is Omnissa Horizon (Previously VMware Horizon)?
Omnissa Horizon, formerly known as VMware Horizon, is a platform for delivering, managing, and securing virtual desktops and applications. It provides IT administrators tools for provisioning virtual desktops and apps on both on-premises infrastructure and multiple cloud environments.
VMware Horizon costs vary based on licensing type, features, and deployment model (on-premise or cloud). Cloud subscription pricing, for example, starts at around $4.67 per user per month for Horizon Apps Standard. On-premise perpetual licenses can cost thousands of dollars for a basic package and require additional support costs. We explore pricing options in more detail below.
Secure Data on Unmanaged Laptops – Without VMware Horizon Complexity
See how Venn enables secure BYOD workforces without the cost, latency, and management headaches of VMware Horizon.

In this article:
Key Factors That Influence Omnissa Horizon Costs
User Licensing Structures
Omnissa Horizon offers licensing models primarily based on the number of users, either as named user or concurrent user licenses. Named user licenses are assigned to specific individuals, making them suitable for organizations with a stable workforce and predictable remote desktop needs. Concurrent user licensing allows a pool of users to access the environment simultaneously up to a licensed maximum, which is often more cost-effective for businesses with shift work or temporary staff.
Infrastructure Components Required for Horizon Deployments
For on-premises Horizon environments, foundational infrastructure includes compute (servers), storage, network equipment, and endpoint devices for users. Core Horizon components such as connection servers, unified access gateways, and management servers must run on reliable, well-spec’d hardware to ensure user performance and service reliability. Over-provisioning or under-provisioning physical resources can directly affect costs and user experience.
Cloud vs. On-Premises Cost Variables
Deploying Omnissa Horizon in the cloud shifts cost considerations from capital expenditures (CapEx) to operating expenditures (OpEx). Cloud models typically offer pay-as-you-go pricing, simplifying management and enabling rapid scaling, but can become costly with sustained high usage or if resources are not carefully monitored. Organizations must budget for ongoing license subscriptions, cloud storage, egress fees, and feature-based pricing tiers.
Add-Ons, Integrations, and Feature Costs
Omnissa Horizon’s base offering is often extended with add-ons for enhanced functionality, such as application virtualization (App Volumes), profile management (Dynamic Environment Manager), and security tools (VMware NSX integration). Each add-on introduces incremental licensing and infrastructure costs that must be factored into total cost of ownership. Licensing for these components may differ from the core product and often depends on the number of users or desktops managed.
Omnissa Horizon Licensing Models Explained
Omnissa Horizon offers two primary licensing models: per named user (NU) and per concurrent connection (CCU). Choosing the right model depends on how users access the system and the nature of their work patterns.
Named user (NU) licensing assigns a license to a specific individual. It is suited for environments where users consistently need access to virtual desktops, such as in organizations with fixed teams working standard hours. Each named user license remains tied to a user for up to 60 days after their last session, unless reassigned earlier due to employment termination.
Concurrent connection (CCU) licensing allows a pool of users to share licenses, with the total number of simultaneous active sessions capped by the license count. This model is efficient for environments with shift workers or shared usage patterns. For example, if 300 users access desktops during the day and 200 at night, only 300 CCU licenses are required if they don’t overlap.
In both models, Horizon bundles, which may include components like Workspace ONE Access or ThinApp, are treated as unified units. When a user initiates any component, the entire bundle is considered consumed. This means other users cannot use unused components of an active session’s bundle, even if they’re not in use.
Mixing NU and CCU licenses in the same Horizon instance is technically allowed but discouraged due to the lack of monitoring tools that differentiate between license types once activated. SaaS subscriptions further restrict mixing: NU and CCU licenses must be assigned to different subscription identifiers (SIDs), and those SIDs cannot operate within the same Horizon pod. Though multiple SIDs can connect to a single Horizon Control Plane, compliance must be actively maintained.
Similarly, mixing different Horizon SaaS or term editions is possible under certain conditions, but not all combinations are supported on a single SID. When combining editions like Horizon Universal Subscription and Horizon Enterprise Plus, each must be isolated within separate pods or control planes. Organizations should consult licensing guidelines or vendor representatives to ensure valid deployment configurations.
Horizon SaaS Edition Details
Omnissa Horizon offers several SaaS subscription editions to support different deployment models, from on-premises to hybrid and multi-cloud. Each edition includes cloud management services and varying levels of desktop and application delivery, automation, and user experience features.
Horizon universal subscription
This is the most comprehensive edition, supporting hybrid and multi-cloud deployments. It includes full desktop and application delivery for Windows and Linux, with optional VMware vSphere Foundation (VVF) for VDI. It provides features like real-time application delivery, environment management, session recording, and integration with Workspace ONE Intelligence. Organizations also get access to SaaS tools such as Universal Broker, Image Management Service, and Cloud Monitoring Service, managed via the cloud-hosted Horizon Control Plane.
Horizon cloud on Azure standard subscription
Designed specifically for single-cloud deployments on Microsoft Azure, this edition delivers virtual desktops and applications for Windows and Linux. It includes security and user experience features, real-time application delivery, and basic management tools. It lacks the hybrid deployment flexibility of the Universal edition but is optimized for Azure-hosted environments.
Horizon enterprise plus subscription
This edition supports on-premises or single-cloud deployments with features similar to the Universal edition, including full desktop and app delivery, user management, and security capabilities. It also includes SaaS-based management, though limited to single-cloud scenarios.
Horizon standard plus subscription
Targeted at organizations needing only Windows VDI, this edition offers core desktop delivery features, security, and environment management. It supports both on-premises and cloud deployments but lacks advanced app delivery or multi-cloud support. Like Enterprise Plus, it uses the Horizon Control Plane for cloud-based management.
Horizon standard subscription
A simplified version of Standard Plus, this edition offers Windows VDI with basic management and support for features like SSO and Teams optimization. It includes SaaS tools such as Universal Broker and Cloud Monitoring Service but only supports single-cloud or on-premises deployments. This edition is no longer sold to new customers, with renewals limited to existing clients.
Horizon apps universal subscription
Built for hybrid and multi-cloud app delivery, this edition supports Windows and Linux applications and multi-session desktops. It includes real-time delivery tools, power management, and SaaS services for managing hybrid environments. It’s managed through the Horizon Control Plane and allows both cloud and on-premises deployments.
Horizon apps standard subscription
Focused on application delivery for single-cloud or on-premises environments, this edition supports Windows and Linux apps and includes user management and power management tools. It excludes vSphere Foundation and hybrid features but integrates with SaaS tools like Universal Broker and Image Management Service.
Pricing Overview for Omnissa Horizon
Omnissa Horizon offers five subscription-based pricing editions, ranging from $4.67 to $12.50 per user per month. Each edition is designed to align with specific deployment models and feature requirements, allowing organizations to choose a plan based on their technical and operational needs.
- Horizon apps standard: $4.67/month (cloud)
Entry-level option focused on application delivery with environment and power management. Suitable for single-cloud or on-premises deployments where full desktop virtualization is not required. - Horizon standard plus: $5.79/month (cloud)
Provides Windows VDI support with core management and security features. Suitable for organizations needing basic desktop virtualization managed from the cloud. - Horizon apps universal: $6.00/month (cloud)
Supports hybrid cloud app delivery with management and security features. A good fit for enterprises with mixed on-premises and cloud environments. - Horizon enterprise plus: $10.71/month (on-premise)
Designed for customers deploying on-premises or in a single cloud. Includes full desktop and app delivery, management, and user experience features. - Horizon universal: $12.50/month (cloud)
This edition supports hybrid and multi-cloud deployments. Offers the complete suite of desktop and app delivery features, cloud automation, and cross-cloud management tools.
Key Limitations of Omnissa Horizon
Omnissa Horizon suffers from several technical and operational limitations that organizations should be aware of before adoption, reported by users on the TrustRadius platform:
- High licensing and infrastructure costs: Licensing fees are considered expensive, particularly for small and mid-sized businesses. Combined with the need for trained IT staff and infrastructure investments, total cost of ownership can be a barrier for smaller teams.
- Performance issues under variable network conditions: Horizon does not handle bandwidth fluctuations as efficiently as some alternatives. This can lead to slowdowns or degraded user experience during unstable network conditions, especially for remote users.
- Complex configuration and fragmented management: Configuring Horizon can be challenging for those without VDI experience. Settings are distributed across multiple systems (Group Policy Objects, configuration files, and internal consoles) which adds to the complexity.
- Poor support and outdated documentation: User reports highlight lack of responsive support, with some tickets closed without resolution. Documentation and FAQ resources are still tied to legacy VMware links, many of which are broken or outdated.
- Limited integration with legacy systems: Integrating Horizon with older enterprise systems, such as proprietary CRMs, can be inconsistent. Compatibility with legacy tools often requires additional workarounds or support.
- Gaps in mobile and client application functionality: The mobile client lacks some of the file-sharing and usability features found in the desktop version. Improvements are needed to close the gap in user experience between platforms.
- Limited database options: Horizon environments still depend heavily on Microsoft SQL Server. Organizations looking for alternative database backends may find fewer supported options.
- Training and skill requirements: Managing and maintaining Horizon environments requires specialized knowledge. However, accessible training is limited, making it harder for new admins to get up to speed without paid resources.
Related content: Read our guide to VMware Horizon alternatives
Venn: Ultimate VDI Alternative
With Venn, you can eliminate the burden of purchasing and securing laptops and managing virtual desktops (VDI.) Unlike virtual desktops, Venn keeps users working locally on natively installed applications without latency – all while extending corporate firewall protection to business activity only.
Similar to an MDM solution but for laptops, work lives in a company-controlled Secure Enclave installed on the user’s PC or Mac, where all data is encrypted and access is managed. Work applications run locally within the Enclave – visually indicated by Venn’s Blue Border™ – protecting and isolating business activity while ensuring end-user privacy.
Key features include:
- Zero trust architecture: Uses a zero trust approach to secure company data, limiting access based on validation of devices and users.
- Visual separation via Blue Border: Visual cue that distinguishes work vs. personal sessions for users.
- Supports turnkey compliance: Using Venn helps companies maintain compliance on unmanaged Macs with a range of regulatory mandates, including HIPAA, PCI, SOC, SEC, FINRA and more.
- Granular, customizable restrictions: IT teams can define restrictions for copy/paste, download, upload, screenshots, watermarks, and DLP per user.
- Secure Enclave technology: Encrypts and isolates work data on personal Mac or PC computers, both for browser-based and local applications.
To see Venn in action, you can book a demo here.