License and Editions
UTMStack v12 comes in two editions: Community, which needs no licence file, and Enterprise. An Enterprise licence can also carry the multi-tenant option for managed service providers (MSSPs). This page explains what each edition includes, how to install a licence, and what the About page shows.
Editions and what they include
| Feature | Community | Enterprise | Enterprise with multi-tenant |
|---|---|---|---|
| Alerts, incidents, automated response (SOAR), dashboards, Log Explorer, rules, pipelines, integrations, SOC-AI | Yes | Yes | Yes |
| API keys: creating them and signing in with them | No | Yes | Yes |
| Single sign-on (SAML 2.0 and OpenID Connect) and creating or editing identity providers | No | Yes | Yes |
| White-label branding | No | Yes | Yes |
| Shipped compliance frameworks | CMMC 2.0 and GDPR only | All | All |
| Tenants, support access, tenant switcher, Apply to all tenants | No | No | Yes |
On Community, the compliance limit applies only to the frameworks and controls that ship with UTMStack. Frameworks and controls you create yourself are not limited.
When a licence expires or cannot be verified, UTMStack falls back to Community. Your data is kept, but the Enterprise features above stop working until a valid licence is installed.
What stops when a licence expires
The License page shows Expiring soon during the last 30 days. Renew before then. When the licence expires:
| Feature | What happens |
|---|---|
| Single sign-on (OpenID Connect and SAML) | Sign-in through these providers stops. Users who have no local password cannot sign in until a valid licence is installed. Keep at least one administrator with a local password. |
| API keys | Every request made with an API key is refused, including scripts, integrations and AI assistants that use a key. |
| Branding | Your branding is no longer shown, and the branding page can no longer be changed. Your settings are kept. |
| Compliance | Only the frameworks and controls available on Community can be used. |
| Tenants (multi-tenant licence) | The tenant pages and features need the multi-tenant licence. |
Log collection, alerts, incidents, rules and searches keep working on Community.
View your licence
Open Configure > Settings > License. Only the instance operator sees this page (see Settings Overview).
| Field | What it shows |
|---|---|
| Status | Community, Active, Expiring soon (30 days or less left) or Expired |
| Edition | Community or Enterprise |
| Ingest volume | The contracted log volume: Not metered, Unlimited or a number of GB per month. It is shown for information. |
| MSSP / multi-tenant | Whether the multi-tenant option is enabled |
| License type | Online or offline |
| Instance ID | The identifier of this server. A licence is issued for one instance ID. |
| Valid until | The expiry date, or No expiry |
| Time remaining | Days left before the licence expires |
The version shown in the top bar links to this page for administrators on Community (Manage license).
Install or replace a licence
You need to be the instance operator.
- 1
Get the licence file
Get your
LICENSEfile from UTMStack. The licence is issued for the Instance ID shown on the License page, so send that ID when you request it. - 2
Open the License page
Go to Configure > Settings > License.
- 3
Upload the file
Under Upload a license, click Choose file, select the file and click Install license.
- 4
Check the result
UTMStack checks the file's signature, that it was issued for this instance ID and that it has not expired. If the file is accepted, the page shows the new edition. If not, you see an error that starts with
invalid license:followed by the reason, for examplelicense expired at ...ordecrypt/verify failed: ....
The licence is stored on the server as /utmstack/updates/LICENSE. The server reads this file again every 5 minutes.
Servers with internet access also receive their licence automatically from the UTMStack licence server every 5 minutes, so you usually do not need to upload it yourself.
Uninstalling UTMStack deletes /utmstack/updates, which holds the licence file and the server's registration. Keep a copy of your licence file.
Troubleshooting the licence
| What you see | Cause | Fix |
|---|---|---|
| "Administrator privileges are required to upload a license." | You are not the instance operator | Sign in as an administrator of the default tenant. |
An error that starts with invalid license: decrypt/verify failed or invalid license: license expired at | The file was issued for another instance ID, was changed or damaged, or has expired | Compare the Instance ID on the License page with the one you gave UTMStack, and request a new file if they differ. |
The License page shows no Instance ID row, or the upload fails with invalid license: license verification not configured | The server has not registered with UTMStack yet. It receives its instance ID from the UTMStack update server, which needs internet access. A licence cannot be verified without it. | Check that the server can reach the internet (see Network Ports and Firewall), wait a few minutes and reload the page. For servers without internet access, contact UTMStack. |
On the server, the backend log shows why a licence file was rejected: docker service logs --since 1h utmstack_backend 2>&1 | grep -i license.
About this instance
Open Configure > Settings > About (instance operator only). The page shows:
The edition and the server's host name (Server).
The Instance ID.
A licence summary with a View license link.
System health for the backend API, with a Refresh button.
Data sources: how many data sources are configured.
Support links (documentation, GitHub repository, issue reporting, website) and Legal information.
System health checks only the backend API (Healthy or Down). It does not check the event store, the queue or the agent manager. To check every service on the server, see Health Checks and Troubleshooting.
You can also see the installed version and edition on the server with:
utmstack_installer --version