--- title: "Licensing" slug: "v20-licensing" updated: 2026-11-21T01:21:56Z published: 2026-11-21T01:21:56Z canonical: "docs.telosalliance.com/v20-licensing" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.telosalliance.com/llms.txt > Use this file to discover all available pages before exploring further. # Licensing Each Pathfinder Core PRO system includes a base license that provides a pool of 1000 license points to be allocated between Axia Audio Sources and Logic Flow endpoints. > [!NOTE] > Important Note: The licensing model changed with version 2.0 of Pathfinder Core PRO. Key9 license keys, which are activated against the Telos license server, replace the license keys used in earlier versions. An existing license must be converted to Key9 before a system can be updated to 2.0; see [Licensing Requirements for Updates](/v1/docs/v20-licensing#licensing-requirements-for-updates). Beginning with version 2.1, software updates also need a current TelosCare subscription. This article covers: - [Virtual License Types](/v1/docs/v20-licensing#virtual-license-types) and [Additional Licenses](/v1/docs/v20-licensing#additional-licenses): what each license provides - [Key9 Licensing](/v1/docs/v20-licensing#key9-licensing): the Licenses page, and adding and removing license keys - [License Health](/v1/docs/v20-licensing#license-health): the warnings the system gives about its licensing - [TelosCare Subscription](/v1/docs/v20-licensing#teloscare-subscription): the support subscription and what it controls - [Licensing Requirements for Updates](/v1/docs/v20-licensing#licensing-requirements-for-updates): what an update package checks before it installs - [Licensing in a Cluster](/v1/docs/v20-licensing#licensing-in-a-cluster): how cluster nodes share a license ## Virtual License Types If you purchased a hardware-based Pathfinder Core PRO, the base license is pre‑installed. If you purchased a virtual machine license, there are four possible license types: | | License Type | Points | Notes | | --- | --- | --- | --- | | 1 | Pathfinder Core PRO VM | 1000 | The same functionality as the hardware license | | 2 | Pathfinder Core PRO VML | 300 | A lower license count and a correspondingly lower cost of entry | | 3 | Pathfinder Core PRO VM Backup | 0 | Intended for adding a VM-based cluster node to a Pathfinder Core PRO cluster. This license works only when clustered with another hardware or VM instance of Pathfinder Core PRO. If the primary licensed Pathfinder Core PRO fails, the backup continues to function as if it were the primary for up to 90 days while you repair the primary instance. If this 90-day limitation is not acceptable, full licenses can also be clustered, without that restriction. | | 4 | Pathfinder Core PRO VM HD | Set by the license | A base license that carries its own point allowance. That allowance is the whole point pool. Points from add-on licenses are not added to it. | ## Additional Licenses You can purchase additional licenses to add functionality through your Telos distributor. Each one adds either 500 (the *Pathfinder Core PRO Add-On 500*) or 100 (the *Pathfinder Core PRO Add-On 100*) license points. Add-on licenses are shared between the Pathfinder Core PRO units in a clustered system. This means that if you need a redundant Pathfinder Core PRO system that supports 1500 license points, you will need to purchase *two* Pathfinder Core PRO systems (each of which comes with a base license or backup license) *and* a single add-on license to add the additional 500 sources. The add-on license allows both systems in the cluster to mirror and synchronize the full 1500 license point functionality. > [!NOTE] > Important Note: Virtual sources and GPIO sources do not count against the license. Only Axia Audio Sources with enabled streams and Logic Flow endpoints are counted in the licensing. Logic Flows that the system creates dynamically during HTML5 panel binding or hardware mapping also do not count against your licensing. If you have questions about the licensing model, contact Telos support or your Axia distributor. ## Key9 Licensing Pathfinder Core PRO 2.0 is licensed with **Key9** license keys, which are checked against a Telos license server. Click **System > Licenses** in the navigation bar. ![](https://cdn.document360.io/57e3cd80-d493-453c-9672-ad1b043dadc3/Images/Documentation/v20-system-licenses.png?sv=2026-02-06&spr=https&st=2026-11-21T13%3A26%3A30Z&se=2026-11-21T14%3A26%3A30Z&sr=b&sp=r&sig=7jhErhjtBl8Ug8lLiqUcpj03UcI0rBGX1KGm9zeXplw%3D) The page shows: | Item | Description | | --- | --- | | License Server Status | Whether the system can reach the license server. When there is a problem, a banner explains it, for example *Cannot reach the license server.* | | Total Points, Used, Available | The license point pool and how much of it is in use. | | Base License, Scheduler, External Auth | Whether the base license is active and whether the Scheduler and External Authentication (LDAP) features are licensed. | | TelosCare, TelosCare Expiration | The TelosCare subscription on this system and when it expires. The TelosCare subscription determines which software updates may be installed; see [TelosCare Subscription](/v1/docs/v20-licensing#teloscare-subscription). | | Last Server Response | When the license server last answered. | | Node Name | The name this system is known by on the license server. | | Backup License | On a cluster backup node, how long it has been running on its primary's license. | Below these is the list of license keys on the system, with what each one provides. When an HD license is installed, its points are the whole point pool. A banner names any other keys whose points have no effect. To add a license: - Select **[ Add New License Key ]** in the list. - Type or paste the key into **License Key** and click **Add License**. The system contacts the license server to activate it. To remove a key, select it and click **Delete License**. Click **Refresh Licenses** to ask the license server for the current state of all keys right away. > [!NOTE] > Important Note: License changes may require a reboot to take effect. Click the **Configuration** link under System to find the reboot button. ### Offline Activation A hardware Pathfinder Core PRO that cannot reach the license server can be activated offline. Click **Offline Activation**, type the license key, and click **Add License** to generate a request code. Then follow the steps in the dialog: ![](https://cdn.document360.io/57e3cd80-d493-453c-9672-ad1b043dadc3/Images/Documentation/v20-system-licenses-offline.png?sv=2026-02-06&spr=https&st=2026-11-21T13%3A26%3A30Z&se=2026-11-21T14%3A26%3A30Z&sr=b&sp=r&sig=TyoV2MedMn%2Fa6dAJtHAB%2B0m9ZVeNNbc25Xcox3HMRV4%3D) 1. Click **Copy Request Code**. 2. On a computer with internet access, go to https://secure.telos-systems.com/ (no login is required), paste the request code into the form and submit it. 3. Copy the activation code the server returns and paste it into **Activation Code from Server**. 4. Click **Complete Activation**. Click **Start Over** to begin again with a new request code. Offline activation is not offered on virtual machine or container installations. > [!WARNING] > Important Note: Offline activation is ONLY available for Pathfinder Core PRO hardware units. ### Custom License Servers Click **Advanced Settings** to choose which license servers the system uses. ![](https://cdn.document360.io/57e3cd80-d493-453c-9672-ad1b043dadc3/Images/Documentation/v20-system-licenses-advanced.png?sv=2026-02-06&spr=https&st=2026-11-21T13%3A26%3A30Z&se=2026-11-21T14%3A26%3A30Z&sr=b&sp=r&sig=NPuHnijiAF4m04sTzgX57qHVB7YmoX9iepPPTr%2FGTQM%3D) Servers are tried in order from top to bottom. An empty list uses the default Telos servers. Type a server's address and click **Add**, select a server and use the arrow buttons to change its place in the list, or click **Delete** to remove it. Each server is colored by its state: green when accessible, red when not available, and white when not yet known. ## License Health Pathfinder Core PRO watches its licensing and reports a health state of OK, WARNING or ERROR: - **WARNING** when the license server cannot be reached (after two failed checks in a row) while the license is still valid, or when a licensed feature expires within 30 days - **ERROR** when a licensed feature expires within 14 days or has expired, or when the license is no longer valid When the state changes, an email is sent to the **Critical Event Email Address** set in *Email Settings* (see the [System](/v1/docs/v110-system-1) article), with a reminder every 24 hours while the problem lasts and a final message when it clears. In a cluster, only the primary node sends these emails. The health state is also available to Logic Flows and SAPv2 through the `LicenseHealth` and `LicenseHealthDetail` properties of `System#0.Validation#0`. ## TelosCare Subscription TelosCare is the support subscription for your Pathfinder Core PRO. The **TelosCare** and **TelosCare Expiration** items on the Licenses page show the subscription on this system and when it expires. Beginning with version 2.1, the TelosCare subscription determines which software updates may be installed; see [Licensing Requirements for Updates](/v1/docs/v20-licensing#licensing-requirements-for-updates). A cluster backup node without its own TelosCare subscription uses its primary's. For more information about TelosCare, see [https://success.telosalliance.com/teloscare](https://success.telosalliance.com/teloscare). ## Licensing Requirements for Updates Before an update package is installed, the system checks that it is licensed to run it. The checks depend on the version of the package being installed, not the version currently running: - **Key9 license**: packages of version 2.0.0 and later need a Key9 license on the system. Without one, the update stops at *Validating Key9 License...* with **Update Failed: License Required** and a link to the Licenses page. - **TelosCare Subscription**: beginning with version 2.1, a package can only be installed while the system holds a current TelosCare subscription, or one that covers the package's release. If the TelosCare subscription does not allow the update, the update fails, and the system log gives the reason. Version 2.0.x packages do not require an active TelosCare subscription. A cluster backup node without its own TelosCare subscription uses its primary's TelosCare subscription for this check. To move a unit from version 1.x to 2.0, first update it to 1.10.12 or later, add and validate its Key9 license there, and then install the 2.0 update. Updates are installed from the **Upload Update** page; see *Upload Update* in the [System](/v1/docs/v110-system-1#upload-update) article. ## Licensing in a Cluster A cluster shares its license. A backup node that has no license of its own (for example a *Pathfinder Core PRO VM Backup* license) inherits the license points, the Scheduler and External Authentication features, and the TelosCare subscription of the primary. If a backup node restarts while the primary is offline, it keeps working on the inherited license for up to 90 days, so the primary can be repaired. The backup's license health turns to a warning at 60 days and an error at 80 days (see [License Health](/v1/docs/v20-licensing#license-health)). Leaving the cluster, or being ejected, ends the inheritance. Add-on licenses are also shared between the units in a cluster; see [Additional Licenses](/v1/docs/v20-licensing#additional-licenses). For how to build a cluster, see the [Clusters](/v1/docs/v110-clusters-1) article.