How it works
The customer pays once for a perpetual license, and the price includes a period of maintenance, for example 12 months. After that period they can renew maintenance for a smaller fee. What it covers is your choice: new versions, bug fixes, support, or all three.
The line that matters is a date, not a version number. Every version released while maintenance is active belongs to the customer for good. Versions released afterwards need a renewal.
A worked example
An illustrative case: a $199 license includes 12 months of maintenance, and renewal costs $49 a year.
| Date | Event |
|---|---|
| 1 March 2026 | Customer buys. Maintenance runs to 1 March 2027. |
| 10 December 2026 | Version 4.2 is released. Covered, so it is theirs forever. |
| 1 March 2027 | Maintenance ends. The app keeps working. |
| 20 May 2027 | Version 4.3 is released. Not covered unless they renew. |
| 2 June 2027 | They renew for $49. Under a “starts today” rule the new period runs to 2 June 2028. |
You must also decide whether a late renewal starts today or continues from the old date, and whether it covers versions released during the lapse, such as 4.3. Both choices are fair; say which one you use in your terms.
Maintenance versus a subscription license
In a subscription license, the license itself ends when payment stops. With maintenance, the license is perpetual and only the stream of new versions ends. The difference matters in code: an app that treats every expired license as unusable breaks the promise.
How Clavem handles it
Clavem has no separate “updates until” date. The license’s validity is its only date: expires_at, or the end of a Stripe subscription. You can still build maintenance from documented pieces, with your app doing the enforcement.
- Set
expires_atto the maintenance end. Renewal is a management API call that moves it forward, which also revives an expired license:
curl -X PATCH https://clavem.io/v1/admin/licenses/412 \
-H "Authorization: Bearer sk_clavem_…" \
-H "Content-Type: application/json" \
-d '{ "expires_at": "2028-03-01T00:00:00Z" }'
- An expired license answers
valid: false, statusexpired, with itsexpires_at. Your app can compare that date with the date its own build was released and keep running builds from before it. - The releases endpoint returns release notes and download links only for a license that is neither expired nor disabled. For any other key, or none, it still returns
versionandpublished_at, so your app can say “4.3 exists, renew to download it”. See Releases and downloads.
Clavem does not run this rule for you: it reports the dates, and your app decides what an expired license may still do.
Questions
What happens if a customer stops paying maintenance?
The software they own keeps working. They stop receiving new versions and support. Versions released before the maintenance ended stay theirs.
Is maintenance the same as a subscription?
No. A subscription pays for the right to use the software at all. Maintenance pays for new versions and support on software the customer already owns.