Five ways to charge for a new major version
A major version is the one that changes the first number in a version such as 3.0.0, usually with changes that break compatibility or add a lot. The question is what owners of version 2 pay for it.
| Model | Existing customer pays | What you earn | Fits |
|---|---|---|---|
| Free updates forever | Nothing | Only new sales fund development | Small tools with low maintenance |
| Free inside a major, discounted upgrade | 25% to 50% off the full price | A pulse of revenue at each release | Desktop apps with real major releases |
| Update window | Nothing for N months after purchase, then renew | Rolling renewals | Plugins and tools with steady updates |
| Subscription | A recurring fee | Steady revenue | Apps with ongoing cost per user |
| Full price for the new major | The new-customer price | The most per upgrader, usually the fewest upgraders | A rewrite that is effectively a new product |
The discounted upgrade is the usual middle path, and the rest of this article works through it. For the subscription trade-offs, see one-time purchase vs subscription.
Discount math with 2,000 existing customers
Assume 2,000 people own version 2 and version 3 costs $79 for new customers. These tables are arithmetic on assumed take rates, not predictions.
Gross upgrade revenue by price and the share of owners who upgrade:
| Upgrade price (discount) | 15% upgrade | 25% upgrade | 35% upgrade |
|---|---|---|---|
| $59 (25% off) | $17,700 | $29,500 | $41,300 |
| $39.50 (50% off) | $11,850 | $19,750 | $27,650 |
| $29 (63% off) | $8,700 | $14,500 | $20,300 |
Read the table by columns for a fixed take rate, then ask how much the discount has to lift it. Compared with full price, a 50% discount needs twice the upgrade rate to earn the same, a 25% discount needs 1.34 times, and a 63% discount needs 2.72 times. If you expect 15% of owners to pay $79, a $39.50 upgrade must reach 30% to match it. Discounts also pass more of each sale to Stripe’s fixed fee: $39.50 costs $1.45 in fees, which is 3.7%, against 3.3% at $79.
A deep discount is justified when upgraders are hard to reach, or when you want a large installed base on the new version because it is cheaper to support. Otherwise a 25% discount is a mild thank-you that keeps most of your revenue. Test with your own list. Send the offer to one segment first and compare.
Do not make people guess what they own
Whatever model you choose, write it where buyers see it before they pay: on the pricing page and in your terms. Three statements prevent most disputes:
- What is included. “Includes all updates to version 2.x.” Name the major version, not a time.
- What is not. “Version 3 and later are sold separately as upgrades.”
- How long you fix bugs in the old major. Pick a period you can keep, such as security fixes for 12 months after the next major ships. This is a promise, so only write what you will do.
This is general information, not legal advice. Have your terms reviewed, and see writing an EULA for the usual sections.
A short grace window is kind. Customers who bought version 2 a few weeks before version 3 shipped feel cheated if the upgrade is not free. A rule like “bought within 60 days before release: free upgrade” costs little and avoids refund requests. Each license carries its created_at date, so the rule is easy to apply.
One product per major version
This is where licensing meets pricing. There are two ways to set up the license side.
| Setup | Cut-off enforced by | Latest release per version | Weakness |
|---|---|---|---|
| Separate product per major version | The signing key: tokens from the version 2 product do not verify against version 3’s public key | Independent for each product | You manage several products |
| One product for all versions | Your app’s own rule | One list, one “latest” | A direct API call can still fetch any release |
With Clavem, every product has its own Ed25519 key pair and its own releases. A token signed for one product does not verify against another product’s public key, and the token carries pid, the product id, which your app should check. A version 3 app that expects version 3’s pid and public key rejects a version 2 license, even if someone copies the token.
There is a second reason that comes from how releases work. The docs say the latest release is the most recently published one, not the highest version number. If you publish a 2.9.1 security patch after 3.0.0, the patch becomes the latest of that product. On a single product, version 3 customers would then be offered 2.9.1. With one product per major, the 2.9.x patches go on the version 2 product and never touch version 3’s latest. The flip side is that you must remember to publish patches to both when both need them.
A single product can work as a courtesy gate. File platform labels are free text, so one could use macos-v3, but the label limits nothing for someone who calls the endpoint themselves. For a real cut-off, separate products.
On the plan side, Free allows one product and Indie five; Studio and Scale are unlimited. A new product for each major release uses one slot.
Selling the upgrade in Stripe
Create a Stripe price for the upgrade and map it to the version 3 product in Clavem. A mapping to a price wins over a mapping to its whole Stripe product, so one Stripe product can feed different Clavem products. A purchase creates a new license under version 3 and keeps the version 2 key as it was.
The harder question is how to give the discount only to owners. Options:
| Method | How it proves ownership | Effort |
|---|---|---|
| Promotion code restricted to a customer | You send each owner a code tied to their Stripe customer | A list and an email |
| Shared code with a redemption limit and expiry | It does not; anyone with the code can use it | One code, and expect leaks |
| Your server checks the key, then creates a Checkout Session | A lookup of the version 2 key through the management API | A small backend |
| An upgrade price on an unlisted page | It does not; it relies on the URL staying private | Almost none |
Stripe’s docs describe coupons as the discount (percent off or amount off, with a duration, a redemption limit and an end date) and promotion codes as customer-facing codes that point at one. A promotion code can be restricted to one customer, given its own redemption limit and an expiry, and limited to first-time customers or a minimum order amount. First-time restriction is the opposite of what an upgrade wants, but it is handy for a “new customers only” launch price. In Checkout, allow_promotion_codes=true shows a code field, and discounts[0][coupon] applies a coupon directly to a one-time payment.
For the server-side route, the management API finds a license by key or email, with GET /v1/admin/licenses?key=.... You check the product and status, then create the Checkout Session with the discount. Clavem has no hosted checkout, so this part is your code.
Free upgrades for recent buyers
For the 60-day window, you can issue version 3 licenses yourself with POST /v1/admin/licenses, giving the version 3 product_id, the buyer’s email and name, an activation limit, and expires_at left empty for a perpetual license. The response includes the new key and an order_url. The docs do not say the buyer is emailed, so send the link yourself. Manual licenses count toward the plan, and past the limit the call answers 402 plan_limit.
Doing this with Clavem
Products are cheap to add, releases are per product, and the license keeps its own created_at, so the date logic above is available. Clavem does not enforce an update window by itself and has no upgrade-discount feature. Discounts live in Stripe, and the choice of which product a purchase maps to is made by the price you sell. See Releases and downloads for the latest-release rules and the API reference for the endpoints.
Questions
How much should an upgrade cost compared with a new license?
There is no standard. A reasonable range to test is 25% to 50% off the new-customer price. A discount pays only if it raises the number of upgraders enough. At 50% off you need twice as many upgraders as you would get at full price just to break even.
Can the same license product cover version 2 and version 3?
Technically yes, but the cut-off then lives in your app and not on the server. A separate product per major version gives each version its own key pair and release list, so a version 2 license cannot be passed off as a version 3 license.
How do I send existing customers an upgrade discount in Stripe?
Create a coupon, then a promotion code restricted to one customer, with a redemption limit of one and an expiry date. Stripe's docs list customer, redemption limits and expiry as the available restrictions.