Utility 02 / 05
Know every machineEven after a reinstall
Fingerprints part by part, clear move rules, seats returned when a machine goes quiet
Devices & HWIDMachines known part by part
Move rules
defaults · set per plan
- Moves
- 2 per 30 days
- Wait between moves
- 24 hours
- Silent machine
- seat freed after 72 hours
- Who may move
- you and the buyer
TPM keys · server ready, native SDKs next
How it works
- 01
The machine introduces itself
The SDK sends each component, not one single hash
- 02
The server compares parts
A little drift is the same machine, a lot is another one, with the reason
- 03
Moves under rules
Buyers free a machine within the limits you set
Everything in it
- Matched part by partNew disk, new card, fresh Windows, same seat
- Refusals with reasonsThe parts that changed are written down, allow it again in one click
- Move rulesMoves per month, the wait between them, who may move
- Seats come backA machine silent too long gives its seat to the next one
- Device blocksBlock a machine once, it is blocked across the app
- Hardware keysThe server accepts TPM keys, native SDKs are next
In code
const clavis = new ClavisClient({
appId,
appPublicKey,
device: await describeThisMachine(), // each part, not one hash
});
await clavis.activate(key); // a new disk or a fresh Windows keeps the seat
// Moving to another PC? Free this seat first, within the move rules
const { remaining } = await clavis.transfer();
Which plan has it
- Basic
- Up to 3 machines per key, every move rule
- Premium
- Up to 100 machines per key for studios and labs
Read more in Protect Hub