User personas and concurrency
Separate named staff, shared workstations, shift users, contractors and occasional access. Record peak concurrent use as an architecture fact even where the commercial unit is a user or device.
Citrix licensing
Citrix licensing
Scope secure application and desktop delivery around user personas, deployment location, concurrency, platform services and dependent Microsoft licensing.
Request a licensing quoteRequirementMetricTermLifecycleCitrix
Licensing overview
Map the requirement before comparing offers.
Citrix requirements usually sit at the intersection of application delivery, virtual desktops, remote access, endpoint control and network delivery. Licensing therefore needs a user-persona and architecture view: who connects, how often they connect, which applications or desktops they receive, where workloads run and what supporting services are needed.
Current Citrix terminology includes the Citrix Platform and Platform Flex, Citrix DaaS, NetScaler, XenServer, Endpoint Management and SecurAccess ZTNA. Available subscriptions and metrics vary, and Citrix materials may distinguish user, device, concurrent, capacity or Flex-based constructs. Older Citrix Virtual Apps and Desktops names may also remain in deployed estates or product documentation.
Atmic can help assemble the technical and commercial facts needed for a current quote. The exercise must also identify non-Citrix dependencies such as Microsoft server, desktop, Remote Desktop Services and cloud infrastructure rights. A Citrix subscription should never be presented as automatically licensing those separate components.
Relevant software areas
What teams commonly evaluate.
- Citrix DaaS and app-and-desktop delivery for cloud, hybrid or private environments
- Citrix Platform and Platform Flex combinations for broader platform requirements
- NetScaler application delivery and secure access capacity
- XenServer virtualisation where it is part of the chosen design and entitlement
- Endpoint Management and SecurAccess ZTNA capabilities for applicable user journeys
Typical business uses
Where the requirement starts.
- Delivering line-of-business applications to distributed employees without installing every application locally
- Providing controlled desktops for contractors, branch users or specialist workloads
- Modernising an existing Citrix Virtual Apps and Desktops environment
- Designing hybrid delivery while retaining selected workloads in a private data centre
- Reviewing NetScaler capacity and platform subscriptions before infrastructure change or renewal
Commercial and technical considerations
Details that can change the right quotation.
Control plane and workload location
Clarify whether the design uses cloud services, on-premises components or a hybrid arrangement, and where applications, profiles, images, identity services and gateways will operate.
Edition and component scope
Compare the exact current subscription matrix. Product names may group multiple components, but only the quoted edition and its current terms establish usable features and quantities.
Microsoft and cloud dependencies
Windows, Microsoft 365 Apps, Remote Desktop Services, SQL Server, Windows 365 and public-cloud consumption can carry separate requirements. Include them in the solution bill of materials.
Experience and operations
Validate network paths, profile design, peripheral needs, multimedia, application compatibility, image lifecycle and support ownership. A correct subscription does not compensate for an unsuitable desktop architecture.
Discovery checklist
Information to gather before requesting a quote.
- Which applications or desktops will be delivered to each user persona?
- How many named, device-based and peak concurrent users are expected?
- Where will control-plane services, workloads, profiles and gateways run?
- Which Citrix products, editions, versions and subscriptions already exist?
- What NetScaler capacity, secure-access or endpoint-management functions are required?
- Which Microsoft, cloud, database and network dependencies need separate licensing or consumption estimates?
- What availability, recovery, support and upgrade expectations apply?
Renewal and lifecycle planning
Treat renewal as a decision point.
- Keep user and device assignments aligned with identity and HR processes.
- Review actual concurrency, platform consumption and gateway capacity against forecast assumptions.
- Track subscription, support, cloud consumption and dependent Microsoft renewal dates together.
- Revalidate application compatibility and architecture before major Citrix or operating-system upgrades.
- Use the current Citrix feature matrix and product-specific terms for each renewal or expansion.
Product packaging, availability, metrics and terms can change. Final recommendations and quotations should be checked against the vendor’s current official product terms for the selected region and purchasing channel. No partner, reseller or authorisation status is implied on this website.
Licensing FAQ
Questions worth resolving early.
What is the difference between Citrix DaaS and an on-premises Citrix deployment?
The control plane, operational responsibilities and available services can differ. Citrix DaaS uses Citrix-hosted services for applicable control-plane functions, while workloads may still run in cloud or customer-managed locations. The selected subscription and design define the actual arrangement.
Is Citrix licensed per user or per concurrent connection?
Metrics vary by current offer and edition. User, device, concurrent, capacity and Flex-based constructs may be relevant. The quote must state the unit type and quantities; concurrency data is still useful for sizing even when it is not the licensing unit.
Does Citrix include Microsoft licences?
Do not assume it does. Windows, Remote Desktop Services, Microsoft 365 Apps, SQL Server and other Microsoft products may have separate requirements. Any included or dependent right must be explicit in current documentation.
Can existing Citrix Virtual Apps and Desktops licences be moved to a current platform offer?
A transition may be possible under a specific commercial path, but rights and consequences depend on the existing agreement and proposed subscription. Obtain a written quotation and terms before changing the estate.
What information is needed for a Citrix quote?
Provide personas, user and concurrency counts, application list, desktop types, locations, control-plane preference, gateway capacity, existing Citrix estate, Microsoft dependencies, term and renewal date.
Citrix
Prepare a better licensing request.
Share the users, devices, workloads, deployment model, current entitlement and renewal date.