How it works
The buyer is an organization, not a person. The seller defines the scope, usually one of these: a physical location, a legal entity, a campus, or a named number of staff. The buyer pays one fee, often per year, and anyone inside the scope may use the software. The seller usually issues one key or one installer configuration, and the contract, not the software, carries most of the limits.
Worked break-even
Example numbers. Per-seat price: $40 a year. Site license: $3,000 a year. The site license is cheaper from 3,000 / 40 = 75 seats. A company with 120 staff pays $4,800 at per-seat prices or $3,000 flat. A company with 30 staff pays $1,200 per seat and would never take the site license. So a site license suits large buyers who would otherwise negotiate a quote, and it saves them procurement work: one invoice, no seat counting. The seller’s cost of that convenience is the headcount they never see.
Site license versus volume license
A volume license still counts seats and lowers the price per seat as the count rises. A site license replaces the count with a flat price. Per-seat licensing makes the buyer track who holds each seat. A site license removes that task.
How Clavem handles it
Clavem has no organizations, teams or team seats. A license belongs to one buyer, identified by an email address. The workaround is one license with a high device limit, created through the management API with your secret key:
curl https://clavem.io/v1/admin/licenses \
-H "Authorization: Bearer sk_clavem_…" \
-H "Content-Type: application/json" \
-d '{
"product_id": 75,
"email": "it@acme.example",
"name": "Acme Corp IT",
"activation_limit": 500,
"expires_at": "2027-11-19T00:00:00Z"
}'
activation_limit takes 1 to 10000, or -1 for unlimited. expires_at makes it an annual deal; leave it out and the license follows the product’s validity. The response includes order_url, a private order page with the key, which you pass to the company’s IT contact. Each employee’s machine then activates the same key. The buyer can see and remove devices on /licenses/manage with the key.
Know the limits of this setup. Clavem does not tell you which employee holds which device, only the device names your app sends. Disabling the key switches off the whole company. A license made by hand counts against your plan like any other, as one license however many devices use it. See device limit and the API reference. Details on selling this way are in site licenses for companies.
Questions
Does a site license mean unlimited users?
Not always. Many site licenses cap headcount or devices, or cover only one campus or legal entity. The contract should say what counts as the site and who counts as a user.
How is a site license different from a volume license?
A volume license still counts seats and lowers the price per seat as the count rises. A site license replaces the count with one flat price for the whole organization.