Licensing

Polygent uses an offline signed license installed on the application server; routine validation does not contact a licensing service.

The license can define expiry, user capacity, worker-host capacity, enabled features, and—depending on the issued license—machine or request-domain restrictions. Treat the license text and machine-information file as sensitive operational records.

Access during a license problem

When no valid license is active, normal application features are blocked and users see the activation, invalid-license, or expired-license screen.

Administrators can download machine information and install a replacement license. Non-administrators must contact an administrator. Authentication and the recovery screen remain available so an operator can restore service.

Initial activation

Activation binds an operator-issued license to the installation's approved identity or domain.

1. Sign in as an administrator.
2. On the activation screen, select Download machine-info.json.
3. Send the file to your authorized Polygent license operator through an approved secure channel.
4. Receive the signed .lic value.
5. Paste it into Install License and submit it.
6. Confirm the status is Active, the customer and tier are correct, and capacity and features match the order.

Machine information is time-sensitive. Download a fresh file when the operator requests one instead of reusing an old attachment. License installation takes effect without restarting the application.

Monitor license status

The License tab is the operational source for current entitlement and capacity.

Field	Operational use
Status and expiration	Confirm activation and plan renewal before expiry.
Customer, license ID, issue date, and tier	Verify the installed entitlement.
User limit	Compare active licensed users with purchased capacity.
Session and deploy hosts	Compare connected workers with concurrent-host limits.
Features	Confirm required modules are licensed.
Allowed domain	Verify the hostname restriction when present.
Machine ID	Identify a machine-bound installation.

Administrators receive warnings as expiry approaches. Do not depend on alerts alone: include license expiry and host/user capacity in routine operational monitoring.

Renewal and replacement

Renew before the current license expires to avoid an application-wide interruption.

1. Contact the license operator with the license ID and required capacity or feature changes.
2. Provide fresh machine information if requested or if server identity changed.
3. Receive the replacement .lic value through a secure channel.
4. Install it under Settings → License, or from the blocked recovery screen after expiry.
5. Confirm status, expiry, capacity, features, domain, and worker connectivity.
6. Store the issued license and approval record according to your configuration-management policy.

Uploading a replacement is immediate and does not require a service restart. Keep a securely stored copy of the currently valid license for disaster recovery, subject to its machine and domain restrictions.

Capacity and feature enforcement

License limits are enforced independently from user permissions.

• User capacity limits active licensed users. Offboard or deactivate obsolete accounts before adding users at capacity.
• Session-host capacity limits concurrently connected session workers.
• Deploy-host capacity limits concurrently connected deployment workers.
• Feature entitlements control whether licensed modules are available.

When a worker-host limit is reached, additional workers cannot connect until capacity is freed or the license is replaced. Do not repeatedly restart workers to bypass the limit; identify duplicate or obsolete hosts and stop them cleanly.

Domain and machine changes

Infrastructure changes can invalidate an otherwise unexpired license.

A machine-bound license can require reissue after an operating-system reinstall, machine identity restoration, or migration to another server. Download fresh machine information from the new installation and request a replacement before cutover where possible.

A domain-restricted license validates the request hostname. Exact domains must match the deployed hostname. A pattern such as *.acme.internal matches one subdomain level, such as api.acme.internal, but not the bare domain or a deeper name such as api.eu.acme.internal. Ensure reverse proxies preserve the intended public host and request a license matching every production hostname required by your deployment.

Backup and disaster recovery

Licensing must be included in application recovery planning.

• Back up the Polygent database and configured storage with the rest of the installation.
• Keep the current .lic value, license ID, expiry, and operator contact in a restricted configuration vault.
• Document whether recovery to new hardware requires reissue.
• Test license status after database restore, hostname change, proxy change, or server migration.
• Maintain correct time synchronization; significant backward clock movement can invalidate the license until time is corrected.

Do not edit, decode, or attempt to reuse a license outside its issued scope.

Troubleshooting

Use the exact status shown on the License page and correlate it with recent infrastructure changes.

Symptom	Resolution
Not Installed	Download fresh machine information and complete initial activation.
Expired	Install a renewed license. Normal application access remains blocked until activation succeeds.
Invalid	Confirm the complete .lic value was pasted without alteration; otherwise request reissue.
Machine identity changed	Request a replacement using newly downloaded machine information from the current server.
License domain mismatch	Access the configured hostname, correct reverse-proxy host forwarding, or request a license for the actual hostname.
Worker reports host-capacity limit	Stop an obsolete connected worker or obtain higher licensed capacity.
Expected feature is absent	Check the Features list and user permissions; request a replacement license if the entitlement is missing.
User cannot be added or activated	Remove obsolete users or obtain a higher user limit.
License becomes invalid after clock change	Restore accurate time and reliable time synchronization; restart only if status does not refresh after correction.
Upload fails	Confirm administrator access, use the full signed value, check server logs and database availability, then retry.
Recovery server rejects the old license	Restore the original machine identity where supported or request reissue for the recovery host.

Escalate with the customer name, license ID, displayed status, server time, public hostname, and a newly downloaded machine-information file. Do not send repository credentials, model keys, database passwords, or host API keys with a licensing request.