What a site license is
A site license lets everyone in a defined organization use the software under one agreement and one key. The unit being sold is the company or the location, not the person. Customers like it because they do not count people or chase leavers. Sellers like the larger deal and the single renewal.
It sits at the end of a line of models. A single-user license covers one person. A seat or volume license covers a counted number of people. A site license covers an organization, up to a limit you choose. The choice follows from how your customers think about your product. If they ask “how many licenses do we need”, sell seats. If they ask “can everyone use it”, sell a site.
Technical shape in Clavem
A site license is one license with a large device limit. You create it by hand, because a card checkout would not know the company’s size:
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 GmbH, site license",
"activation_limit": 300,
"expires_at": "2027-12-31T00:00:00Z"
}'
activation_limit accepts 1 to 10,000, or -1 for unlimited. Setting expires_at to a date makes it a term license that expires on that day, and leaving it out follows the product’s validity. The response returns the key and an order_url, the customer’s private page with the key, the downloads and the activation instructions. Send that link with the invoice.
The license counts as one active license toward your Clavem plan, whatever its device limit, which makes it cheap to carry. The buyer’s administrator can see and remove devices on the device page by entering the key.
Price it
There is no single right formula. Three common approaches:
| Approach | How it works | Strength | Weakness |
|---|---|---|---|
| Bands by company size | A fixed price for 1 to 25, 26 to 100, 101 to 500 people | Easy to quote and compare | A customer at the top of a band pays the same as one at the bottom |
| Per seat with a floor | A price per person with a minimum, such as 10 seats | Fair for the customer | Needs a headcount, and seats become a negotiation |
| One flat company price | A single large number | Simplest | Hard to defend for a very small or very large company |
Worked example
Assume an individual license costs $49, and you want a site license to feel like a clear discount at 10 or more users. The figures below are an example, not a recommendation.
| Band | Site price | Equivalent in individual licenses | Price per person at the band’s top |
|---|---|---|---|
| Up to 25 people | $490 | 10 | $19.60 |
| Up to 100 people | $1,290 | about 26 | $12.90 |
| Up to 500 people | $2,990 | about 61 | $5.98 |
| Larger than 500 | Quote |
At 25 people, a customer who would otherwise buy individually pays $1,225. The band price is 40% of that, and nobody has to count seats. At the top of a band the customer saves a lot, which is the point. At the bottom a small company can pay more than seats would cost: a 5-person company pays $490 where five individual licenses cost $245. That is the trade-off of bands. Offering a per-seat quote next to the band price lets small customers choose.
Keep one rule across all bands: a site license is for one legal entity and its employees, and it does not cover affiliates or contractors unless the contract says so.
Cap it, do not leave it unlimited
Clavem allows unlimited devices with a limit of -1. The risk is a key posted on a forum or a coupon site. An unlimited key then works for everyone who finds it, and nothing stops it. A finite cap changes that: set the limit to a multiple of the stated headcount, such as 3 times for a company that uses laptops and desktops. A leaked key then fills up and refuses new activations, and the real customer’s staff meet the limit and contact you, which is how you find out.
If the key does leak, disable it with PATCH and "disabled": true, then issue a new one and send the customer the new order page. The old key returns valid: false with the status disabled from then on. Devices that already hold a token keep working until the token’s 14-day refresh window ends.
Audit at renewal
The management API returns one license with its active devices. Each instance carries a name, the activation time and the time it was last seen. Before a renewal conversation, count devices seen in a recent window and look for names that do not fit. I ran this on sample data in the same shape as the API’s response:
const recent = instances.filter((i) => now - Date.parse(i.last_seen_at) <= 90 * DAY);
const stale = instances.filter((i) => now - Date.parse(i.last_seen_at) > 90 * DAY);
const odd = recent.filter((i) => !/^ACME-/.test(i.name));
With five sample devices and a limit of 300, it reported four seen in the last 90 days, one not seen since June, and one host name that did not match the customer’s naming scheme. That is the sort of output that starts a friendly conversation: “your license has 4 active devices, and one has a name we do not recognize”. Do not treat it as proof of misuse, because machines get renamed and imaged.
Ask customers to name devices with a pattern when they install, for example the computer’s asset tag. The app can send the computer’s name as instance_name, and the pattern then makes the audit easy.
Terms the contract must settle
Write the answers down, in the order form, the agreement or your terms, so they are not argued later.
| Question | Typical answer |
|---|---|
| Who is covered | Employees and contractors of one legal entity, or of named sites |
| What is the term | One year, renewing, with the price held for the first renewal |
| What happens at renewal | The key’s expiry moves forward when the invoice is paid |
| What counts as a device | A machine that has activated the software |
| Can the key be shared outside the company | No |
| What if the company grows | A price band applies at the next renewal |
Hand-made licenses are not tied to a Stripe subscription, so Stripe’s events never change them. Extend the date yourself when the invoice is paid, and record the renewal in your own system.
Doing this with Clavem
A site license is a license you create by hand with a high device limit and an expiry, delivered through its order page. Clavem does not send invoices, track headcount or bill by size. Stripe invoicing and your own records do that. The API reference lists the fields, and selling software to businesses covers the surrounding process.
Questions
What is the difference between a site license and a volume license?
A site license covers everyone at a defined company or location for a flat price. A volume license sells a counted number of seats, usually at a discount per seat. A site license is simpler to buy and to administer, and harder to price, because you are guessing how many people will use it.
Should a site license have an unlimited device limit?
Usually not. Clavem allows unlimited with a limit of minus one, but a high finite cap such as several times the headcount gives the same experience for honest use and limits the damage if the key is posted publicly.
How do I know how many people a site license is really used by?
Read the license through the management API. It lists each activated device with its name, activation time and last seen time. Counting devices seen in the last 90 days at renewal gives you a basis for a conversation, not proof.