A concurrent user license allows any user in the population to access the software, as long as the count of simultaneous active sessions stays within the license pool. Concurrent pools were historically sized at 1 to 4 or 1 to 8 of total named user population, which meant a 100 license pool could serve 400 to 800 identities under staggered shifts. Cloud delivery and per user SaaS subscriptions have made the model rare outside specialist engineering categories and certain legacy on premises deployments.
Concurrent User Licensing: A license model where the license count caps simultaneous active sessions rather than identified individuals. Any employee can access the software so long as the total session count stays within the purchased pool. Sessions release back to the pool on logout or timeout, after which another user can connect.
Concurrent licensing is the older sibling of named user licensing. It dominated client server software pricing through the 1990s and into the 2000s when most enterprise software ran on premises and identity systems were primitive. Reporting tools, CAD suites, terminal services, and ERP modules with low session duration all used the model. A buyer with 2,000 employees could often run on a 250 concurrent license pool because reporting sessions were short and staggered.
The model died for two reasons. Vendors realized concurrent pools cap their revenue growth even as customer headcount expands, so the commercial incentive moved toward identity. Cloud delivery then made identity the natural metering unit because every session must authenticate. Oracle retired most concurrent options by 2010. SAP retained concurrent for certain industry solutions only. Concurrent survives most strongly in engineering CAD software, where vendors like Autodesk and Siemens still offer network license pools.
We benchmark concurrent pool sizing and migration cost to named user across 320 legacy contracts. Send us your current pool and we return migration intelligence in 48 hours.
The single biggest cost event in concurrent licensing is forced migration to named user at renewal. Vendors price the swap on total named identity headcount, not on prior pool size. A buyer who ran on a 250 concurrent pool for 2,000 employees may face an 8x cost increase when forced to license each named user individually. Negotiation tactics include staged migration, named user minimum caps, and grandfathered pricing on the original pool for legacy systems still in scope.
For related vocabulary, see the named user licensing definition, the per seat pricing definition, and the ELA definition. The glossary hub covers the broader pricing vocabulary. For renewal mechanics that often trigger the named user conversion, see the auto renewal clause benchmark.
A concurrent user license allows any user in the population to access the software, as long as the total number of simultaneous active sessions stays within the license count. A 100 concurrent license pool can serve 400 or more named identities if usage is staggered across shifts or time zones.
Concurrent user pools were historically sized between 1 to 4 and 1 to 8 of total named user population, depending on session duration and shift patterns. Call center applications used tighter ratios near 1 to 2. Reporting and BI tools used wider ratios near 1 to 10.
Cloud delivery and per user SaaS subscriptions made identity the natural metering unit. Vendors prefer named user models because they grow with employee headcount. Concurrent licensing survives in legacy on premises deployments and in specialist categories like engineering CAD software.
Send us the proposal or renewal. We return discount, term, and unit price intelligence in 48 hours.