Skip to content

Licensing

Consystence licences control which features are available and how many sites, devices, and users an organisation can use.

Licence types

Licence Target Includes
Cloud Tenant Small to mid-size operators Single org, up to 5 sites, cloud dashboard, standard support
Cloud Enterprise Large operators and multi-site fleets Unlimited sites, fleet analytics, SSO/SAML, priority support
Site Licence On-premises site servers Per-site activation, offline capable, local historian, edge device management
Edge OEM Licence Equipment manufacturers embedding Consystence Per-device activation, white-label option, OEM marketplace publishing
Development Licence Integrators and internal dev teams All features enabled, limited to non-production use, 90-day rolling term

Cloud Tenant

For organisations that need real-time dashboards and alarm management without on-premises infrastructure. Data flows from edge devices through a Consystence-managed site server in Azure.

Cloud Enterprise

Everything in Cloud Tenant plus fleet-wide analytics, cross-site reporting, SSO integration (SAML/OIDC), and a dedicated support channel. Suited for mining companies operating multiple sites.

Site Licence

Activates a single on-premises site server. Includes the Orleans silo, scene graph engine, alarm processor, and local historian. Required for each physical site that runs its own server. Supports offline operation — the site continues to function when the cloud connection is down.

Edge OEM Licence

For equipment manufacturers who embed Consystence on their hardware. Each edge device is individually activated. OEMs can publish device types to the marketplace and optionally white-label the operator interface.

Development Licence

Provides full platform access for non-production use. Designed for integrators building process templates and internal teams evaluating the platform. Automatically renews on a 90-day rolling basis.

Activation

Online activation (preferred)

The site server or edge device contacts the Consystence licence service on first start:

POST https://account.consystence.dev/api/licences/activate
Authorization: Bearer <org_admin_token>
Content-Type: application/json

{
  "licence_key": "CST-SITE-XXXX-XXXX-XXXX",
  "hardware_id": "auto-generated"
}

The licence service validates the key, binds it to the hardware fingerprint, and returns a signed licence token. The server stores this token locally and re-validates periodically.

Offline activation

For air-gapped or restricted-network sites:

  1. Generate a licence request file on the site server:

    consystence licence request --key CST-SITE-XXXX-XXXX-XXXX --output request.json

  2. Transfer request.json to a machine with internet access.

  3. Upload the request to the licence portal at account.consystence.dev and download the signed licence file.

  4. Transfer the licence file back and apply it:

    consystence licence apply --file licence.json

Grace period

If a previously activated site server loses contact with the licence service, it continues to operate for 30 days before entering a restricted mode. Offline-activated sites do not have this limitation — their licence file contains the full validity period.

Feature gating

Device type templates and process templates declare the licence features they require in their manifest:

# device-type.manifest.yaml
requires:
  features:
    - edge-ml
    - advanced-alarms
  min_licence: site

When a template is deployed to a site, the platform validates that the site's active licence includes all required features. If a feature is missing, deployment is blocked with a clear error message indicating which licence upgrade is needed.

This ensures that marketplace device types work correctly everywhere they are installed — there are no runtime surprises from missing capabilities.