An installation license

Each installation has its own identifier, created at first startup. The license key is bound to that identifier and includes a validity period. The server verifies the digital signature locally; activation does not require contacting an external licensing service.

Adding a key

  1. Open “Settings → Licensing”.
  2. Copy the installation identifier to obtain a key from the supplier.
  3. The administrator pastes the received key into “License key” and clicks “Add key”.
  4. Check the status, customer name and start/end dates.

Several keys can be stored. Consecutive periods without a gap extend operation. The system warns 30 days before expiry. Validity dates use UTC and include both the first and last day.

If the license is invalid

Login and settings remain accessible for recovery, while operational actions are blocked with code LICENSE_REQUIRED. Workspace buttons and integration report an invalid license. The executor checks authorization before writes; expiry during a run can stop it before the next batch.

Migration and backup

Preserve the data directory together with the installation identifier and license keys. Creating an empty directory on a new server may generate a different identifier and require a new key. Installation-health checks should cover the database, files, license validity, executor operation and required connection availability.