Licensing Guide
Understand Community mode, the full-feature demo, and hardware-bound commercial license files.
License modes
Kalytera evaluates a signed license file locally. The implemented modes are:
| Mode | Device limit | Capabilities |
|---|---|---|
| Community | 4 devices | Core VMS operation without a commercial license file. |
| 30-day demo | Shown on the Licensing page | A time-limited, full-feature evaluation when the demo is available. |
| Commercial | Defined by the signed file | The purchased device allocation and feature flags encoded in the license. |
Install a commercial license
- Open Admin → Licensing.
- Copy or export the displayed hardware fingerprint.
- Provide the fingerprint when the license is issued.
- Receive the signed
.licor.jsonlicense file. - Select Import License File and choose that file.
Validation is local and does not require an online activation service. Keep the original license file in your deployment records so it can be restored on the licensed host.
Commercial feature flags
A commercial file can enable the implemented optional capabilities individually:
- Alarms, Analytics, Maps, and Appearance Search
- I/O Control, Generic Devices, Virtual I/O, and Edge Analytics
- Access Control, Customizable Dashboard, and Assistant
The signed file is the authority for the maximum device count, expiration, and enabled flags. Do not infer capabilities from marketing tier names.
Renewals, upgrades, and server changes
Renewals and upgrades are delivered as a replacement signed file. Import the new file from the Licensing page. A license is bound to the hardware fingerprint used when it was issued; moving to a host with a different fingerprint requires a newly issued file for that host.
Before replacing hardware, record the current license details and obtain the destination server's fingerprint. Copying the existing license file to different hardware does not rebind it.