AppGate ZTNA is licensed by users, portal users, Sites, and Connector resource groups. The first Controller in a Collective includes a default license that allows two Sites and six users.
NOTE
Service users have been deprecated as of v7.0.
NOTE
Optional feature licenses appear only when they are enabled.
Users and Portal users
Each user type draws from a separate license pool on a first-come, first-served basis and is counted on a unique-user basis. A user who signs in twice using the same IdP uses only one license.
The system licenses a local user when a unique Kubernetes (k8s) service client is injected.
The system automatically unassigns users and returns their licenses to the pool 30 days after the user or device was last seen. For portal users, this period is two days.
The system checks license counts every hour to determine whether used licenses exceed the effective license total. This can occur when a license expires, is deleted, or a CA renewal is completed with a smaller license. When the used count exceeds the effective total, the system unassigns all licenses of that type, returns them to the pool, and reassigns them on a first-come, first-served basis.
The always-on client consists of two parts—full and headless—and consumes two user licenses. The headless part typically uses a shared service account across multiple machines, so the actual number of licenses consumed is closer to n+1 (where n equals the number of users).
Sites and Connector resource groups
The system grants a Site a license when it is created. For more information, see Sites.
A Connector is configured using resource groups, which are client instances with up to 60 resource groups per Connector. The system grants a resource group a license when it is created. For more information, see Express Connector and Advanced Connector. When you configure a Connector for high availability (HA) by sharing a virtual IP address (VIP) with another Connector, the system does not count the cloned resource groups in the second instance toward the license total.
The system automatically unassigns Site and Connector resource group licenses and returns them to the pool when you delete the licensed entity.
Feature Licenses
The following three feature licenses enable additional functionality in AppGate ZTNA:
Brokered Access. Includes Brokered RDP and Brokered SSH entitlement types.
Collective Replication. Distributes a shared configuration baseline from a source Collective to one or more target Collectives. See Collective Replication for more information.
Observability. Provides insight into user activity and software performance through telemetry data to help you understand and diagnose issues. See Observability for more information.
Operational Technology. Enables use of the Claroty CTD resolver and protocol templates. See AppGate for OT for more information.
Optimizer. A tool that discovers, narrows, and continuously re-optimizes entitlements. Includes Application Discovery. See Optimizer for more information.
Risk Sentinel. Enables the risk engine connectors available through the AppGate ZTNA ZTP cloud service.
Session Governance. Enables session recording, the Active Brokered Sessions page, and the Recorded Brokered Sessions page.
License usage
License usage appears in the following locations:
The License widget on the Dashboard
The resource group fields when adding resource groups to a Connector
.png?sv=2026-02-06&spr=https&st=2026-11-21T21%3A29%3A23Z&se=2026-11-21T21%3A43%3A23Z&sr=b&sp=r&sig=g4m1Rm6R1RbtqmIqF2JIJNs3tBmj6pfZYlNy%2BecWezw%3D)
A health check warning when usage exceeds 95 percent and fewer than 50 licenses remain
The file generated by the
cz-system-infocommandThe SNMP/Prometheus statistics provided by the Controller
License Expiry
A warning banner appears on the dashboard 30 days before a license expires. The banner continues to display the time remaining until expiry. Request a new license before the current one expires.
When a license expires:
The system revokes and reallocates user and portal user licenses on a first-come, first-served basis. When all licenses of a given type are allocated, additional users cannot connect.
Sites and Connector resource groups are not removed or disabled. You can only create, edit, or save Sites and Connector resource groups when sufficient licenses of the respective type are available.
To ask about license renewal, contact Support.
The Licenses Page
Use the Licenses (Settings > Licenses) page to view all licenses applied to the system. The system sums these licenses to produce the effective license active on the system.
The Licenses page includes the following:
Effective License Summary. Displays the total number of active licenses on the system.

New systems include one default license that allows six users and two Sites. To test portal user or Connector resource group licenses, contact support.
Actions button. Select one of the following options:
Download License Utilization. Downloads a JSON file containing the number of users, Sites, and other Collective information.
Download License Utilization by IdP. Available to administrator users with the View User License privilege. Downloads a CSV file of the number of licenses used per identity provider.
Adding another license. To add a license, select Upload License. You cannot remove the last license on a system.
Current Licenses. Displays the details of each individual license on the system, including which feature licenses are enabled.
License for next CA. Displays the details of the first license that the system uses when the next CA is activated. You can obtain this license using the unique request code used for license generation. This license must be present before the next root CA is activated, because it applies to that CA.
NOTE
This license applies after the next CA is activated. Add additional licenses after activation.
Obtaining a production license
To request a production license, send your unique request code to appgatesdp.support@appgate.com. The request code is tied to the root CA of your system and works only on that system. Select the link on the Licenses page to generate an email with the subject line:
Request for Production license xxxxxxxxxx_v2
Include the number of client users, portal users, Sites, and Connector resource groups purchased, as detailed in your proof of entitlement (POE).
To replace a license for the next CA, follow the same process with the subject line:
Request Replacement Production license from xxxxxxxxxx_v2 to zzzzzzzzzz_v2