What is inside one
| Part | Job |
|---|---|
| Database | Licenses, activations, products, buyers, expiry dates |
| License API | Activate, validate and deactivate, called by the app |
| Issuance | Creates a key when a payment succeeds, usually from a payment webhook |
| Signing keys | Sign answers so the app can check them offline |
| Admin side | Search, extend, revoke, resend a key |
| Abuse control | Rate limits per IP address and per key |
| Delivers the key to the buyer |
In enterprise engineering software, “license server” can also mean a daemon that hands out floating seats on a company network. This page covers the internet service for sold software.
How it fails
A license server is a dependency on your app’s launch path, so decide in advance what the app does when it gets no answer. The failures and a sensible reaction:
| Failure | Clavem’s response | App reaction |
|---|---|---|
| Database unreachable | 503 with Retry-After: 5 |
Use the stored token if it is still fresh |
| Too many requests | 429 with Retry-After: 60 |
Back off, use the stored token |
| No network on the device | No response | Verify the stored token offline |
| Server gone for good | None | Tokens stay valid until refresh_by |
The documented fallback is to verify the stored signed token. Trust it if the signature is good, valid is true, exp has not passed and refresh_by is in the future. Past refresh_by, ask the customer to connect once. Validate once per launch, not in a loop: the rate limits are 120 requests a minute per IP address and 60 per key.
Build or buy
| Build | Use a hosted one | |
|---|---|---|
| Control | Anything, including floating seats and on-premise | The vendor’s model |
| Your time | Keys, webhooks, signing, rate limits, email, admin screens, patching | An integration |
| Uptime | You carry it | The vendor carries it, and your app falls back to signed tokens |
| Cost | Hosting plus your hours | A subscription |
Build when your rules are unusual or the customer’s network forbids outside calls. Buy when the rules are ordinary. The longer version is in should you build your own license server.
How Clavem handles it
Clavem is a hosted license server at https://clavem.io. The app calls it with no secret, since the key is the credential. Every answer carries a token signed with the product’s Ed25519 key, so a valid license still proves itself when the server cannot be reached. You can export every key, buyer and status as CSV, and the paths and fields match the Lemon Squeezy License API, so moving to another server or your own is a hostname change.
For the admin side, see license manager. Endpoints are in the API reference, and the offline fallback is in the offline verification docs. The honest comparison is Clavem versus building your own.
Questions
What happens to my app if the license server is down?
That is your decision, made in the app. Common choices are to trust the last signed answer for a fixed window, or to refuse to run. Failing open for a limited time is kinder to honest customers.
Is a license server the same as a license manager?
No. The server answers the app at run time. The manager is the admin side where the vendor issues, searches and revokes licenses. Many products ship both.