Usage-based pricing models explained
Pure usage, tiered, volume, and hybrid pricing — what each model means, when it fits, and what it demands from your billing system.
Free and open-source under AGPLv3 — self-host today, or talk to us about cloud.
June 3, 2026 · 6 min read · The GetPaidHQ team
Usage-based pricing ties what a customer pays to how much they use. It has become the default for infrastructure, API, and AI products, where a flat fee would either overcharge small customers or leave money on the table with large ones. But "usage-based" is an umbrella term covering several distinct models, and the one you pick shapes both your revenue and what your billing system has to do.
Why usage-based pricing took over
When cost scales with consumption, pricing should too. Usage-based pricing aligns what customers pay with the value they get, lowers the barrier to starting (you pay little when you use little), and lets revenue grow with a customer automatically — no renegotiation required. The trade-off is predictability: usage-based bills are harder for customers to forecast, which is part of why hybrid models are so common.
The main usage-based pricing models
- Pure usage: a flat rate per unit consumed — for example $0.01 per API call. Simple to explain, but revenue is fully variable.
- Tiered (graduated): the per-unit rate changes as usage crosses thresholds, and each tier is billed at its own rate — like income-tax brackets. The first 1,000 calls cost one rate, the next 9,000 a lower one.
- Volume: the entire usage is billed at the rate of the tier the customer lands in. Cross a threshold and *all* units get the cheaper rate, which rewards bigger commitments.
- Hybrid: a fixed base fee plus metered usage on top — a platform fee for predictability, with consumption charges for fairness.
Hybrid pricing: the most common in practice
Most successful usage-based companies are really hybrid. A fixed monthly platform fee gives the customer a predictable floor and the business a revenue base, while metered usage captures the upside as the account grows. A typical shape is "$99/month base + $0.01 per API call + a transaction percentage." Supporting that combination cleanly inside a single subscription is exactly what usage-based billing is for.
What usage-based pricing needs from your billing system
A pricing model is only as good as your ability to bill it accurately. Usage-based pricing depends on metered billing — capturing every billable event, aggregating it per customer and period, and turning the total into a clear invoice. Specifically, you need:
- Real-time event ingestion that records usage as it happens, reliably and idempotently.
- Aggregation that rolls events up per customer and billing period, applying tiers, volume rules, and included allowances.
- Transparent invoicing that shows customers exactly what they consumed, alongside any fixed charges.
- Proration and mid-cycle changes, so upgrades and downgrades are billed fairly.
Getting started
Choose the simplest model that matches how your product creates value, then make sure your billing system can meter it honestly. GetPaidHQ supports fixed, pure-usage, tiered, graduated, and hybrid pricing as first-class concepts — see usage-based billing for how the metering and invoicing fit together.
Billing for the rest of us.
GetPaidHQ is open-source, self-hostable billing on any processor. Run it free, or talk to us about managed Cloud.
Free and open-source under AGPLv3 — self-host today, or talk to us about cloud.