Connect your application.
A consistent licensing flow for .NET, Node.js, and disconnected environments.
1. Register your application
An administrator registers the product and its offerings. Each offering combines a duration, device allowance, connectivity mode, and feature entitlements.
2. Activate a device
Use a stable device identifier and the product slug to generate a versioned fingerprint. Send the license key only over HTTPS in the Authorization header. Activation and validation never need a privileged server token.
POST /api/licensing/v1/installations/activate
Authorization: License YOUR-LICENSE-KEY
Content-Type: application/json
{ "product": "your-app", "fingerprint": "v1:…64 hexadecimal characters…" }3. Enforce your connectivity mode
Strict online installations check at startup and every five minutes. Intermittent installations refresh hourly and use a verified certificate for up to 72 hours. Activate-once and air-gapped installations verify signed machine files locally on every startup and periodically while running.
4. Verify offline files
Embed your trusted account ID, product ID, and RSA public key in the app. Verify signatures, device binding, entitlements, and both expiry dates. Renew a disconnected subscription by importing a new file.
An isolated device cannot receive suspension or revocation updates. Ask an administrator to issue or replace permanent offline files.
Download the OpenAPI contract · Client packages and complete examples are provided with the platform source.