- About
- Core technologies
- Requirements
- Getting started
- Configuration Overview
- General
- License
- Identity
- Rate limiting
- Cors
- LoginProvider
- Logging
- Theme builder
- Email template builder
- Health checks
- What's New
- Migration guides
- Changelog
IdentitySuite License
Manage your license
License Management
IdentitySuite operates in Free mode by default with limitations of 3 concurrent applications and/or 100 concurrent users. To unlock additional features and increased capacity, you need to install a valid license. Visit our pricing page to explore available plans and features, or contact us for more information and to purchase a license.
Free Mode (Default):
- • Maximum 3 concurrent applications and/or 100 concurrent users
- • No license key required
- • Automatically active when no license is installed
Installing a New License:
Paste the license key received via email into the "License key" field in the interface.
Click the green checkmark button to verify the license. If valid, license details will be displayed.
Click "Add license" to install it. The license key is written straight to the configuration file (identitySuiteSettings.[Environment].json) — the entered license will be active from the next reboot.
Offline Activation (Air-Gapped Environments):
If the machine running IdentitySuite has no route to the license server — an air-gapped network, a restrictive firewall, a fully isolated deployment — the normal verification step above automatically falls back to an offline flow instead of just reporting failure.
Paste the license key and click the checkmark button, exactly as in a normal activation.
When the license server can't be reached, IdentitySuite shows "License server unreachable" and automatically prepares an activation request in a read-only text box. This request contains only the license key and a fingerprint of the current environment — no personal or sensitive data.
Copy the request and send it to IdentitySuite support via the contact page, asking for an offline activation response.
Once support replies, paste the response (the raw token, or the full text they send) into the "Offline Activation" box that appeared below the license key field, and click "Import license file". IdentitySuite validates it locally and shows the resulting license type and expiry date.
Click "Add license" to finalize activation — the result is identical to the online flow, including the reboot required to make the license effective.
Both steps of this round trip happen without any network access on the target machine — the request is built and the response is validated entirely offline. All that needs to move between the two machines is two small blocks of text, so email, a USB drive, or any other offline channel works.
License Renewal:
Environment Binding:
The first time a license activates, IdentitySuite binds it to a fingerprint of the environment it's running on — a hardware identifier on physical machines and VMs, or a locally persisted identifier when hardware identifiers aren't meaningful, such as inside a Docker container. This is the fingerprint carried in the offline activation request above, and it's also what a normal online check compares against on every subsequent verification.
Docker and other containers: the persisted identifier lives under the application's own data directories. If those aren't preserved across container recreation, the environment appears to change on every restart and the license has to reactivate each time. See the Docker Configuration for the volumes that need to persist.
Migrating to genuinely different hardware (e.g. replacing a server) legitimately changes this fingerprint. Contact support if you need a license reactivated on new hardware.