One account, one product per app
Clavem’s unit is the product. Each app, plugin or edition you sell is a product with its own device limit, validity, signing key and release files. A product’s tokens are signed with its own Ed25519 key, so a key for one app does not work in another, as long as each app checks pid and uses its own public key.
For a studio, that gives a tidy structure:
| You sell | Clavem products | Stripe |
|---|---|---|
| App A, App B, a plugin | Three products | A Stripe product and price for each |
| A bundle of A and B | Products A and B | A checkout or Payment Link with both prices as line items |
| Annual and lifetime editions of App A | Two products, one with a subscription validity and one perpetual | Two prices, each mapped to its own product |
When one checkout contains several mapped items, Clavem creates a license for each. A bundle is therefore a checkout with two line items, optionally with a Stripe coupon for the discount, and the buyer receives two keys, each limited by its own product’s device limit. A mapping can target a whole Stripe product or a single price, and the price mapping wins over a product mapping, so a monthly and a lifetime price of the same Stripe product can issue licenses for different Clavem products.
Plans decide the catalogue. Indie allows 5 products and 1,000 active licenses. Studio allows unlimited products, 10,000 active licenses and 50 GB of file storage for 79 USD a month. A studio over five apps, or one that imports a back catalogue of keys, needs Studio. See pricing.
Who does what
Clavem does not offer team seats, so decide roles in your studio first.
| Task | Who and how |
|---|---|
| Create products, set policies, upload releases | The person who holds the dashboard login |
| Look up a customer, resend a key, extend a license | Support, through the dashboard, or an assistant using the MCP server with a management API key |
| Create licenses by hand for a partner or a press copy | A script with a management API key (POST /v1/admin/licenses) |
| Check status in a backend | A service with its own API key, revoked when no longer needed |
| Connect or change Stripe | The person who owns the Stripe account |
API keys start with sk_clavem_, are shown once and can be revoked at any time. Give each service its own, and keep them on servers; the management API sends no CORS headers because it must only be called from a server. The management API does not create products or delete licenses: disable instead, so a key keeps answering with a reason.
Creating licenses by hand counts against your plan like any other. Stripe purchases never stop at the limit.
A release routine for several apps
Files and releases belong to a product and are uploaded in the dashboard. A release has a version of up to 64 characters, notes and one or more files with a platform label. A product cannot have the same version twice.
A routine that works for a small team:
- Build and sign each platform’s installer in CI.
- Upload to the product’s release page, with the platform label and release notes.
- Test the download from a test purchase before you publish.
- Publish. The latest published release is the one customers get.
- If a build is bad, unpublish it. The previous release becomes the latest again.
“Latest” means most recently published, not highest version number, so a backport published after a newer build becomes the latest. Plan for that. Storage is per account: add up the files of every app. Three apps with 300 MB installers on two platforms are 1.8 GB for one version, so Indie’s 10 GB holds about five versions before you must delete old builds; Studio’s 50 GB gives much more room. Delete builds you no longer offer. See releases and downloads.
Selling to businesses
Studios often sell to companies as well as individuals. Quantity at checkout issues one key per seat, up to 100 per line item. Stripe handles invoices and tax IDs; Clavem is not a merchant of record. See software for businesses for what is missing and what to tell buyers.
Support without a help desk
Most licensing support is three questions:
- “I lost my key”: the order page link from the original email shows it, and you can search by email and resend.
- “I changed computers”: the buyer removes the old device on the device page at
/licenses/manage, with no account. - “I was charged twice or want a refund”: a full refund in Stripe disables the licenses of that order.
Write these into your help page, and link them in the receipt.
Recommended setup
| Setting | Suggested value | Why |
|---|---|---|
| Plan | Indie for up to five apps; Studio beyond that or with large files | Limits are the only difference between plans |
| License type | Per product, to match its pricing model | Each product has its own policy |
| Device limit | 2 or 3 for personal apps; one key per seat for business | Matches the buyer |
| Roles | One dashboard owner; API keys per service | No team seats |
Doing this with Clavem
Create one product per app, connect Stripe, and map each price, including bundles. Follow the guide for each app’s stack; a studio often uses several, for example Swift for a Mac app, Electron for a cross-platform one and PHP for a WordPress plugin.
Guides to follow
Questions
Which Clavem plan suits a small studio with several apps?
Indie holds up to 5 products and 1,000 active licenses for 29 USD a month. Studio holds unlimited products, 10,000 active licenses and 50 GB of files for 79 USD a month. Every feature is on every plan; only the limits differ.
Can several people use the Clavem dashboard?
Clavem does not offer team seats. Plan around one account: decide who holds the login, and let tools and scripts use management API keys, which you can create and revoke separately.