Skip to main content

Licensing

Licensing affects whether the system is considered active and ready for normal administrative use. It is one of the first things admins should verify during installation, recovery, and troubleshooting.

What Licensing Controls​

The current API and UI model supports:

  • retrieving the active license
  • activating a license by submitting a license string
  • reading license state such as status, expiration, activation time, and grace period

The current license status values are:

  • MISSING
  • VALID
  • CORRUPT
  • EXPIRED

When Licensing Matters Most​

Licensing is especially important during:

  • initial installation
  • post-restore validation
  • upgrades
  • admin troubleshooting
  • renewal planning

Activation Flow​

The current activation flow uses the activateLicense mutation with a license string.

Operationally, that means admins should be prepared to:

  1. obtain the correct license data
  2. open the licensing workflow
  3. submit the license
  4. confirm the resulting active status

Active License Information​

The current license model includes fields such as:

  • license data
  • status
  • expiresAt
  • createdAt
  • activatedAt
  • gracePeriod
  • active

Licensing Status Stub screenshot: licensing modal or admin licensing flow showing current status, expiration, activation state, and any grace-period details. Save final image at packages/docs/screenshots/overview-licensing-status.png.

These values are useful both for normal operations and for diagnosing license-related problems.

What To Check Operationally​

Admins should confirm:

  • whether an active license exists
  • whether the status is valid
  • whether expiration is approaching
  • whether the system is inside any grace-period logic

If Licensing Looks Wrong​

If licensing appears missing or invalid:

  1. confirm the server is reachable and healthy
  2. inspect the active license state
  3. confirm the correct license data is being used
  4. retry activation only if you understand the intended licensing workflow
  5. escalate if the state remains missing, corrupt, or expired unexpectedly