What a seat is
“Seat” can mean three different things, and the licensing model follows from which one you mean.
- A named user: Ada has a seat and Bo has a seat, whatever machines they use.
- A device: eight machines may run the software at once.
- A concurrent user: eight people may use it at the same time, from any machine.
Clavem counts devices. A license has a device limit, each machine that activates takes one, and a deactivation frees it. That makes the second meaning native, the first approximate, and the third unavailable, because floating or concurrent licenses are not part of Clavem. This article covers the first two.
Three models
| Model | What the customer buys | What exists in Clavem | Leavers | Seat changes | Licenses used |
|---|---|---|---|---|---|
| One key per person | Quantity N in one Stripe line item | N licenses, each with a small device limit | Disable that person’s key | Add or disable a key | N |
| One team key | One line item, or a quote | One license with a device limit of N | Cannot revoke one person | Change the limit | 1 |
| Your own accounts | A team plan in your product | A key per account, or none | Remove the user in your system | Your admin screen | Few |
One key per person
Map the Stripe product to a Clavem product. When a buyer checks out with quantity eight, Clavem issues eight licenses in one order, up to 100 per line item, and emails the buyer all eight keys with an order page that lists them. Each key carries the product’s device limit. Set that limit to what one person needs, such as 2.
This is the cleanest answer to a leaver. Disable that person’s key through the dashboard or the management API, and nobody else is affected. The license answers valid: false with the status disabled from then on.
The costs are logistics and plan counts. The buyer receives eight keys and must hand them out. Clavem does not email each person or invite team members. And eight keys count as eight licenses toward your plan.
One team key
Create a single license with a device limit equal to the seat count. Everyone on the team enters the same key, each machine takes one of the eight seats, and the buyer manages the list on the device page.
The management API creates it directly:
curl https://clavem.io/v1/admin/licenses \
-H "Authorization: Bearer sk_clavem_..." \
-H "Content-Type: application/json" \
-d '{ "product_id": 75, "email": "it@acme.example", "name": "Acme", "activation_limit": 16 }'
Changing the seat count later is one request:
curl -X PATCH https://clavem.io/v1/admin/licenses/412 \
-H "Authorization: Bearer sk_clavem_..." \
-H "Content-Type: application/json" \
-d '{ "activation_limit": 20 }'
The weakness is the leaver. The ex-employee knows the key, so you cannot cut off one person without issuing a new key to everyone else. The buyer can remove that person’s device on the device page, but the person can activate again while a seat is free. A team key suits a small group that trusts each other, and a shared company key whose ownership never changes.
Counting seats and devices
If a seat means a person with a laptop and a desktop, a limit of eight is too low for eight people.
| Team | Seat means | Limit to set |
|---|---|---|
| 8 people, one machine each | One device per person | 8 |
| 8 people, laptop and desktop | Two devices per person | 16 |
| 8 people, plus a build server | One device each, one shared | 9 |
| 8 people on per-person keys | Two devices per key | 2 on each of 8 keys |
Be explicit in your pricing page about what a seat includes. If you say “per user” and then enforce per device, customers who use two machines will hit the limit and write to support. For the trade-offs see how many devices per license.
Plan limits and the cost to you
Clavem’s plans count active licenses, which are those that are neither revoked nor expired. The two models use very different numbers of them.
Assume 100 team customers averaging 12 seats each.
| Model | Licenses | Smallest Clavem plan that fits | Monthly price |
|---|---|---|---|
| One key per person | 1,200 | Studio (up to 10,000 licenses) | $79 |
| One team key | 100 | Indie (up to 1,000 licenses) | $29 |
Prices are from the pricing page. Going over a limit never blocks sales or validation, but it pauses manual creation and imports, which matters for the team-key model because you create those by hand. If the plan difference is small compared with the revenue, ignore it and choose the model that fits the customers.
The Stripe side
Stripe quantity is the natural fit for per-person keys. A Checkout Session with line_items[0][quantity]=8 produces eight keys. The edge case to plan for is a change after checkout. Clavem issues licenses on checkout.session.completed. Its other subscription events extend or expire licenses that already exist, and none creates new ones.
That has three consequences:
- A customer who raises the quantity from 8 to 9 through Stripe’s customer portal is billed for nine seats but has eight keys.
- A customer who lowers the quantity from 8 to 6 is billed for six but keeps eight working keys.
- A cancellation expires every key in the subscription together.
Handle seat changes by hand, or with a small script that watches your own Stripe events and calls the management API. For the first, a reminder in your support process is enough at small volumes. See subscription licenses with Stripe Billing for the full event table.
A small script for seat changes
If seat changes are frequent enough to hurt, write a small job on your own server that listens to your own Stripe webhook for customer.subscription.updated, reads the quantity on the subscription item, and compares it with the number of licenses you recorded for that subscription. Where the quantity went up, create the difference with POST /v1/admin/licenses. Where it went down, disable keys, preferably the ones with no active devices, using PATCH /v1/admin/licenses/:id with disabled set to true. Keep the comparison idempotent, so a repeated event creates nothing twice. The management API allows 300 requests per 60 seconds per API key, which is far more than a seat change needs. Clavem does not do this for you, so test it in Stripe’s test mode before you rely on it.
When you need real team accounts
Roles, invitations, per-user usage, single sign-on and an admin screen where managers add and remove people are accounts, not licenses. Clavem leaves team seats out of its first version and does not replace your user table. If your product needs them, keep users in your own system. Your backend can still call the License API with a team key to answer “is this team paid up”, so the key does the billing check and your accounts do the identity.
Doing this with Clavem
For up to a few dozen seats, per-person keys through a Stripe quantity are the least work and handle leavers. For a small trusted team, one key with a device limit is fine. Larger customers usually want an invoice and a single contract, which is the territory of site licenses for companies.
Questions
Does Clavem have team seats or user accounts for buyers?
No. Buyers never create a Clavem account. A purchase produces license keys and an order page. Roles, invitations and named users are not part of Clavem, so a product that needs them keeps its own user table.
What happens when a customer raises the seat quantity in Stripe after buying?
Clavem issues licenses when a Checkout Session completes. A later quantity change on the subscription does not create new keys. Add seats by creating licenses with the management API, or sell extra seats through a new checkout.
Does a seat mean a person or a device?
In Clavem a limit counts active devices, called instances. If a seat means a person who may use two machines, set the limit to seats multiplied by devices per person, or issue one key per person with a limit of two.