This Citrix Virtual Apps and Desktops licensing guide exists because CVAD is the product most enterprises actually mean when they talk about their Citrix estate, and how you license it is one of the largest recurring cost decisions you make. CVAD delivers applications and full desktops to users from a central data center or cloud, and since perpetual licensing ended in October 2022 it is licensed entirely by subscription, counted by user, device, or concurrent models, and frequently bundled inside broader constructs. As of 2026, with Cloud Software Group repricing renewals at widely reported increases of 50 to 200 percent, the difference between licensing CVAD to your real usage and accepting the vendor's default is measured in millions for a large estate.
What Citrix Virtual Apps and Desktops licensing covers
CVAD, Citrix Virtual Apps and Desktops, delivers two related things. Virtual apps stream a single application to a user without installing it locally, and virtual desktops run a complete desktop session centrally and present it to the user's device. The processing happens on servers you control or on Citrix Cloud, and the user connects to a session rather than running the software on their own machine. This central delivery is what makes Citrix valuable for security, manageability, and remote access, and it is exactly what the subscription pays for. CVAD is the engine. The license is how access to that engine is counted and billed.
The product was formed by merging and rebranding the older XenApp and XenDesktop lines, so agreements signed years ago may still reference those names while pointing to the same underlying capability. Those legacy entitlements generally map forward to CVAD, although how they map under current subscription packaging depends on the specific agreement and should always be confirmed in writing before a renewal or migration.
How CVAD is counted: the three models
Every CVAD license is counted in one of three ways, and the choice is the single largest lever in the cost. The same product can cost very different amounts depending on which model you choose, and the right answer comes from your own usage data rather than the vendor's price sheet.
Per user
A per user license is tied to a named individual who can connect from any device, as often as they like. You buy one entitlement per person. This fits dedicated, one to one environments where most people use Citrix on their own assigned devices, such as finance teams, developers, and back office functions. It is the model the vendor most often steers buyers toward, because user counts are the largest and the easiest to grow over time.
Per device
A per device license is tied to a specific machine that any number of people can use. You buy one entitlement per device. This fits shared hardware with rotating users, such as clinical workstations, manufacturing terminals, or retail point of sale machines, where many staff share a smaller number of devices across a day.
Concurrent
A concurrent license is consumed by an active session at a point in time, drawn from a shared pool, so you size to peak simultaneous use rather than to headcount. This fits high headcount, low simultaneity populations such as shift based contact centres, seasonal workforces, and healthcare estates where staff rotate across wards and shifts. It is covered in depth in our guide to Citrix concurrent user licensing explained, and compared with the others in Citrix license types, user, device, and concurrent compared.
The product is the same. The counting model is what decides the bill, and the model is the buyer's decision to make, not the vendor's.
Where CVAD sits in current packaging
In current Cloud Software Group packaging, CVAD entitlements usually sit inside a subscription and are frequently folded into broader constructs such as the Citrix Platform license or Universal Hybrid Multi Cloud licensing. These bundles can include capability well beyond apps and desktops, and the commercial motion is to sell the broad package whether or not the estate uses everything inside it. For some buyers the bundle genuinely fits. For many it is capability paid for and never deployed, which is one of the most common places CVAD overspend hides.
The packaging also blurs the line between on premises CVAD and the cloud managed Citrix DaaS, because hybrid rights can grant both delivery options under one entitlement. The licensing question therefore becomes less about which product name appears on the quote and more about which delivery and feature rights your entitlement actually grants. That detail decides what you can do without buying more, and it matters most when a migration or renewal is on the table. The broader move to subscription is covered in Citrix subscription licensing, how it works.
Where CVAD overspend hides
Three patterns produce most of the waste we find in CVAD estates. The first is the counting model. An estate licensed per user when its real usage is highly shared pays for entitlements that sit idle most of the day, when a concurrent or device model would cover the same work for far less. The second is account hygiene. Dormant accounts, departed staff, and duplicate identities inflate the count, and because every true up measures against that inflated figure, the waste compounds year after year unless the estate is cleaned before reporting. The third is the bundle. A broad Platform or Universal Hybrid Multi Cloud package that includes capability the estate never touches is a recurring premium paid for nothing.
None of these are visible from the vendor's quote, because the quote is built on the counts and packaging the vendor proposes. They become visible only when you measure your own usage and read your own consumption data, which is why measurement is the foundation of every CVAD cost decision. The same discipline also protects you under a review, because the data that sizes the purchase is the data that defends the position.
How to license CVAD to real usage
The method is a short sequence run before any vendor conversation. First, measure real usage from your own data: peak concurrent sessions, genuine named users, and shared devices, so you can compare all three models on equal footing rather than on the vendor's framing. Second, clean the estate, reclaiming dormant and departed accounts and removing duplicates so the count reflects reality. Third, segment the estate wherever the usage pattern changes, because the cheapest answer for a shift floor is rarely the cheapest answer for a head office, and a large estate is almost never uniform. Fourth, price each model against the real quantities it would require, not against list price per license, and choose the lowest compliant total for each segment, which across a mixed estate is frequently a blend.
One caution holds throughout. The cheapest model on paper is not worth choosing if it cannot be administered cleanly or defended under audit. Concurrent licensing in particular demands accurate, ongoing session measurement, so it suits organisations that can maintain that discipline. The right model is the one that is both lowest cost and defensible, which is exactly why the measurement has to be sound. This analysis routinely surfaces savings that no price renegotiation alone could reach, because it removes quantity rather than shaving rate, and it is the core of what our Citrix licensing advisory team does in an assessment.
CVAD and your renewal
CVAD licensing and your renewal are the same conversation, because the counts and packaging you carry into a renewal set the floor the vendor negotiates up from. Arriving at a renewal with a measured concurrency curve, a cleaned account inventory, and a segmented model is what shifts the discussion from the vendor's preferred count to the count your usage actually supports. Doing that work 9 to 12 months before the renewal date is the difference between negotiating from evidence and accepting an uplift on the existing position. For the wider renewal picture, see our pillar on Citrix licensing fundamentals and the guidance throughout the licensing cluster.
Frequently asked questions
How is Citrix Virtual Apps and Desktops licensed?
Citrix Virtual Apps and Desktops, or CVAD, is licensed by subscription since perpetual licensing ended in October 2022. It is counted by user, device, or concurrent models and is frequently packaged inside broader constructs such as the Citrix Platform license and Universal Hybrid Multi Cloud licensing. The right counting model depends on how your users actually consume it.
What is the difference between CVAD and Citrix DaaS licensing?
CVAD delivers apps and desktops and can run on premises or be managed from Citrix Cloud, while Citrix DaaS is the cloud managed service version of that delivery. Many agreements include both delivery options under a hybrid right, so the licensing question is less about which product and more about which delivery rights your entitlement grants.
Which CVAD licensing model is cheapest?
There is no single cheapest model. Per user fits dedicated one to one usage, per device fits shared hardware with rotating users, and concurrent fits high headcount with low simultaneity. The cheapest compliant position usually mixes models across segments of the estate, and only measured usage tells you which fits where.
Where does CVAD overspend usually hide?
In the counting model, in dormant and duplicate accounts carried at every true up, and in broad bundles that include capability the estate never uses. As of 2026, accepting the vendor's default per user count and packaging is the most common source of CVAD overspend.
Can older XenApp and XenDesktop entitlements still be used?
XenApp and XenDesktop were merged and rebranded into CVAD, so those legacy entitlements generally map forward. How they map under current subscription packaging depends on your specific agreement, which should be confirmed in writing before any renewal or migration.