Two meanings
| Meaning | Who uses it | What it does |
|---|---|---|
| Vendor admin tool | The seller | Issues, finds, extends, limits and revokes licenses |
| Floating-seat daemon | A customer’s IT team | Runs on the company network and hands out floating license seats to whoever asks |
The second meaning comes from engineering and design software sold per concurrent user. This page concentrates on the first. The part that answers the app at run time is the license server.
What a vendor does with one
- Issue a license by hand for a reviewer, a partner or a replacement.
- Find a license by buyer email or key when a customer writes in.
- See which devices are activated.
- Extend an expiry, or change the device limit, as a one-off favour.
- Revoke a license after a refund or abuse.
- Resend the key email.
A support example
A customer writes: “I lost my key and I need to add my third laptop.” The seller finds the license by email.
curl "https://clavem.io/v1/admin/licenses?email=ada@example.com" \
-H "Authorization: Bearer sk_clavem_…"
The response lists matching licenses with key, status, activation_limit, activation_usage and expires_at. The ids and keys in a real response are yours. The seller then raises the limit to 4 with PATCH /v1/admin/licenses/412 and { "activation_limit": 4 }, and the customer activates. A year-long extension is the same call with a new expires_at:
curl -X PATCH https://clavem.io/v1/admin/licenses/412 \
-H "Authorization: Bearer sk_clavem_…" \
-H "Content-Type: application/json" \
-d '{ "expires_at": "2028-11-19T00:00:00Z" }'
Moving expires_at into the future also revives an expired license.
License manager versus license server
The server is the public side: the app calls it, and it must answer fast and without a secret. The manager is the private side: a person or a backend calls it, and it needs authentication. A product can ship both in one service, as Clavem does, but they have different users, different failure costs and different security.
How Clavem handles it
Three ways to manage licenses, all on the same data:
- Dashboard. A searchable Licenses table with key, buyer email, product and status. A license page shows the seal, activations and history, with actions to disable, enable, change the limit, change the expiry, resend the email and copy the order link.
- Management API. Bearer keys starting with
sk_clavem_, shown once and revocable, limited to 300 requests per 60 seconds per key. It creates, looks up, changes and disables licenses. It does not create products or delete licenses: disable instead, so the key still answers with a reason. - MCP server. Clavem is adding an MCP server at
https://clavem.io/mcp, with tools to look up, issue, extend and revoke licenses using a management API key. See the MCP docs.
Clavem has no floating-seat manager. It counts registered devices, not simultaneous users. Every endpoint and field is in the API reference, and license revocation covers the disable action in detail.
Questions
Do I need a license manager if I already have a license server?
You need some way to act on licenses, such as looking one up for a support email, extending a trial or revoking a refund. That can be a dashboard, an API you call, or a database you query by hand.
Which meaning applies to software sold online?
Usually the admin side. The floating-seat daemon is a term from software licensed per concurrent user on a company network.