How schools buy and run software
A school or university does not look like either a consumer or a company. A teacher finds the software, a department head or an IT manager approves it, and a business office pays by purchase order. The software then runs on shared lab computers, on a cart of laptops, on machines that are re-imaged each summer, and sometimes on students’ own devices. Licensing has to fit that, or the first week of term turns into support calls.
What differs from a consumer or company sale
Many identical machines. A lab of 30 computers is installed from one image. If the image already holds an activation, every clone has the same stored instance id, and the device limit counts them as one: your limit stops meaning anything. If you activate on each machine, 30 seats are used. Pick on purpose.
| Approach | How | Result |
|---|---|---|
| Activate per machine | The image contains the key in a config file; the first launch on each machine activates with its own fingerprint | One seat per machine; the key needs a device limit of at least 30 |
| Site license | One key, a device limit set for the school (Clavem allows unlimited) | Simple for the school; you rely on the contract, not the count |
| Seat pack | A quantity of 30 at checkout, 30 keys | Strict; the school’s IT distributes keys |
| Image-time activation | Activate once on the master image | Counts one device for many; avoid unless it is what you sell |
For a school with several labs, a site license with a generous limit is the easiest for everyone. See site licenses and the site license glossary entry.
Deployment through tooling. IT staff install software with management tools, not by clicking through a dialog. Support a silent install and a way to pass the key: an installer parameter, an environment variable or a config file in a known location. The first launch under any user account must activate without asking.
School-year cycles. A license that ends in the middle of term, or that lapses over the summer, causes trouble when term begins. Options: a subscription that renews in the spring, a fixed validity of 365 days from purchase, or a validity that outlasts the term by a month. A subscription license in Clavem stays valid through the paid period plus three days, which is not enough to cover a long summer. Plan renewals before the date, and tell the school when they are due.
Shared devices and student data. Devices used by many students have no single owner. The app sends the key, a device name and a fingerprint to the License API; make sure the device name is the machine’s name, such as LAB2-PC14, and never a student’s or teacher’s name. Laws on children’s data differ between countries and regions, and a school will ask what your software collects. State it plainly. This is general information, not legal advice, so ask a professional for your market.
Locked-down networks. School networks filter traffic and sometimes block unfamiliar hosts. A failed validation must not block a lesson. Verify the signed token offline and trust it until refresh_by, 14 days after the last success. Over the school holidays, machines are switched off and a 14-day window will lapse; decide that after refresh_by the app still works for a grace period, so no teacher opens a lab with a license warning on the first morning. See offline verification.
Computers that cannot run keys. Chromebooks and iPads do not run a desktop app with a license key. For iPad, the App Store rules apply: see productivity apps. A web version avoids the problem.
Discounts
Education discounts are a Stripe coupon or a separate price. Decide how you verify eligibility, or choose not to and accept some leakage. A volume discount for larger packs is another price. See educational and volume discounts.
Purchase orders and invoices
Schools often pay by invoice after a purchase order. Stripe can send invoices, and a bank debit or transfer that settles later issues the license when Stripe reports the payment succeeded. Clavem handles that event, so a license appears when money does, not when the invoice is created. Taxes are yours to handle through Stripe, and many schools are tax-exempt in ways that depend on the country, so ask an accountant. Clavem is not a merchant of record.
Recommended setup
| Setting | Suggested value | Why |
|---|---|---|
| License type | Subscription or fixed 365-day validity | Matches the school budget year |
| Device limit | One key per school with a limit that covers all labs, or a seat pack | Simple counts for a site license |
| Trial | 30 days for teachers, or a limited free edition | Teachers try before they ask for budget |
| Updates | Releases endpoint, gated on a current license | Summer is when schools update |
Doing this with Clavem
Create a product per edition, such as single teacher, classroom pack and school site license. Map each Stripe price to a product. Buyers receive keys by email and an order page. Your installer takes a key as a parameter and your app activates at first launch. Follow the guide for your stack: C#, Java, Qt or Electron.
Guides to follow
Questions
How do I license software on a lab of identical computers?
Prepare the image without an activation. Deliver the key through a config file or deployment tool, and let each computer activate on first launch with its own fingerprint. The key needs a device limit at least as high as the lab, or you sell a key per machine.
Should a school license run for a school year?
A fixed validity, such as 365 days from purchase, or a Stripe subscription that renews each year, both work. Match the renewal to the school's budget cycle, and consider a summer grace period so machines work when term starts.