Understanding Citrix license types is the first decision that determines what your estate costs, and it is the one buyers most often get wrong. The three main models, user, device, and concurrent, each count access differently, and the gap between the right model and the wrong one for your usage can run to a large share of your annual spend. As of 2026, with Cloud Software Group repricing renewals at widely reported increases of 50% to 200%, choosing the model that matches how people actually use Citrix is no longer a technical footnote. It is one of the few levers fully inside your control.
The three Citrix license types at a glance
All three models grant the same product. What differs is the unit they count and bill. That unit is the whole game, because it decides how your real usage maps to what you pay.
User licensing
A user license is assigned to a named person. That individual can access Citrix from any device, anywhere, as often as they like, and the license follows them. You buy one license per named user regardless of how many devices they use or how often they connect. User licensing is simple to administer and predictable to count, which is exactly why the vendor favours it: the number of named users in an organization is large and easy to inflate.
Device licensing
A device license is assigned to a named machine. Any person who logs in from that device is covered, and the license follows the hardware rather than the human. Device licensing fits environments where many people share a smaller pool of machines, such as a clinical workstation used across shifts, a shop floor terminal, or a shared kiosk. You buy one license per device, not per person, so a single license can cover many users over a day.
Concurrent licensing
A concurrent license counts simultaneous active sessions rather than named users or devices. If you own 500 concurrent licenses, up to 500 sessions can run at the same time, drawn from a much larger population of potential users. When a session ends, the license returns to the pool for the next person. Concurrent licensing fits estates with high total headcount but low simultaneous use, the classic example being shift workers or task based staff who are never all online at once.
The three models grant the same product. The only thing that differs is what they count, and that is what decides your bill.
How the models compare on cost
List price per license rises roughly in the order user, device, concurrent, because a concurrent license can serve many people and is priced to reflect that. But list price comparison is a trap. The right comparison is total cost for your estate, which is unit price multiplied by the quantity each model requires, and the quantities differ enormously.
Consider an estate of 5,000 named staff where, at peak, only 1,500 are ever on Citrix at once because the rest work different shifts. Licensed per user, you buy 5,000 entitlements. Licensed concurrently, you buy closer to 1,500 plus headroom. Even though each concurrent license costs more, the total can be dramatically lower because you buy a third of the quantity. Reverse the example, an office of 2,000 people who all log in every morning, and concurrency offers no saving because peak concurrency nearly equals headcount, so user licensing wins on simplicity and price.
This is why a model decision can never be made from a price sheet. It is made from your concurrency curve. Measuring peak simultaneous use correctly is the single most valuable input, and it is covered in our guidance on measuring Citrix peak concurrency.
Which model fits which environment
Patterns repeat across enterprises. User licensing suits dedicated, one to one environments where most people use Citrix at the same time on their own assigned devices: corporate knowledge workers, developers, finance teams. Device licensing suits shared hardware with rotating users: clinical workstations, manufacturing terminals, retail points of sale, training rooms. Concurrent licensing suits high headcount, low simultaneity populations: call centers with shift patterns, seasonal or task based workforces, and large estates where total named users vastly exceed peak active sessions.
Most large estates are not uniform. A bank may have dedicated office users best served per user, branch terminals best served per device, and a shift based operations floor best served concurrently. The lowest cost compliant position often mixes models across segments rather than forcing the whole estate onto one. Identifying those segments is the heart of good license allocation.
How the vendor steers the choice
The model decision is commercial, and the vendor has a preference. Per user counts are the largest and the easiest to grow, so sales motions and current packaging tend to steer buyers toward user licensing and away from concurrent. The framing is usually simplicity: one license per person is easy to administer and easy to true up. That convenience is real, but it is convenience the buyer pays for, sometimes heavily, when the underlying usage is highly shared. As of 2026, some packaging changes under Cloud Software Group have narrowed concurrent availability for new purchases, which is itself a reason to confirm exactly what your agreement permits before assuming a model is off the table.
The buyer side discipline is to treat the model as a number you defend with data, not a default you accept. When you arrive with a measured concurrency curve and a segmented estate, the conversation shifts from the vendor's preferred count to the count your usage actually supports.
Where license types sit in current packaging
User, device, and concurrent are counting models, and they operate inside Citrix subscription packaging rather than alongside it. Since perpetual licensing ended in October 2022, Citrix is subscription only, and these models now sit within constructs such as the Citrix Platform license and Universal Hybrid Multi Cloud licensing. The deployment flexibility those packages add does not remove the counting question. You still choose how access is measured, and that choice still drives cost. For how the subscription layer itself works, see our guide to Citrix subscription licensing.
A practical way to choose
The decision comes down to four measured numbers, gathered before any vendor conversation. Count your named users who genuinely need access. Count your shared devices and how many people rotate through them. Measure peak concurrent sessions across a representative period, not an average. Then price each model against those real quantities and segment the estate where the patterns differ. The model that produces the lowest compliant total for each segment is the answer, and it is frequently a mix. This is the work we do in a licensing assessment, and it routinely surfaces savings that no renegotiation of price alone could reach, because it removes quantity rather than shaving rate.
One caution: the cheapest model on paper is not worth choosing if it cannot be administered or if it risks non compliance under audit. Concurrent licensing demands accurate session measurement, and device licensing demands clean device inventories. The right model is the one that is both lowest cost and defensible, which is why the measurement has to be sound enough to stand up in a review.
Switching license types at renewal
A model choice is not permanent, and a renewal is the natural moment to change it. If your estate has grown more shared, or a workforce has shifted to part time and remote patterns, the model that fit three years ago may now be the wrong one. The renewal is when you can re segment the estate and move groups to the model their current usage supports. The vendor will not propose this for you, because the most common profitable direction for them is the opposite: consolidating everyone onto a per user count. Bringing a re segmented proposal to the table, backed by fresh measurement, is how you reset the model in your favour rather than drifting further into the vendor's preferred count.
Switching does carry friction. A change from concurrent to user, or the reverse, alters how you administer and report entitlements, and it may interact with support tiers and bundle terms. The friction is manageable, but it is a reason to plan the switch as part of a renewal project rather than attempt it mid term, where the contract usually offers less flexibility. The work pays for itself when the new model removes a quantity the old one was forcing you to carry.
Common mistakes when choosing a Citrix license type
Four mistakes recur across enterprises. The first is licensing to headcount instead of usage, buying one user license for every employee on the directory regardless of whether they touch Citrix, which is the single largest source of overspend. The second is accepting the vendor's default model without testing the alternatives against measured data, so a highly shared estate ends up on per user counts it does not need. The third is treating the whole estate as uniform, missing the segments where a different model would be far cheaper. The fourth is choosing a model the organization cannot measure accurately, then over provisioning to stay safe under audit, which quietly gives back the saving the model was meant to deliver.
Each mistake has the same root: deciding the model commercially without the usage data to support it. The fix is always the same, measure first, segment, then price every model against the real numbers. That sequence is what separates an estate that pays for what it uses from one that pays for what the vendor counted.
Frequently asked questions
What are the main Citrix license types?
The main Citrix license types are user, device, and concurrent. User licensing assigns an entitlement to a named person, device licensing assigns it to a named machine, and concurrent licensing counts simultaneous active sessions rather than named entities. As of 2026 these sit within Citrix subscription packaging such as the Platform license.
Is concurrent licensing cheaper than user licensing?
It depends on your usage pattern. Concurrent licensing is cheaper when many people share access but few are active at once, such as shift or task workers. User licensing is cheaper when most people use Citrix at the same time. The right answer comes from measuring real peak concurrency, not from a list price comparison.
Can I still buy Citrix concurrent licenses in 2026?
Availability of concurrent licensing depends on current Cloud Software Group packaging and your agreement. Some estates retain concurrent entitlements while new packaging steers buyers toward user or device models. Confirm what your specific subscription allows, because the vendor benefits when buyers move to per user counts.
How do I choose between user, device, and concurrent licensing?
Match the model to how people actually use Citrix. Measure named users, shared devices, and peak simultaneous sessions, then compare the cost of each model against those numbers. Shared and shift environments favour concurrent or device, dedicated one to one environments favour user.
Does the wrong Citrix license type cost much?
Yes. Choosing the wrong model routinely inflates Citrix cost by a large margin, because the vendor's default rarely matches your usage. An estate with high sharing licensed per named user, or a one to one estate licensed concurrently and forced to over provision, both overpay. Measurement is what prevents it.
For the full picture, see our Citrix licensing fundamentals pillar, and related guidance on subscription licensing, license allocation best practices, and measuring peak concurrency.