How it works
The app builds a fingerprint when the customer first enters the key. A fingerprint is a short hash of something stable about the machine, such as a motherboard identifier. The app sends the key and the fingerprint to the licensing server, which records the pair. From then on the app only runs when the fingerprint it computes matches the one on record. See machine fingerprint and hardware ID for what to hash.
What a hardware change looks like
The binding is only as steady as the thing you hash. A worked case, using a seller who allows one machine per key:
- Day 1: the customer activates on a laptop. The app sends fingerprint
a1f3and gets back seat 1 of 1. - Day 90: the customer replaces the SSD and reinstalls the operating system. The app’s stored data is gone, so it asks for the key again.
- The app computes a new fingerprint,
c9d2, and calls activate. The seat is still taken bya1f3, so the server refuses withThis license key has reached the activation limit.
If the fingerprint came from the disk serial, the SSD swap changed it. If it came from the motherboard, it would have survived the swap and changed only after a board replacement. Whichever you pick, plan for the customer who sees the refusal: they need a way to free the old seat without writing to you.
Node-locked versus a device limit
| Node-locked | Device limit | |
|---|---|---|
| Unit | One named machine | N interchangeable devices |
| Binding | Fingerprint must match | Count of active devices |
| Customer with two laptops | Needs two licenses | One license, limit of 2 |
| Moving machines | Free the old one first | Free any one seat |
A device limit of 1 behaves like a node-locked license for a customer who rarely changes computers. The difference shows up on a reinstall: a strict node lock refuses any fingerprint but the recorded one, while a device count only asks whether a seat is free.
How Clavem handles it
Clavem enforces a count of activations, not an identity. Set the device limit to 1 on the product, or per license with activation_limit through the management API. When the app sends fingerprint on activate, activating again from the same machine returns the existing seat instead of using another. That makes a repeated activation harmless.
Validate does not compare fingerprints. The signed token carries the fingerprint as fp, so a strict node lock is the app’s job: verify the token, then compare fp with the fingerprint of the machine it is running on.
A customer can remove a machine themselves on the device page at /licenses/manage, with only the key. Clavem does not offer an offline activation flow with a hardware challenge. See activation and license transfer.
Questions
Is a node-locked license the same as a single-user license?
No. A single-user license names a person, who may use any of their own computers. A node-locked license names a machine, whoever sits at it.
What happens when a customer buys a new computer?
The old machine has to give up its seat first. The customer deactivates it, or the seller frees it, and then the new computer can activate with the same key.