Add an existing (v0) licence— a file that was hand-issued before this service existed
Air-gapped customers licensed by hand are invisible here: nothing records that
they exist, when their contract ends, or which machine they are bound to — so
the fleet view and any renewal reminder are wrong until they are imported.
This mints no key and signs nothing; re-signing could produce a
different file from the one the customer already holds.
Manage licenses
No licenses yet.
Signing keys — which key signs what, and its fingerprint
v1 uses one key for every product. v0 uses one key per product —
each on-prem image pins its own public key, so an offline file can only
be issued for a product listed here.
Platform partners
Partner
Product
Status
Customers
Licenses
Quota
Slots/lic
Max term
Created
No partners yet — create one below.
Partners self-issue license keys through POST /partner/v1/licenses
with their bearer token; every key lands in the fleet table tagged with the partner.
The limits bound what they can issue without us.
New partner
On-prem customers (IAM)
Customer
Products
Access keys
Created
No customers found in the product groups.
New customer
Creates the product-neutral IAM user (tagged customer / project=on-prem / managed-by=manual-cli) and adds it to the selected product group(s) — that membership is the pull entitlement. Mint the access key separately: secrets go into 1Password, never through this dashboard.
Product groups
Console — executed AWS CLI commands & output
No commands executed yet — press Refresh to query AWS.
Executed commands and their console output will appear here.