The gap
A seller who sells software through Stripe gets paid, and then has to do everything else by hand. Someone has to create a license key, email it, limit it to a number of devices, deliver the download, handle refunds and renewals and answer “I lost my key”. Stripe takes the payment and stops there.
Lemon Squeezy did that work for many small software sellers. Its migration guide says it no longer accepts new sign-ups, that transaction processing stops on 31 March 2027, and that migration tooling for Stripe Managed Payments opens on 2 December 2026. It recommends Managed Payments, Stripe’s merchant of record product, and its own comparison says Managed Payments does not deliver files, license keys or download links. Sellers are told to connect a separate solution or build one.
That is the opening Clavem fills: keys, downloads and update checks for software sold through the seller’s own Stripe account.
How the idea was chosen
The decision was recorded on 18 November 2026, after research on five tracks and three rounds of validation. The research looked at what small software businesses verifiably earn, what developer-tool buyers pay for, where cheap alternatives already crowd every slot, which marketplaces are worth building for and which deadlines force buyers to act. Each finding in the research notes is labeled as confirmed on the source page, self-reported or an estimate.
Twenty candidates were scored on how reliably people pay, how reachable they are, revenue potential, growth, differentiation, effort, margin and retention, with penalties for risks. Licensing and delivery for Stripe sellers scored 6.7, the highest. The next was an Atlassian Forge app at 5.5.
The closest competitors on paper lost for specific reasons, which are on record:
| Finalist | Why it lost |
|---|---|
| EU e-invoicing API | It scored well at first. Validation found an identical product live since August 2026, at least eight more vendors, free libraries with over a million monthly installs, and entry prices of EUR 7 to 19 |
| Heartbeat monitoring | Thirteen new entrants in 2026, none with revenue. A thread asking whether people would pay $29 got the reply “I wouldn’t” |
| AI-search visibility tracker | Strong willingness to pay, but it is a wrapper around model calls and competes with heavily funded companies |
| Atlassian Forge app | Needs a registered company and an unpredictable approval, and sits outside the chosen stack. Worth revisiting as a second product |
One lesson from the failed ideas shaped the choice. A product that is deterministic code around a public standard gets cloned within months. What survives needs a forced buyer, switching costs, or an operational trust requirement. Licensing has all three.
Six reasons it was chosen
- A buyer with a date. Lemon Squeezy’s deadline gives sellers a reason to act now.
- The gap outlives the migration. Every software seller who would have picked Lemon Squeezy now lands on Stripe without fulfilment.
- High switching costs. The validation call is compiled into shipped apps, so customers who integrate stay.
- Proven price points. The research notes found licensing tools for business buyers priced from $29 to $750 a month, as checked in November 2026.
- It suits the infrastructure. Validation runs at Cloudflare’s edge and files come from R2 with no egress fees, so the gross margin is high.
- It can be verified end to end in a Stripe sandbox.
What Clavem promises
The positioning is one sentence: license keys, downloads and updates for software you sell through Stripe, at a flat price with no cut of sales, and with keys that keep working whatever happens to Clavem.
That last clause shaped the design. Every license can be verified offline with a public key the seller holds, using an Ed25519-signed token, so a seller’s apps keep running if the service is unreachable. A seller can export every license at any time. The License API uses the same paths, fields and response shapes as the Lemon Squeezy License API, so an app moves by changing a hostname, and an importer brings existing keys and device activations across.
Clavem charges by active licenses, not by a share of sales: Free up to 50 active licenses, then $29, $79 and $199 a month. Validation calls, activations and downloads are not metered, and going over a limit never stops sales or customers’ validation.
What was left out on purpose
The first version leaves out team seats and roles, a Paddle connector, a Stripe App Marketplace listing, custom domains for buyer pages, floating licenses, usage metering and outbound webhooks. Each is noted with the trigger that would justify building it. Clavem is also not a merchant of record: it does not handle tax, and a seller who wants that uses a merchant of record or Stripe’s own product.
Technical choices
| Decision | Choice | Reason |
|---|---|---|
| Hosting | One Cloudflare Worker with static assets | Validation near the caller, one deploy unit |
| Database | Postgres in Frankfurt, through Cloudflare Hyperdrive | Real transactions for device limits |
| Files | Cloudflare R2 | No egress fees on downloads |
| Signed keys | Ed25519 per product, private key encrypted at rest | Apps can verify offline |
| Expiry | Evaluated when a license is read | No scheduled job to fail |
| Seller’s Stripe connection | A restricted key pasted by the seller | Works without Stripe platform approval |
The name
The product was first built under another name. Every common ending for that name was taken, so the founder chose a single word that was free at the registrar on 19 November 2026: Clavem, the Latin accusative of clavis, “key”, with the domain clavem.io. Technical identifiers from the earlier name were kept so that existing integrations keep working: the signed-token prefix, the demo key and API keys already issued.
Risks stated at the start
The decision record lists them plainly:
- A small first wave. The estimate is a few hundred to about 1,500 sellers who depend on Lemon Squeezy keys.
- A live rival with similar pricing, a CSV importer and a head start of weeks.
- A platform move. Stripe could ship native keys, or Lemon Squeezy could name an official partner.
- Trust. An outage would lock customers out of sellers’ apps. Offline-verifiable keys and fail-open guidance reduce that risk and do not remove it.
- The name. “Clavem” is a common word.
The assumptions behind the plan are testable: that sellers moving to Stripe will pay for fulfilment instead of building it, that the Lemon Squeezy-shaped endpoint and key import matter, that sellers will trust a new vendor with validation and that demand continues after March 2027. Each has a threshold that would change the plan.
What is verified and what is not
Verified on 19 November 2026: 137 integration tests against Postgres, 15 of 15 seller-flow checks and 8 of 8 billing checks against production with real Stripe sandbox webhooks, and 27 pages checked at three widths. Clavem’s own billing has run on a live Stripe account since that day. A real card payment end to end has not been checked, because it needs a real purchase.
Open items, with their reasons: the seller-side tax and VAT decision for Clavem’s own subscriptions, a legal review of the Terms and Privacy pages, a trademark check on the name, an external uptime monitor with alert emails, and a run of the importer against a live Lemon Squeezy store, which is not possible while new accounts there stay closed. The first sellers to import get hands-on help.
Doing this with Clavem
If you sell software through Stripe and need keys, devices, downloads and updates without handing over a cut of sales, start on the pricing page or read how the Lemon Squeezy migration works. If a feature in the left-out list matters to you, say so through the contact form, because that is how items on that list get built.
Questions
Who makes Clavem?
Clavem is made in Switzerland by one founder, Gian Hagmann. Support runs through the contact form and support@clavem.io.
Is Clavem a merchant of record?
No. Clavem does not handle tax or take the payment. The seller keeps their own Stripe account, and Clavem charges a flat monthly price with no share of sales.
What has not been tested yet?
Clavem's own billing has not yet taken a real card payment end to end.