What a device limit counts
A device limit is the number of computers one license key may be active on at the same time. The app sends the key once per computer to an activate call, the server records an activation (also called an instance), and from then on the server refuses new activations once the count reaches the limit. Removing an activation frees the place.
The limit is not a count of people, launches or sessions. A buyer who opens your app a thousand times on one laptop uses one device. That is why the limit is a good fit for software that lives on a machine, and a poor fit for a web app that people open on borrowed computers.
A decision table by product type
There is no industry standard to copy, and I will not invent one. What follows is a reasoned starting point. Change it when support tickets tell you something different.
| Product type | Suggested limit | Why |
|---|---|---|
| Personal tool (note app, utility, menu bar app) | 3 | Desktop, laptop and a replacement machine. Low price, so the cost of a support email is high compared with the sale. |
| Professional tool at a mid price (editor, design app, audio host) | 2 or 3 | Buyers work at one desk and travel with one laptop. Three leaves room for a reinstall mistake. |
| Plugin or extension for a larger app | 3 to unlimited | Price is low and the host app often has its own checks. Policing seats may not be worth it. |
| Per-seat business license | 1 per key | You sell a key per person. Quantity three in checkout means three keys, so each person has their own. |
| Site license for a company | Unlimited, or a high number | The contract, not the limit, defines the scope. Pair it with a seat count in your terms. |
| Educational lab license | A high number, or unlimited | One order covers many shared machines. |
| Subscription app | 2 or 3 | The recurring payment already ties the key to a payer. |
Price matters more than the category. The cheaper the product, the less a stricter limit protects you, and the more a refused activation costs you in goodwill.
When an honest buyer runs out of seats
Here is a worked example with stated assumptions. A buyer owns two computers that use your app and replaces one of them every four years. They do not deactivate the old one, because nobody remembers to. Seats used after each replacement:
| Year | Event | Seats in use if never deactivated |
|---|---|---|
| 0 | Activate desktop and laptop | 2 |
| 4 | New laptop | 3 |
| 8 | New desktop | 4 |
With a limit of 3, the buyer is refused at year 8. With a limit of 2, they are refused at year 4, which is a long time before they would have bought an upgrade. The arithmetic is simple, but it shows two things. A limit of 2 turns a normal hardware replacement into a support ticket. And a limit only produces refusals from honest buyers if you do not give them a way to free a seat themselves. A self-serve device page removes most of that cost. Clavem’s buyer-facing page lives at /licenses/manage: the buyer pastes their key, sees each computer with the date it was last seen, and removes the ones they no longer use. No account and no email round trip.
What the API does at the limit
Here is a real response from the demo license, which has a limit of three and one active device. The request uses only the license key, as your app would.
curl https://clavem.io/v1/licenses/validate \
-d license_key="S1GNE-TDEM0-7K4QX-9WZ2P-H5RB8"
{
"valid": true,
"error": null,
"license_key": {
"id": 1,
"status": "active",
"key": "S1GNE-TDEM0-7K4QX-9WZ2P-H5RB8",
"activation_limit": 3,
"activation_usage": 1,
"expires_at": null,
"test_mode": false
},
"instance": null,
"token": "sgt1.eyJ2IjoxLCJsaWQiOjEsInBpZCI6MSwia2gi…"
}
The response is trimmed. activation_limit is 3 and activation_usage is 1. When every seat is taken and a new device tries to activate, the License API answers with HTTP 400 and this body, which comes from the API reference:
{
"activated": false,
"error": "This license key has reached the activation limit.",
"license_key": { "id": 1, "status": "active", "activation_limit": 3, "activation_usage": 3, "…": "…" },
"meta": { "…": "…" }
}
activation_limit: null means unlimited. Show the error text to the buyer, and add a link to your device page so they can fix it without writing to you. Do not parse the sentence for logic. Branch on the HTTP status and on activated.
Edge cases that cause support tickets
Reinstalling the operating system. The old activation still exists on the server and the new install does not know its instance id. If the app sends a stable fingerprint on activation, activating again on the same machine returns the existing seat and updates its name, instead of using a new one. If you send no fingerprint, each reinstall costs a seat until the buyer removes the old one. See machine fingerprinting pitfalls for what makes a fingerprint stable.
Replacing hardware. A new motherboard can change the identifiers you hash into a fingerprint. Treat it like a new computer: the buyer removes the old activation and activates again.
Uninstalling without deactivating. Most buyers drag the app to the trash. Unless your uninstaller calls deactivate, the seat stays used. Offer the device page link in the app’s license screen.
Virtual machines and cloned disks. A cloned disk image carries the same machine identifier to a second computer. With a fingerprint-based seat, the clone looks like the original, so both run on one seat. Decide whether that is acceptable and say so in your terms.
Shared and family use. A limit of three does not know whether three computers belong to one person or three. If that matters to you, price a multi-seat license and sell one key per person. The dashboard shows how many devices each license uses, so a key that sits at its limit is easy to spot.
Beta testers and reviewers. Create a license by hand with a higher limit instead of loosening the product default.
How limits interact with support load
A stricter limit does not reduce support work. It moves it. The work you remove is the case where one key runs on twenty computers. The work you add is the buyer who replaced a laptop and cannot activate. A rough decision rule that does not need statistics:
- Low price: use three or unlimited. Do not spend support time on enforcement.
- Mid-price professional tool: use three, and make the device page link obvious.
- High price or per-seat business tool: use one per key, sell quantities, and expect to handle transfer requests.
If you raise a limit for a single buyer, do it on that license rather than for the whole product. With the management API, PATCH /v1/admin/licenses/:id takes activation_limit as an integer from 1 to 10,000, or -1 for unlimited.
Where a device limit is the wrong tool
A device limit assumes software that is installed on a machine. Three cases do not fit.
Web apps and browser extensions. The same buyer signs in from any browser. A limit on “devices” counts browsers and profiles, which is not what you mean. Tie the license to an account and a seat count instead, which is a different model. See seat-based licensing for teams.
Floating or concurrent use. If twenty people share five seats and only five run the app at once, you need a count of who is running now, not who installed it. Clavem does not offer floating licenses in this version.
Per-user named licenses at a company. The unit is the person, so sell one key per person. A device limit of one per key keeps each person’s key off the colleague’s desk, and the buyer can still reinstall on their own new laptop through the device page.
Wording the limit so nobody is surprised
Say it where the buyer decides, and say what happens when they hit it. A sentence you can adapt:
One license works on up to three of your computers at a time. If you get a new computer, remove the old one on the device page and activate the new one. It takes a minute.
Put it on the product page, in the purchase email and in the app’s license screen. Buyers who learn about a limit from an error message feel punished, and buyers who read it in advance rarely notice it.
The product’s limit is a default. To help one buyer, change that license with the management API rather than the product’s default, so you know exactly which licenses change and the buyers who bought under one limit stay separate from those who bought under the next.
Doing this with Clavem
A Clavem product has a default device limit of 3, and unlimited is allowed. A license starts with the product’s limit, and you can change the limit on one license from the dashboard or with the management API. The first activation moves an inactive license to active. When the last device is removed, an active license returns to inactive. Both states are valid.
Activating again with a fingerprint that is already active on the license returns that seat instead of using a second one. Buyers can free seats themselves at /licenses/manage. Validation, activation and deactivation are not metered, and plan limits never block them. The three endpoints are in the API reference.
Questions
What is the most common device limit for desktop software?
There is no standard, and no published survey to cite. Two or three devices per personal license is common practice, because buyers usually own a desktop and a laptop and replace one now and then. Team and per-seat licenses usually allow one.
Does a device limit stop piracy?
Not by itself. It stops casual sharing of one key between many people, and it gives you a signal when a key is used far beyond what one buyer needs. Determined cracking is a separate problem.
Should I count a virtual machine as a device?
Decide in your terms and apply it consistently. A virtual machine that is cloned or restored from a snapshot can present the same machine identifier, or a new one, depending on how you fingerprint, so tell buyers what happens.