The short answer to what is pooled capacity license: it is a licensing model that grants a shared allowance of capacity, such as bandwidth, throughput, or instances, that can be drawn down and allocated flexibly across multiple appliances or environments rather than fixed to a single one. In NetScaler licensing, a pooled capacity license lets you distribute throughput from a common pool wherever demand sits at a given moment. As of 2026 it is one of the main alternatives to rigid per appliance licensing, and it suits estates whose traffic is variable or distributed.
What the term means
A pooled capacity license treats capacity as a central allocation rather than a fixed grant tied to one device. Instead of buying a set throughput for each appliance, you buy a pool, and individual instances draw what they need from it and return it when demand falls. The same total capacity can serve a busy data center in the morning and a different site in the afternoon, because the entitlement follows the demand rather than the hardware. This is what makes the model attractive for dynamic, hybrid, and multi site environments where load shifts around the estate.
A capacity pool follows the demand, not the hardware. Its value is flexibility, and its trap is buying more pool than you draw.
Where it appears in your agreement
Pooled capacity terms appear in NetScaler and related infrastructure agreements, specified by the total pool size and the rules for how instances allocate and release capacity. Your order documents will define the pool you hold, the maximum any single instance can draw, and how the allocation is measured and reported. Because the model is defined by these specifics rather than a single universal clause, the only reliable way to know what you have is to read the current entitlement, and the detail matters when traffic patterns change or appliances are added.
How it is used for or against you
For the buyer, pooled capacity is efficiency. It avoids stranding licenses on appliances that do not need them and lets a smaller total entitlement cover a larger, shifting workload. Against the buyer, the risk is sizing the pool to peak demand rather than to real measured usage, which leaves you paying for headroom you rarely touch. Under Cloud Software Group, with NetScaler pricing under the same upward pressure as the rest of the portfolio, the discipline is to measure actual capacity consumption across the estate before committing to a pool size, and to confirm at renewal how unused capacity is treated rather than assuming the pool will shrink to fit.
Related terms and guidance
Pooled capacity sits alongside hybrid rights and the broader Universal Hybrid Multi Cloud license as one of the flexibility constructs in current Citrix and NetScaler packaging. For how the wider portfolio is licensed, see our Citrix licensing fundamentals pillar and our guidance on Citrix license types compared. Return to the full Citrix licensing glossary for more definitions.
Frequently asked questions
What is a pooled capacity license?
A pooled capacity license grants a shared allowance of capacity, such as bandwidth or instances, that can be drawn down and allocated flexibly across multiple appliances or environments rather than fixed to one. In NetScaler licensing it lets you distribute throughput from a common pool wherever it is needed.
Why do buyers use pooled capacity licensing?
For flexibility and efficiency. A shared pool lets you move capacity to where demand is, scale individual instances up or down, and avoid stranding licenses on appliances that do not need them. As of 2026 it suits dynamic and hybrid estates better than rigid per appliance licensing.
What is the risk with pooled capacity licensing?
The risk is sizing the pool to peak rather than to real usage, which leaves you paying for headroom you never draw. Buyers should measure actual capacity consumption across the estate before committing to a pool size, and confirm how unused capacity is treated at renewal.
How does pooled capacity relate to NetScaler licensing?
Pooled capacity is one of the models used to license NetScaler, allowing throughput and instances to be shared from a central allocation. It contrasts with fixed per appliance licensing, and the right choice depends on how variable and distributed your traffic is.