LicenPro
DocumentationPerpetual

Perpetual license

A perpetual license grants long-term use without a subscription term. Choose online (live validation, activations, and sessions in the dashboard) or offline (signed license.bin for air-gapped installs). Online perpetual is ideal when you need real-time revocation and usage visibility.

Long-term entitlement

No renewal cycle; licenses issued from the dashboard never expire.

Online or offline

Step 1 of the create wizard — Activation mode.

Multi-device

Online perpetual can show many activations (∞ limit when unset).

Perpetual license — for product owners

Grant long-term use without a subscription renewal cycle. Choose online validation for live revocation and dashboard visibility, or offline for air-gapped installs with RSA-signed license.bin files.

  • Issue via Licenses → Generate License → Perpetual.
  • New products get RSA signing keys automatically; an older product without keys must generate them in Settings before it can issue licenses.
  • Monitor Activations and Sessions for online perpetual.
  • Block or deactivate individual devices without revoking the whole key.
  • Revoke the entire license from the license Danger Zone. Revocation is final; to pause a license temporarily, set its status to Invalid in Edit.

Perpetual licenses are not assigned to a customer: no Issued to is stored, so they never appear in a customer's My Licenses. Hand the license key and license.bin to the customer yourself.

Perpetual license — for end users

You receive a license key and license.bin (plus the product public key from your vendor). Perpetual licenses do not expire.

  • Online perpetual — app validates against the server; supports activations and live sessions.
  • Offline perpetual — app validates locally after signature check; no daily internet required.

Common errors: signature mismatch (wrong public key), credentials mismatch (wrong license key), device blocked, revoked (online copies stop at the next check).

Create a perpetual license (dashboard)

Licenses → Generate License. Four-step wizard: Activation → License Type → Basic Info → Details.

Step 1 — Activation mode

  • Online — SDK calls the API on validation; activations and sessions are tracked. Revoke a device from the dashboard and the next check fails immediately.
  • Offline — distribute license.bin; daily use does not require API connectivity. Perpetual is available in both modes; Opened products always use Offline, and Perpetual is the type they offer.

Step 2 — License type

Select Perpetual — multi-user, indefinite use; works online or offline depending on step 1.

License Type — select Perpetual (or compare with Node-Locked).

Step 3 — Basic info

  • Product and Software release (required)
  • Issued to — shown as Perpetual License (auto-assigned). Perpetual licenses are not tied to a user, and the SDK does not check a user name.
  • If the product has no RSA signing keys yet, the wizard warns you and links to the product settings; the license cannot be created until keys exist.
  • License name (required)
Basic Info — product and release context.

Step 4 — Details

Perpetual licenses do not show Device binding mode (that is node-locked only). There is no expiry field for Perpetual. Configure optional entitlement sets and notes, then generate.

Licenses list — perpetual vs node-locked

ColumnPerpetual (example)Node-Locked (example)
TypePerpetual badgeNodeLocked badge
ModeOnline / OfflineOnline / Offline
ExpirationOften ∞ (no expiry)Often Never
Activationse.g. 2 / ∞ — many devices allowede.g. 1 / 1 — one bound device
Licenses list — activation counts differ by type.

Machine workflow (online perpetual)

  1. Distribute license key + license.bin + embedded public key.
  2. App calls LicenseClient.ValidateAsync or Validate License in the WinForms sample.
  3. The server checks status, expiration and the device block list; the SDK verifies the RSA signature and the license key locally.
  4. On success, SDK creates an activation record (first time per device) and a live session.
  5. Heartbeats keep the session online while the app runs; disconnect on exit.
  6. If activation or the session is refused (for example the maximum number of activations is reached), validation fails and the SDK disconnects the session and disables the license's features.
Revocation

Block or deactivate a device from the license Activations tab. The next online validation or heartbeat on that machine fails with a device-blocked or invalid message — other activations stay valid.

Revoking the whole license is final. A running app learns it on its next heartbeat: the SDK disables the license's features and raises SessionDisconnected; the next validation reports Revoked.

License details — Overview tab

  • License type — Perpetual
  • Validation mode — Online or Offline
  • Expiration — No expiration (∞) unless you set a date
  • Usage statistics — active devices vs max (unlimited when max not set)
  • Online activity — shortcut counts for Activations and Active Sessions

Perpetual online licenses do not show Device Binding fields (no hardware binding mode).

Activations tab

Each row is a device that validated or activated this license key. Online perpetual may have many rows; there is no single-machine lock unless you set max activations on create.

ColumnMeaning
DeviceHostname and hardware fingerprint
UserOS / SDK user at activation
IPClient IP when activated
ActivatedFirst-seen time for this device
StatusActive — device may validate; Blocked — denied on next check
Activations tab — same UI for all online license types.

Active Sessions tab (online only)

Lists apps currently connected with a live heartbeat. Multiple sessions can exist when several users run the app at once (subject to max concurrent seats if configured).

ColumnMeaning
UserSession identity + app version
DeviceMachine name and OS
IP AddressCurrent connection IP (masked in UI)
ConnectedSession start time
HeartbeatLast SDK ping — stale heartbeats mark session offline
Active Sessions — live connections for this license.

When the server is unreachable (online perpetual)

  • At startup — validation fails with "Unable to reach the licensing server". There is no fallback to the offline cache yet.
  • While running — the SDK keeps retrying heartbeats. After 3 unanswered heartbeats it raises SessionDisconnected once with reason Unreachable; the license stays loaded, and the next successful heartbeat clears the condition.

Offline perpetual workflow

  1. Create with Offline activation mode.
  2. Customer imports license.bin; SDK verifies RSA signature locally.
  3. On the first run on each machine, ValidateAsync checks the license online once (status + validate), then validates locally on every later start. Use ValidateOfflineAsync on machines that never reach the server.
  4. A revoke after that first check does not reach copies already in use. Choose Online mode when you need revocation.
  5. Dashboard may show fewer live sessions; Device Binding tab is not used.

Global monitoring

Sidebar Activations and Sessions aggregate all licenses. Filter by device, user, or IP for support. See Sessions & Activations.

Global Sessions — all products; license name links to detail.

Compare with node-locked

  • Perpetual online — many devices possible; focus on Activations + Sessions.
  • Node-locked — one hardware binding; focus on Device Binding tab + binding mode at create.
  • See Node-locked license for Auto-bind and approval flows.

See also