PRIVATE ADMINISTRATION
Manage access, simply.
Sign in to manage organizations, machines and activation permissions.
This administration endpoint is restricted to the server or your SSH tunnel.OVERVIEW
Licenses & machines
Organizations
Seats are allocated to individual clients.Clients
Each client owns a separate seat allocation.Prepare a personal installer authorization
The device must first generate its TPM key. Issue a ticket for its approved key only. A shared installer carries no company secret.
Machines
Revocation stops renewal; an already issued offline lease remains valid until expiry.Hardware trust
Unverified keys cannot activate. An administrator must independently validate the TPM attestation and its binding to the exact key below. Merely checking a box or receiving a claimed TPM key is not verification.
Recent administration activity
One installer. Controlled activation.
- The customer's PC runs
InterceptorLicenseAgent.exe --prepare-enrollmentto generate a TPM key. - Your trusted company backend verifies the customer's entitlement. An administrator independently approves the hardware key after verifying its attestation.
- Your backend requests a short-lived ticket bound to that exact public key. Keep company API credentials exclusively on your backend.
- Your installer passes the personal ticket to the console installer. A signed preflight proves key possession before driver installation; activation consumes a seat only after successful installation.
- Updates and repair preserve the machine key and activation. Explicit uninstall removes local authorization and requests server deactivation.
Updates do not consume another seat. Uninstall and revocation reserve the old seat until all previously issued leases have expired. Removing Windows or changing the TPM requires administrator recovery.
The current policy grants a maximum 24-hour authorization with a recommended renewal every 30 minutes. A missing connection never makes a revoked license immediately disappear on an offline machine.
This is a controlled implementation, not a guarantee of zero vulnerabilities. Device-key preapproval must be based on trustworthy evidence; a software-generated RSA key is otherwise indistinguishable to this service.