Clavem

Clavem vs Keygen: which license server fits software sold through Stripe

Keygen is a general-purpose licensing and distribution API with floating, metered and entitlement models, self-hosting and an SLA tier. Clavem is narrower: it turns Stripe payments into keys, downloads and device limits for about a third of Keygen's entry price. Pick Keygen for complex licensing models, Clavem for a Stripe-based shop with ordinary per-device keys.

Side by side

Keygen facts below are as of November 2026, from Keygen’s own pricing page and documentation. Clavem facts come from its pricing and API reference.

Clavem Keygen (as of November 2026)
Price Free for 50 active licenses; $29, $79 or $199 a month for 1,000, 10,000 or 50,000 Free Dev tier for 100 active licensed users; Std 1 $99, Std 2 $299, Std 3 $599 a month for 1,000, 10,000 and 25,000 users
Cut of your sales None None; Keygen states it never takes a percentage of revenue
Fees on 100 sales of $49 $29 plan, plus Stripe’s own fee: about $201 $99 plan, plus Stripe’s own fee: about $271
Merchant of record No No
License keys Created when Stripe confirms a payment Created through the API; you connect Stripe by webhook or Zapier
Device limits Per license, with a product default; buyers free seats on their own device page Policies with device activations; also floating, metered and user-locked licenses
Offline checks Signed sgt1 token, Ed25519, verified in your app Signed license files and machine files; offline licenses on every tier
Downloads and updates Upload releases; buyers download from an order page; update endpoint Distribution API on Std and Ent tiers only, with OCI, npm, RubyGems, PyPI, Tauri and binary engines
API Lemon Squeezy-shaped License API, management API, import API JSON:API-style REST API over every resource
Migration path CSV or JSON import, Lemon Squeezy and Dodo Payments importers Export your data through Keygen’s API, then import the file into Clavem

Fees on 100 sales of $49

Take 100 sales a month at $49, which is $4,900. Stripe’s standard US card rate is 2.9% plus 30 cents (as of November 2026), so Stripe takes $172.10 whichever licensing tool you pick. Add the licensing plan:

  • Clavem Indie: $29, total $201.10.
  • Keygen Std 1: $99, total $271.10.

Neither tool takes a share of the sale, and neither handles tax. If you need a merchant of record, that is a separate decision covered under Stripe alone.

What each tool counts

The two prices measure different things, and that decides which is cheaper for you.

Keygen counts active licensed users: a unique end user with an API action (a validation, an activation, an offline check-in) in the last 90 days. Clavem counts licenses that are neither expired nor disabled, whether or not anyone has used them yet.

Say you have sold 1,000 keys and 300 customers open the app in a given quarter. Keygen counts about 300 users and the free tier no longer fits, but a 1,000-user plan has room to spare. Clavem counts 1,000 licenses and you are at the top of the Indie plan. For an app with many dormant keys, Keygen’s meter can be kinder. For an app that most customers open every month, the gap narrows.

Keygen’s free Dev tier is a hard limit: it answers with a 402 when you pass it. Paid Keygen tiers have soft limits. On Clavem, hitting your plan limit never blocks validation: it only pauses creating licenses by hand and importing.

Same task, two APIs

Validating a key from your app looks like this on Keygen, taken from its documentation:

curl -X POST https://api.keygen.sh/v1/accounts/<account>/licenses/actions/validate-key \
  -H "Content-Type: application/vnd.api+json" \
  -H "Accept: application/vnd.api+json" \
  -d '{"meta": {"key": "C1B6DE-39A6E3-DE1529-8559A0-4AF593-V3", "scope": {"fingerprint": "4d:Eq:UV:D3:XZ:tL:WN:Bz:mA:Eg:E6:Mk:YX:dK:NC"}}}'

On Clavem the same check is a form post, shown here with the public demo key:

curl https://clavem.io/v1/licenses/validate \
  -d license_key=S1GNE-TDEM0-7K4QX-9WZ2P-H5RB8
{
  "valid": true,
  "error": null,
  "license_key": { "id": 1, "status": "active", "activation_limit": 3, "activation_usage": 1, "expires_at": null },
  "meta": { "product_name": "Inkwell", "customer_email": "ada@example.com" },
  "token": "sgt1.eyJ2IjoxLCJsaWQiOjE…"
}

Fields are trimmed for space. Keygen’s response is a JSON:API document with meta and data; Clavem’s has valid at the top level and a signed token your app can check without a connection. See offline verification.

When Keygen is the better choice

  • You need floating or concurrent licenses, metered usage, or entitlements. Keygen lists them on every tier. Clavem does not offer floating or usage-based licenses today.
  • You want to run the license server yourself. Keygen publishes a free community edition and sells an enterprise edition for self-hosting.
  • You distribute packages, not just installers. Keygen’s distribution engines cover container images and package registries.
  • You need SAML single sign-on or a 99.99% uptime SLA. Keygen lists both on its Ent tiers.
  • Your licensing is separate from how you take payments. Keygen is neutral about the payment provider, while Clavem reads Stripe only.

When Clavem is the better choice

  • You sell through Stripe Checkout, Payment Links or subscriptions and want the key created without writing a webhook handler. Clavem registers the webhook, handles refunds and subscription renewals, and gives each buyer an order page.
  • Your app already calls the Lemon Squeezy License API. Clavem answers on the same paths and fields, so that move is a hostname change.
  • You want one flat price in the $29 range for the first thousand customers.
  • Per-device keys with a seat limit cover your model.

Moving from Keygen to Clavem

  1. Export your licenses and machines through Keygen’s API into a CSV or JSON file with key, email, an activation limit, an expiry and the devices already activated.
  2. Create a product in Clavem and import the file. Each key is kept as written; the import is safe to run twice. See importing licenses.
  3. Change the validation call in your app to the form above, and ship the update.
  4. Keep Keygen running until most customers have updated, then close it.

Two checks before you import. Clavem matches keys without regard to capitals, so two Keygen keys that differ only in capitals would collide. And devices only carry over if the file lists them: put the id your app stored for each machine in instance_id, so a validate call that sends it succeeds straight away. After the move, new activations can send a fingerprint, which should be a hash rather than a raw hardware id. Longer reading: moving from Keygen.

Questions

Is Keygen cheaper than Clavem?

Not at the entry level. As of November 2026 Keygen's paid plans start at $99 a month for 1,000 active licensed users, against $29 a month for 1,000 active licenses on Clavem. Keygen has a free tier for 100 users, and it counts only users active in the last 90 days, so a large dormant customer base can cost less there.

Does Keygen work with Stripe?

Yes, but you connect them yourself. Keygen's Stripe page describes wiring Stripe to Keygen over webhooks and points to an example integration, and Keygen also supports a no-code route through Zapier. Clavem registers its own Stripe webhook and issues the key without code on your side.

Can I move from Keygen to Clavem without changing my app?

No. Keygen's API uses a different URL, request body and response format. Your app needs a small change to call Clavem's activate and validate endpoints, and your existing keys can be imported so customers keep the key they have.

Sources

  1. Keygen pricing page and feature table (checked November 2026)
  2. Keygen plans API, the data behind the pricing page (checked November 2026)
  3. Keygen documentation, offline licenses (checked November 2026)
  4. Keygen documentation, licenses API and validate by key (checked November 2026)
  5. Keygen and Stripe integration page (checked November 2026)
  6. Stripe pricing page, card rate (checked November 2026)