Sell a site or lab license for your software
A school wants your app on every machine in its computer lab. A small studio wants it on eight workstations that different people use on different days. A firm asks for "a license for the office". None of them wants to buy a key per person, and the school may not be allowed to: lab software policies ask for a site license that covers the lab.
Small vendors already sell this, and mostly not with floating or concurrent licensing. They sell a site license: one purchase that covers a place, either with a stated number of machines or with no count at all. This guide shows three ways to offer one with Casazium License Server — hosted, or self-hosted — as it works today, and when each one fits.
In this guide a seat is one activated machine. The console calls
the number of seats a license has Max activations
(max_activations in the API). It builds on
Limit a license key to a set number of computers,
which covers activation and instance IDs in full.
What site and lab buyers ask for
- A school lab needs every lab machine covered, usually through one purchase order. Western Illinois University's lab software rules, for example, require a site license that covers the number of students who will use the software.
- A studio or small firm has a known set of workstations, and staff who move between them or leave.
- Both want one key to manage, not thirty, and someone to call when a machine is replaced.
Three ways to offer it
1. One license with many seats
Issue one license with as many seats as the site has machines: 25 for a 25-machine lab. Each machine takes a seat when it activates, and the 26th is refused. This is how FabFilter's site license works: a license for an institution, capped at the number of devices written into its key.
Use it when the buyer can tell you how many machines, and you want the count to hold. It's the default choice.
2. Seats that free themselves
The same license, but a machine that stops checking in eventually gives up its seat to a machine that needs one. Lab machines get reimaged, studio PCs get replaced, and a reinstalled operating system can look like a new machine; this way the old seat comes back without an email to you. You turn it on with Free inactive machines (a lease, below).
Use it when the buyer's machines change over the life of the
license. It needs your app to check in, by calling validate() at
launch, and a lease is at least a day long. It returns seats held by
machines that are gone, not by apps that are closed.
Reclaim license seats from machines that are gone
explains what happens when a lease runs out; for schools, see
Leases and school holidays below.
3. An honor-system site license
A license with no machine count: Unlimited seats in the console. Every machine that activates is still recorded, so you and the buyer can see how many are using it, but none is ever refused. The site's limits live in your license terms (one campus, one building, one company) rather than in License Server. Scooter Software, Vernier and Felt Tip all sell site licenses like this (Pricing).
Use it when the buyer is an institution you trust to keep to the terms, or when counting machines would cost you more support than it saves. A lease does nothing here: with no cap, no seat is ever reclaimed.
Setting it up
By hand, in the console
For a deal you closed by email or purchase order. On a hosted account, or in the self-hosted bundle's console: Licenses → Issue license.
| Field | For a site or lab license |
|---|---|
| Product ID | The same product as your single-user licenses. |
| Tier | A name your app and the buyer can read, such as site or edu-site (below). |
| Issued to | The school or company, or its IT contact's email. |
| Perpetual (never expires), or Expires on | Perpetual for a one-time purchase; an expiry for an annual site license. |
| Max activations | The number of machines: 25 for a 25-machine lab. |
| Free inactive machines | Never, After 30 days, After 90 days or Custom, for option 2. |
| Notes | The purchase order number, the site's address, the renewal date: anything you'd want when they email next year. |
| Limits (optional) | Leave empty. Its Seats and Users fields are usage limits your app can read, not the machine count; that's Max activations. |
The issue form has no unlimited option. For option 3, issue the license, then open it and choose Edit terms → Unlimited seats → Save. Edit terms also changes the machine count later, when the lab grows, without re-issuing the key. Using the Console describes every field.
Send the buyer the key, the portal link and how many machines they
bought. The Portal link is shown only once; if it's lost or the
IT contact changes, Reissue portal link on the license's page makes
a new one. The portal shows the tier (as Plan), the expiry and each
activated machine by its instance ID, a long string, with when it last
checked in if the license has a lease. From License Server 1.34.0 it
also shows how many machines are in use out of the license's count
("Machines: 18 of 25"), and with a lease, how many of them haven't
checked in recently, whose seats a new machine takes when the license
is full. On an older server the portal doesn't show the count, so tell
them. To free a seat for a replacement, IT deactivates the
machine that's gone: with a lease, usually the one that checked in
longest ago; without one, the portal only shows when each machine
activated. Casazium runs the portal on hosted
accounts; self-hosted, it's off until you turn it on (PORTAL_ENABLED).
Purchase orders and invoices. License Server doesn't create invoices or track purchase orders. Send the invoice from your own accounting tool or storefront, then issue the license by hand, with the PO number in Notes. If you issue before you're paid (net 30, say) and the invoice goes unpaid, Revoke the license.
On a hosted account, a site license counts as one license toward your plan, however many machines it covers and even with unlimited seats: Plans and quotas.
Through the API
These calls go to your own server, or on a hosted account to
https://license-cloud-api.casazium.com with your API key:
where these calls go.
curl -X POST https://your-license-server.example.com/v1/issue-license \
-H "Authorization: Bearer $ADMIN_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"tier": "edu-site",
"product_id": "my-product",
"issued_to": "it-helpdesk@school.example.edu",
"expires_at": "2027-09-30T23:59:59.000Z",
"max_activations": 25,
"lease_seconds": 15552000,
"notes": "PO 4471, Room 214 lab, renews each September"
}'
lease_seconds sets the lease: 15552000 is 180 days, and leaving it
out makes every seat permanent. The response's portal_token, returned
only this once, makes the buyer's portal link: your server's address
without /v1, then /portal/<portal_token>, so
https://license-cloud-api.casazium.com/portal/<portal_token> on a
hosted account.
max_activations must be at least 1 when you issue; for an
honor-system license, set it to null afterwards:
curl -X POST https://your-license-server.example.com/v1/admin/update-license-terms \
-H "Authorization: Bearer $ADMIN_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"key": "7yChyZcfMG23Dx1sjBoLziPFrH4n-6f28",
"max_activations": null
}'
Issuing Licenses has the full field list.
As a product in your storefront
To sell a site license off the shelf, create it as its own product or price in Stripe, Lemon Squeezy or Paddle ("Site license, 25 machines") and give it its own mapping in License Server, under Settings → Storefront webhooks on a hosted account. Self-hosted, create the mapping through the API: see Storefront Auto-Fulfillment. On the mapping, set:
- Tier to your site tier;
- Max activations (optional) to the machine count. Left blank, it's 1, so don't leave it blank here;
- Free inactive machines, if you want option 2;
- Duration in days (optional) for an annual license, or blank for perpetual.
Each purchase then issues one license with those terms and emails the key to the buyer. Use a fixed machine count per product and turn off quantity selection in your store: buying two still issues one license with the mapping's count. That's the simplest setup, and the only one for a one-time Stripe purchase.
On Lemon Squeezy and Paddle you can instead sell per machine: map a one-time product with Activations per unit set to 1 (and Max activations blank), and a purchase of 25 issues one license for 25 machines. On Paddle the license comes from the cart's first item, so keep the licensed item first: Per unit on one-time purchases. A Stripe checkout carries no quantity, so a one-time Stripe purchase always gets the mapping's fixed count.
A mapping takes a whole number of machines of at least 1, so it can't issue an unlimited license; sell an honor-system site license by hand, or give the mapping a count well above any site you'd sell it to.
Things to know before you create it:
- Mappings can't be edited. To change the count, delete the mapping and create it again, then fix licenses already sold with Edit terms.
- A subscription re-applies its mapping's terms on every plan change, so a site license sold as a subscription keeps the mapping's count, not one you set by hand: Storefront licenses overwrite what you set here. To sell per-seat subscriptions instead ("$8 per machine per month"), a mapping's Activations per unit follows the number of seats bought: Plan changes and seats.
- A full refund revokes the license, unless you've set the webhook to keep licenses after refunds (Refunds). A license you issued by hand isn't affected by any refund: revoke it yourself.
The Stripe, Lemon Squeezy and Paddle guides cover setting up a store.
Renewing an annual site license
For a site license you sold by hand, open the license, choose Edit terms and move Expires on to the next year. The key, the seat count and the activated machines stay as they are, so nothing changes in the lab. License Server doesn't remind the buyer; the console's dashboard shows licenses expiring in the next 30 days under Expiring soon. If a site license does expire, every machine on it stops at once, so for a school, set the expiry a few weeks after the end of term.
Sold through a storefront, an annual site license renews best as a yearly subscription: each payment extends the same key. A one-time purchase with Duration in days renews only by buying again, which issues a new key the lab must enter on every machine.
Let your app know it's a site license
The tier you chose comes back to your app. verifyKey() returns the
license's tier, and so does a signed offline license file, so your
app can show "Site license" in place of a personal name, or turn on an
education edition's features. The buyer's name isn't returned to the
app.
const license = await client.verifyKey(licenseKey, MY_PRODUCT_UUID);
const isSite = license.tier === 'site' || license.tier === 'edu-site';
A license's tier can't be changed afterwards with Edit terms. To move a customer from a single-user tier to a site tier, issue a new license.
Rolling it out across a lab
Activate on each machine, not on the master image. Many labs install software once on a disk image and copy it to every machine.
- Let your app activate on first launch on each machine: an activation saved in the image is copied with it.
- Each machine needs its own instance ID. Two machines that send the
same
instance_idare one machine to License Server, and share one seat. - With the SDK's
getFingerprint(): on Windows, build the image with Sysprep/generalize, and check that two imaged machines report different IDs. On Linux, empty both/etc/machine-idand/var/lib/dbus/machine-idin the image. Macs take theirs from the hardware. - If the license's Activations list shows fewer machines than the lab has, copies are sharing an ID.
Instance ID Generation shows how to make an ID on each platform.
Check before you activate. Activation is limited to 20 requests
per 15 minutes per license key, shared by every machine on it,
repeat activations included
(Rate Limits).
Some labs reset every machine at reboot (Deep Freeze, Reboot Restore)
or keep app data in each student's profile, so your app forgets that
it activated; if it then activates on every launch, the whole lab
activates every morning. So at launch call validate(key, instanceId)
first: it answers { valid: true } only when the license is good
and this machine already holds a seat. Activate only when it
answers valid: false; the activation then tells you if the license
itself is refused. If validate() throws instead (no network, or a
429), don't activate; try again later. Keep the key and activation
token machine-wide (on Windows, under C:\ProgramData), not in a
user's profile.
validate() has no per-key limit, only a per-network one: 1,000
requests per 15 minutes, shared with your app's other license and
update checks, by every machine behind the school's connection.
Expect a 429 on a big rollout. A 40-machine lab switched on for
the first time at once activates about half its machines, and the rest
are answered 429 until the 15 minutes pass. A 429 means "try
later", not "invalid key": have your app say "couldn't activate yet,
try again in a few minutes", or ask the lab to set machines up in
batches.
Leases and school holidays
A check-in renews a lease only once less than half of it is left (why), so a machine's lease runs out between half and all of the lease length after its last check-in. With the 90-day preset, a lab idle over a ten-week summer comes back with many machines lapsed. A lapsed machine keeps working until another machine needs its seat, but then loses it. A lapsed machine that checks in again before that keeps its seat. For a lab that sits idle all summer, choose Custom and 180 days or more: choose more than twice the longest gap between uses.
Labs with no internet
Activation needs to reach License Server, so a machine that never goes online can't take a seat. What does work offline is a signed license file: your app checks License Server's signature with its public key, with no network call. The file carries the key, tier, product, limits and expiry, but no seat count and no machine (its limits are usage limits). Every copy works on any machine until the license expires, so an offline lab gets an honor-system site license in practice, whatever its seat count says. Price it and word the terms that way.
A file can't be called back, either: revoking the license, or a
refund, doesn't stop a file already downloaded
(Refunds).
So give an offline site license an expiry, a year say, rather than
selling it perpetual, and send a new file when it renews. The buyer
can download the file from their license portal while Offer the
license file in the buyer portal is on for the product (Products
→ Edit in the console), or you can export it for them with
POST /v1/license-export/offline.
Pricing a site license
There's no standard price, but the public examples show the usual shapes:
- A flat price per site, with no count. Beyond Compare's site license is listed at $5,250 for Standard and $10,500 for Pro, unlimited users, and not concurrent (pricing).
- A price by number of seats. FrameForge's EDU site license is quoted from the number of seats the school wants, as an annual fee or a one-time purchase.
- Per person instead of per site. SmartGit (pricing) licenses each user on up to five machines, and lets a company reassign a license once a month. In License Server that's one license per person with a few seats.
- No published price. Felt Tip's site license, covering an organization within a stated radius, has a Buy button but no price, and education discounts by email. Vernier's site licenses don't count users or devices, and it offers site-license help to qualifying small schools by email. For a first school deal, talking to the buyer before you fix a price is a reasonable place to start.
Whatever you choose, write down in the terms you sell it under what the license covers: the machines or the site, home use by students or staff, moving it to new machines, renewal, and offline use. License Server enforces a machine count, or nothing; the rest is your agreement with the buyer.
What Casazium doesn't do
No floating or concurrent licensing. License Server doesn't count
how many copies are running at once, so "any 10 of our 30 machines at
a time" can't be enforced. The concurrent_sessions limit you can set on a license is a
cap on a counter that only ever goes up, so it can't track who is
running right now.
For most site and lab deals that's fine: count machines (options 1 and 2), or don't count at all (option 3). If you're losing deals because a buyer needs true concurrent seats, tell us about it.
Where to go next
- Limit a license key to a set number of computers — activation, instance IDs, and what the customer sees at the cap.
- Reclaim license seats from machines that are gone — free a seat by hand, and choose a lease length.
- Offline license verification — signed license files for machines without a network.
- Using the Console — the issue form, Edit terms and the Activations table.
More in Guides, or the full documentation.