How it works
The server keeps a count of active devices per key. In Clavem’s responses it is activation_usage, next to activation_limit. Activation adds one. Deactivation subtracts one. When the two numbers are equal, the next activation fails with a 400 and the message This license key has reached the activation limit.
The limit counts devices that are registered, not devices running right now. A laptop that is switched off still holds its seat.
Choosing a number
These are starting points to adjust for your product, not rules.
| Who buys | Limit to start with | Reason |
|---|---|---|
| One person, one desktop app | 2 or 3 | A desktop and a laptop, plus slack for a replacement before the old one is removed |
| One person, a plugin used on several machines | 3 to 5 | Plugins follow users across studio and home |
| A household | 3 to 5 | Shared use is expected and cheap to allow |
| A team | One key per person | Sell quantity, not a high limit |
A Stripe line item with quantity 3 issues three keys in Clavem, up to 100 per line item, so a team gets one key each instead of one key shared by everybody.
A worked count
Take a limit of 3 and an app that sends no fingerprint. A customer reinstalls their operating system twice and never deactivates. Each reinstall looks like a new device, so two seats are lost on top of the real machine. A third activation on a new laptop then fails. If the app had sent a fingerprint, each reinstall would have returned the same seat. The limit is only as fair as the way devices are identified. See machine fingerprint.
Device limit versus seat and concurrent license
A seat is one person or one device allowed to use the software, depending on the vendor. A concurrent license counts how many copies run at the same moment and lets any machine take a free slot. A device limit counts registered machines, whatever they are doing. Clavem uses the device model only.
How Clavem handles it
- A product has a default limit. The quickstart default is 3, and unlimited is allowed.
- A license made through the management API can override it with
activation_limit: an integer from 1 to 10000, or-1for unlimited. Leave it out or sendnullto use the product’s number.0is refused. - Change an existing license in the dashboard or with
PATCH /v1/admin/licenses/:id:
curl -X PATCH https://clavem.io/v1/admin/licenses/412 \
-H "Authorization: Bearer sk_clavem_…" \
-H "Content-Type: application/json" \
-d '{ "activation_limit": 5 }'
- Activating again with a fingerprint already active on the license returns that seat instead of using another one.
- Buyers can free a seat themselves at
/licenses/manage.
On the demo license, a validate call reports "activation_limit": 3 and "activation_usage": 1. For how many devices to allow in practice, read how many devices per license. Every field is in the API reference.
Questions
Is a device limit the same as an activation limit?
Yes. Clavem calls the field activation limit in its API. Other tools say max devices, machines or seats. It is the same idea.
Can the limit be unlimited?
Yes. In Clavem an unlimited license reports a limit of null, and activations are never refused because of the count.