Glossary
Software licensing glossary
Short, plain explanations of the words used in software licensing and selling software online.
Business models
- Affiliate programAn affiliate program pays partners a commission on referred sales. How payout windows work, a worked commission example and how refunds affect license keys.
- ChurnChurn is the share of customers or recurring revenue lost in a period. The formulas, voluntary versus involuntary churn, and a worked example.
- Dual licensingDual licensing offers one codebase under an open-source license and a paid commercial license. Who can do it, a worked example, and where license keys fit.
- Educational discountAn educational discount gives students and teachers a lower price. Three ways to run it with Stripe and license keys, plus a worked 50 percent example.
- FreemiumFreemium means a free version that never expires plus a paid tier with more. How to gate features on a verified license token, and how it differs from a trial.
- Lifetime dealA lifetime deal sells permanent access for one payment. Break-even maths for buyer and seller, the cash-flow risk, and how it differs from a perpetual license.
- MRR (monthly recurring revenue)MRR is the subscription revenue you can expect each month. How to convert annual plans, what to leave out, and a worked example for software sellers.
- Open coreOpen core is an open-source core with paid proprietary features. How a license key gates the paid module, with tested code, and versus source-available.
- ResellerA reseller sells your software to its own customers at a discount or margin. How money and license keys flow, with a worked margin example.
- Software escrowSoftware escrow deposits source code with a neutral third party that releases it to customers on set events. How it works, who asks for it, and what it is not.
- Software maintenanceSoftware maintenance is a fee for updates and support after a perpetual purchase. How a cutoff date works, and how to build it from Clavem's license dates.
- Source-availableSource-available software has public code but a license that is not open source by the OSI definition. The Business Source License as an example.
- Upgrade pricingUpgrade pricing is a lower price for owners of an old version moving to a new major one. How to set it up with Stripe and a second product in Clavem.
- Usage-based pricingUsage-based pricing charges for what a customer consumes, not a flat fee. Units, tiers, a flat-versus-usage break-even example and how Clavem fits.
- White-labelWhite-label means selling a product under someone else's brand. What it means for license pages and checkout, and which parts Clavem lets you brand.
Distribution and updates
- AppcastAn appcast is the RSS feed Sparkle reads to find new versions of a Mac app. The format, a minimal item, and why expiring download links break a static feed.
- Auto-updateAn auto-update checks for a newer app version, downloads it and installs it. How update checks work, how licenses fit in, and the Clavem endpoint.
- Delta updateA delta update is a patch holding only the differences between two app versions. How Sparkle handles deltas, a size example and the full-download fallback.
- InstallerAn installer puts your app on a customer's machine. Common formats for macOS, Windows and Linux, why keys stay out of it, and how Clavem serves it.
- NotarizationNotarization is Apple's automated scan of Developer ID software before it ships. The workflow with notarytool and stapler, the edge cases, and what to upload.
- Release channelA release channel is a named track of updates such as stable or beta. How channels work, the "latest" trap in Clavem when you publish a beta, and a workaround.
- Semantic versioningSemantic versioning numbers releases MAJOR.MINOR.PATCH. The precedence rules for pre-releases, a tested comparison that fails, and how Clavem treats versions.
Keys and activation
- ActivationActivation registers a license key to one device so the server can count seats. See the request, the response and every error an activation call returns.
- DeactivationDeactivation removes a device from a license key and frees its seat. See the API call, what the server returns and the edge cases around lost machines.
- Device limitA device limit caps how many computers one license key can be active on. How it is counted, how to pick a number and what happens when it is reached.
- EntitlementAn entitlement is what a license lets its holder do: product, features, versions, devices and period. Which fields carry it in Clavem, and which are signed.
- Grace periodA grace period keeps a license working briefly after a payment or renewal date passes. The three different windows in a Stripe-backed license, with dates.
- Hardware IDA hardware ID is the raw identifier an operating system holds for a computer. Where it comes from on macOS, Windows and Linux, and why you hash it first.
- License expiryLicense expiry is the date a license stops being valid. How perpetual, fixed-term and subscription licenses expire, with a dated example and the API response.
- License keyA license key is the code a buyer enters to activate software they paid for. How keys are generated, checked and tied to devices, with examples.
- License managerA license manager is the vendor-side tool for issuing, finding, extending and revoking licenses. Two meanings of the term, and a support example with the API.
- License revocationLicense revocation ends a license before its expiry date. How it works, what triggers it, and why an offline device can keep running for up to 14 days.
- License serverA license server stores licenses and answers an app's validity checks. Its parts, how it fails, and how an app should behave when it is unreachable.
- License transferA license transfer moves a license to another computer or person. How device and owner transfers differ, and how to handle both with Clavem and Stripe.
- Machine fingerprintA machine fingerprint is a hash that identifies a device for licensing. Which inputs are stable, how collisions happen and how to send one to a license API.
- MCP serverAn MCP server exposes tools to AI assistants through the Model Context Protocol. How it differs from a REST API, and the Clavem server for licenses.
- Offline activationOffline activation registers a license on a computer with no internet. How challenge-and-response works, and what a signed token gives you without it.
Licensing models
- Concurrent licenseA concurrent license caps how many people use software at the same moment. How it relates to floating licenses, and how to size one from peak usage.
- Floating licenseA floating license is a pool of seats users check out on launch and return on exit. How leases and heartbeats work, with a 20-engineer example.
- License seatA seat is one unit of licensed use. It can mean a user, a device or a concurrent session. How the three differ, and how seats, keys and devices map in Clavem.
- Metered licensingMetered licensing ties access or price to measured usage such as exports or tokens. How to count, enforce and bill it, and why the counter lives on your server.
- Node-locked licenseA node-locked license ties software to one specific computer. How the machine fingerprint binds it, what breaks after a hardware change, and how to set it up.
- Perpetual licenseA perpetual license lets a buyer use a software version forever after one payment. What it does and does not include, and how it differs from a lifetime deal.
- Site licenseA site license covers everyone at one organization for a flat price. Break-even against per-seat pricing, and how to issue one in Clavem.
- Subscription licenseA subscription license stays valid while payment is current. A dated renewal timeline and the Stripe statuses that keep it valid or end it.
- Trial licenseA trial license lets a buyer try software for a limited time. Three ways to build one, with a real API request and the trade-offs of each.
- Volume licenseA volume license sells many seats to one buyer at a lower price per seat. A worked tier table, the price cliff to avoid, and how Clavem issues one key per seat.
Payments and billing
- ChargebackA chargeback is when a buyer's bank reverses a card payment. How Stripe disputes work, what they cost, and why a license stays active until you disable it.
- Coupon codeA coupon code is a code a buyer enters at checkout to get a discount. Stripe coupons versus promotion codes, percent versus amount off, with worked numbers.
- DunningDunning is how a subscription business recovers failed payments with retries and reminders. A dated timeline of Stripe's retries and the license state.
- Idempotency keyAn idempotency key is a unique value that makes a retried API request safe to repeat. How Stripe uses it, a double-charge example, and Clavem's approach.
- Payment processorA payment processor moves a card payment from the buyer's bank to yours. How a payment flows, how a processor differs from a gateway and a merchant of record.
- ProrationProration credits or charges the unused part of a billing period when a subscription changes mid-cycle. A worked upgrade and what it means for licenses.
- Stripe CheckoutStripe Checkout is a hosted payment page for one-time purchases and subscriptions. How Checkout Sessions work and how a paid session becomes license keys.
- Stripe customer portalThe Stripe customer portal lets subscribers update cards, see invoices and cancel without emailing you. What it covers, what it does not, and license effects.
- WebhookA webhook is an HTTP request one service sends to your URL when something happens. How signatures, retries and duplicates work, with a tested Stripe example.
Security and cryptography
- API keyAn API key is a secret a server sends with each request to prove who it is. How they work, where they must never go, and the real Clavem 401 responses.
- Code obfuscationCode obfuscation rewrites a program so it behaves the same but is harder to read. What it does for a license check, what it costs you, and where it stops.
- Code signingCode signing attaches your certificate-backed signature to an app so the OS can name the publisher and spot tampering. How it works on Windows and macOS.
- Digital signatureA digital signature proves a message came from a private key holder and was not changed. A tested example, and how it differs from a MAC and an e-signature.
- Ed25519Ed25519 is a fast signature algorithm with 32-byte public keys and 64-byte signatures. How it works, how it compares with RSA, and a Node.js example.
- Keygen and crackA keygen makes valid license keys and a crack removes the license check. How each works, why random server-checked keys beat keygens, and what is left.
- Public-key cryptographyPublic-key cryptography uses a key pair, one half secret and one public. Why that lets an app verify licenses offline, with a table against shared secrets.
- Rate limitingRate limiting caps requests per time window. The 429 response, Retry-After, Clavem's exact limits and how a licensed app should behave.
- Signed license tokenA signed license token is a small signed document a license server returns so an app can verify a license offline. See a real one decoded, field by field.
- Software piracySoftware piracy is using or copying software without a license. The main forms, which defences fit each, and what a license service can and cannot stop.
Tax and legal
- EU VAT on digital servicesSoftware sold to EU consumers is taxed where the buyer lives. What counts as a digital service, the 10,000 euro threshold, the One Stop Shop and an example.
- EULA (end user license agreement)An EULA is the contract that sets what a buyer may do with your software. The clauses to include, how it lines up with device limits, and what it is not.
- Merchant of recordA merchant of record is the legal seller of an online sale and handles tax and disputes. What changes for software sellers and how it differs from Stripe.
- Refund policyA refund policy states when buyers get their money back and what happens to their license. What to include, EU rules for downloads, how a refund revokes a key.
- Sales tax softwareSales tax software works out which tax applies to each sale, collects it and tracks where you must register. What it does for software sellers, and its limits.