Licensing (admin)
The Licenses page from the operator side — issuing and binding ed25519 keys to tenants, seats, expiry, heartbeat, and revocation. The other end of the customer licensing flow.
Licensing (admin)
The Licensing page is where an operator mints, seats, and revokes the license
keys that agents authenticate with. It requires the licenses.manage privilege —
without it the page shows a locked state ("You need the licenses.manage privilege
to issue, bind, or revoke licenses.").
This is the operator end of the license lifecycle. The customer end — what each tier unlocks, activating a key on a box, seat binding from the CLI, the offline grace window, and what expiry or revocation means for their servers — is documented in Licensing, seats & transfers. The two describe the same license from opposite sides: you issue it here, the customer activates it there.
What a license is here
A license row is the entitlement an agent presents on every privileged call.
Issuance generates a key; the raw key is shown once and only a masked form
(hsk_1234••••-••••-abcd) is stored for display. The agent-facing validator
(validateLicenseKey) accepts a row only while it is active, non-expired, and
non-revoked, so revoking here is what actually cuts a key off.
What the page shows
Four KPI stats sit at the top:
| Stat | Meaning |
|---|---|
| Active licenses | Count of active rows, with total ever issued |
| Seats used | Sum of seatsUsed over seats, with a % allocated |
| Bound servers | Total servers currently bound across all tenants |
| In-grace / expired | Rows in grace, expired, suspended, or revoked — needs renewal or a revoke |
The Issued licenses table lists every key with its tenant, tier, seats (used/total), bound servers, status, expiry, and last heartbeat.
| Status | Badge |
|---|---|
active | success |
grace | warning |
expired / revoked / suspended | danger |
Seats note.
boundServersandlastHeartbeatare derived live from the agents registry (how many agents report that license, and their most recent heartbeat).seatsUsedis honestly reported as 0 in the current store — there is no per-seat assignment model yet, so the used/total column shows allocation againstseats, not a live per-seat tally. Bound-server count is the real occupancy signal.
Issuing a license
Issue license opens a dialog:
- Pick a tenant. The dialog shows the selected tenant's tier and status, and its registered server count.
- Seats (optional). Leave blank to use the tier default; otherwise 1–100000.
- Mint + bind key. The key is issued bound to the tenant at that tenant's own tier — you don't choose a tier here; the license must match the account's plan.
Issuance is blocked for accounts that are past due ("must renew before issuing") or churned ("can export or restore data, but cannot issue new license codes"). It's also refused if the requested seats would push the account past its tier's server-seat capacity.
On success the dialog shows two things to copy, once:
- the raw key (the agent's bearer credential), and
- a ready-to-run install command with the key baked in.
Copy them before closing — only the masked form survives.
Seats, expiry, and heartbeat
- Seats are the number of servers a license may bind. The per-account seat
math (included vs. billable overage, available capacity) is computed against
the plan catalog and the tier's
maxServerscap, so you can't over-issue past what the account's plan allows. - Expiry is optional at issue time (
neverwhen unset); an expired row stops authenticating new privileged actions until renewed. - Heartbeat is the last time any agent on that license checked in. A key with bound servers but a stale heartbeat is a box that's gone quiet.
Binding and unbinding individual servers is driven from the customer/agent
side (hostssh license bind / unbind, or a migration that moves the seat) —
see the customer view.
Revoking a license
Each row's Revoke button (disabled once already revoked) asks for
confirmation — "…the tenant's bound servers will fail heartbeat after grace" —
then flips the row to revoked. Revocation takes hold on the agent's next
heartbeat; the offline grace window still applies, so a revoke is not
instantaneous on a disconnected box. Crucially, emergency restore of an
existing image still works even on a revoked license — the data-hostage promise
in the customer view holds through
revocation.
Audit
Both privileged actions here are recorded to the Audit log:
license.issue (with the tier and target tenant) and license.revoke (with the
license id), stamped with the acting operator, IP, and launch mode.
Related
- The customer side of every concept here → Licensing, seats & transfers
- Which tenants can hold which licenses → Tenants
- How issue/revoke appear in the trail → Audit log