Clavem

Usage-based pricing

Usage-based pricing charges customers according to how much they use a product, such as API calls, exports or processed minutes, instead of a flat price per period.

How it works

You choose a unit that tracks the value the customer gets and the cost you carry: an API call, an export, a gigabyte processed, a minute of audio. Then you choose a shape.

Shape How the bill is calculated
Pay as you go Units x price, billed after use
Included allowance plus overage A base fee covers a quota, extra units cost more
Graduated tiers Each block of units has its own price
Prepaid credits The customer buys a balance, and use draws it down

Billing happens after the fact, so a counter has to exist somewhere you trust. How to count and enforce is covered in metered licensing; this page is about the price.

A worked comparison

An example unit price of $0.05 per export against a flat $20 plan:

Exports a month Usage price Flat $20 plan
100 $5.00 $20.00
400 $20.00 $20.00
2,000 $100.00 $20.00

Below 400 exports the customer pays less on usage, above it less on the flat plan. For you, the flat plan carries the cost risk of heavy users, and usage pricing makes your income swing with their activity. A common compromise is a base fee that includes an allowance, so the bill has a floor.

Predictability matters to buyers. Without a cap or an estimate in the app, a surprise invoice is the main reason customers dislike usage pricing.

Usage-based pricing versus a subscription

A subscription sells access for a period, whatever the use. Usage pricing sells the use. Many products mix them: a monthly fee for the license, and usage on top for the costly feature. A subscription license can carry the base fee.

On the Stripe side, its documentation describes usage-based billing built on Billing Meters, where you record usage and Stripe bills the customer. As of November 2026 the same documentation recommends Metronome, now part of Stripe, as the starting point for new usage-based integrations, and keeps the Meters API for existing ones. Check Stripe’s current pages before you choose.

How Clavem handles it

Clavem does not meter usage and does not bill by usage. Its own price is a flat monthly fee based on active licenses. Validation calls, activations and downloads are never counted toward that bill, so you cannot use them as a usage counter.

If your product has usage pricing, the counting lives in your own backend, which also sends the totals to Stripe. The license key is still useful as the customer identity: your server can look up usage by the key or by the license id in the signed token. Clavem decides whether the key is valid, and your system decides how much it has consumed. See pricing a desktop app for how to pick a model.

Questions

What is the difference between usage-based pricing and metered licensing?

Usage-based pricing is how you charge. Metered licensing is how you limit or count what a license may do. A flat plan with a monthly quota is metered but not usage-priced.

Does usage-based pricing suit a desktop app?

It suits features that cost you money per use, such as hosted processing or an AI model call. It suits a local feature much less, because the cost to you does not grow with use.

Sources

  1. Stripe Docs, Basic usage-based billing (checked November 2026)