Usage-Based Billing Platforms in 2026: Why Your Pricing Should Belong to You

For a usage-based product, billing isn't the last step anymore. Who can use what, how much, at what cost, and under which deal: those decisions are the product. They decide whether a heavy customer is profitable, whether a new model can launch, whether the contract sales just signed is honored on Monday.

Somewhere along the way, our industry decided those decisions should live in someone else's system, and that the system should take a cut of everything you bill. We think that's backwards, and we built Limitr to fix it.

This post is two things. First, what we think went wrong and what we believe instead. Second, an honest guide to the platforms you're probably comparing, written to help you choose well even if you don't choose us. If you're here for the comparison, skip to the guide.

What went wrong

Billing became a toll. Many billing platforms price on a share of what you bill. That sounds harmless until you do the math at three times your size: your growth becomes their revenue, and the fee rises with your success rather than with anything they do for you.

Your pricing moved into their system. Plans, prices, and contract terms are configured inside the vendor's product. Your app still needs its own code to enforce limits and gate features, so now there are two sources of truth, and keeping them in step is your job.

Leaving was made hard on purpose. When your pricing logic, customer state, and contract history live in a vendor's model, switching means rebuilding all of it. The lock-in is the business model.

So teams keep building it themselves. Even with a dozen platforms available, many teams still write pricing and entitlements in-house, because it's the only way to keep control. They pay for it in engineering time on every plan, every price change, and every custom deal, and they rarely know what each customer actually costs to serve.

What we believe

The engine that makes these decisions should be yours. It should run in your stack, read like code you could have written, and bend to your business: your units, your costs, your rules, your exceptions. Open source, so you can read it, extend it, and never depend on our roadmap.

The platform around it should keep you in sync, not hold you in place. A hosted platform earns its keep by keeping every service, every team, and every customer on the same policy, live, without a release. Not by being the only place your pricing exists.

You should know what every customer costs you. Not just what you charge. Margin per account, per feature, and per vendor should be visible as usage happens, not reconstructed after the invoice.

A contract should be enforced as written. If sales signs a spend cap, a ramp, or a custom rate, the product should honor it on the customer's next call, not just the invoice at month's end.

Changing pricing should be safe. The people who run pricing, in finance, revenue ops, and product, should be able to see what a change does to revenue and margin before it ships, and roll it back if they're wrong.

We shouldn't earn more just because you do. Billing infrastructure should be priced on what it does, not on a percentage of your revenue.

That's what Limitr is: usage-based billing and entitlements that you own. An open-source engine inside your product decides, prices, and meters every unit of usage from a policy you keep. Limitr Cloud keeps every engine in sync with your team, enforces contracts, bills, and shows live margin, and Limitr Analyst lets the people who run pricing test a change before it ships. We never take a share of your revenue, and if you leave Limitr Cloud, your pricing keeps running on the open-source engine.

Choosing a usage-based billing platform in 2026

We believe all of that, and you should still choose with clear eyes. Here's the market as it stands, checked November 3, 2026. Platforms change quickly, so treat the specifics as a starting point and confirm them in a demo.

The short answer

If your pricing will keep changing and you want to keep control of it as you grow, own the engine. That's Limitr: metering, limits, entitlements, credits, contracts, invoicing and collection, and live margin, from one policy you own, with an analyst to test every change before it ships, and never a share of your revenue. It covers what most usage-based businesses need, and it fits best when you sell to businesses, negotiate deals, and carry real usage costs like AI tokens or compute.

Look elsewhere when one need outweighs the rest:

• One vendor for payments, tax, and revenue recognition at very high volume: Stripe with Metronome.
• Invoicing accuracy across complex, high-volume contracts is the whole problem: Orb.
• Subscription management and dunning come first: Chargebee.
• Finance is standardized on an enterprise quote-to-cash suite: Zuora, or m3ter inside Salesforce.
• Your billing system must be self-hosted end to end: Lago, Flexprice, or OpenMeter.
• You only need entitlement checks on top of billing you already have: Stigg or Schematic.
• You only need to see what AI usage costs you: Paid or Amberflo.

Three paths

Build it in-house. Full control, paid for in engineering time on every change. A coding agent makes the first version fast; every change after it is the lasting work.

Buy a platform. Speed and a mature billing system, with your pricing in their model, enforcement in your product still yours to build, and often a share of what you bill.

Own the engine. Run the pricing and entitlement logic inside your own stack from a policy you keep, managed from a hosted platform that keeps every copy in sync. The control of building, without building and maintaining the engine.

The market consolidated

Much of this category changed hands between 2025 and 2026. That matters to a buyer: a billing platform owned by a payments company or a CRM tends to follow that parent's roadmap.

Platform	Now part of	When
Metronome	Stripe	Closed January 2026
Orb	Adyen	Closed July 2026
m3ter	Salesforce	Closed July 2026
OpenMeter	Kong (now Konnect Metering & Billing)	September 2025
Zuora	Taken private by Silver Lake and GIC	February 2025

Independent today: Chargebee, Lago, Flexprice, Stigg, Schematic, Paid, Amberflo, and Limitr.

Five questions to answer before you choose

Feature lists blur together. These questions separate the options.

1. Who owns the decisions? When a customer hits a limit or a deal changes, does the logic live in your product, or in a vendor's system that your product asks or hears from?
2. How does the cost grow? A share of billings, a count of events, or a fee tied to what the platform actually governs? Run the numbers at three times your current size.
3. Where do contracts live? Are negotiated terms enforced in your product, or only applied when the invoice is produced?
4. Who iterates on pricing, and how safely? Can finance, revenue ops, and product test a change against real customers and costs before it ships, or does every change go through engineering and hope?
5. What happens if you leave? Do you keep your pricing logic, or rebuild it?

The platforms

Billing and invoicing platforms

Stripe Billing and Metronome. Stripe now calls Metronome its primary usage-based billing platform: Metronome meters, rates, and handles enterprise contracts (commits, credits, drawdowns, amendments), and Stripe adds payments, tax, and revenue recognition. Its customers include OpenAI, Anthropic, and NVIDIA, so scale is proven. Usage is sent to the hosted service, and threshold alerts reach your app by webhook, so enforcement in the product is yours to build. Priced as a percentage of billing volume plus events. Choose it when you want metering, invoicing, and payments from one provider at very high volume.

Orb. "The revenue design platform," now owned by Adyen. Orb stores raw usage and computes billing from it, which makes re-rating and late data easy, handles enterprise contracts, reads contract PDFs into billing terms, and can replay past usage under proposed prices to show the revenue impact. It's a hosted billing system; limits in your product are yours. Priced on billing volume and events. Choose it when invoicing accuracy across complex, high-volume contracts is the core problem.

Chargebee. A mature subscription and recurring billing platform, a Gartner Magic Quadrant leader for recurring billing, with usage ingestion, credits, CPQ, revenue recognition, and an MCP server. Its ledger API can place a hold on credits before an action, which your app calls. Priced as a share of billings. Choose it when subscription management, dunning, and finance workflows matter as much as usage.

Lago. Open-source (AGPLv3) metering and usage-based billing that you can self-host or use as a cloud service, with entitlements, wallets, commitments, revenue forecasting, and an agent SDK that bills LLM cost plus a markup. Customers include Mistral AI and Groq. Choose it when you want an open-source billing system you can run yourself.

Flexprice. Open-source (AGPLv3) usage billing aimed at AI and API companies, with cost sheets for revenue and cost analytics, credits, and on-premises deployment. Early-stage. Priced as a platform fee plus a share of billing volume. Choose it when you want open-source billing with cost tracking and can work with a young vendor.

OpenMeter (Kong). Open-source (Apache 2.0) metering, now sold as Kong Konnect Metering & Billing. Kong's gateway can enforce entitlements on API and LLM traffic before it reaches your service. Choose it when you already run Kong and want metering and limits at the gateway.

Where Limitr differs. Limitr meters, invoices, and collects too. The difference is where your pricing lives and runs: in an engine you own, enforcing limits and contract terms in your product in the same step that meters them, rather than in a vendor's system your app reports to. And it's never priced on what you bill.

Enterprise quote-to-cash

Zuora. The deepest enterprise quote-to-cash suite here: CPQ, flexible commitments, revenue recognition, and a growing set of AI agents, including a pricing simulator. Entitlements are tracked in its catalog; enforcement happens in your systems. Contract-priced. Choose it when you're a large enterprise standardizing finance operations end to end.

m3ter (Salesforce). Usage metering and rating that sits in front of your CRM and ERP, now going into Salesforce's Agentforce Revenue Management. Contract-priced. Choose it when Salesforce is the center of your revenue process.

Where Limitr differs. Limitr handles contracts with phases, ramps, renewals, fees, commitments, and recognition schedules, and enforces their terms in your product on the customer's next call. It's self-serve on its Scale plan, so a contract doesn't wait on an implementation project. Keep your ERP and CPQ for what they do best.

Entitlement and credit platforms

Stigg. "The usage runtime for AI products": plans, entitlements, credits, and budgets, checked through a cached sidecar next to your app, with integrations into billing, CRM, and CPQ tools. Contract management is in beta. Flat platform tiers. Choose it when you need entitlements and credits in your product quickly and already have billing.

Schematic. Credit-based pricing, plans, and entitlements with a strong developer experience and billing components for your UI. By default its SDKs check flags against its API with a short local cache; an opt-in mode evaluates flag and credit checks locally, while usage is processed on its servers. Its own billing product is in early access. Flat platform tiers. Choose it when you want credits and entitlements live fast.

Where Limitr differs. Limitr covers plans, entitlements, and credits too, from the same policy that prices and bills them, so there's no second system to keep in step with your billing. The whole policy runs in your process, including prices, costs, and contract terms, and usage is counted in the same step as the decision.

Cost and margin for AI

Paid. Monetization and cost tracking for AI agents: cost per agent and workflow, margin, outcome-based billing, and value reports for your customers. Your app enforces access. Choose it when you sell AI agents and proving value and margin per outcome is the main need.

Amberflo. AI cost attribution and billing, with an AI gateway that runs in your VPC and customer-level cost and margin. Choose it when you need cost allocation across clouds and models alongside billing.

Where Limitr differs. Limitr prices every call at what it costs you and what you charge, so margin per customer, feature, and vendor comes from the same step that enforces the limit and feeds the invoice, not from a separate system.

Where Limitr fits

Limitr fits any usage-based business that expects its pricing to keep changing. It fits best for sales-led companies whose usage carries real cost, such as AI tokens, compute, and vendor APIs: every deal is different, margin per account matters, and pricing has to keep changing without breaking the customers you already have.

• An engine you own. Open source and running inside your application. It decides what each customer may use, prices it at what it costs you and what you charge, and counts it, in one step. Plans, limits, credits, contracts, vendor costs, and overhead live in one policy you keep, and you can override built-in rules and add your own logic.
• A platform that keeps every engine in sync. Limitr Cloud is the live, hosted way to run those engines: edit and publish without a release, store customers and usage, enforce contracts on the next call, invoice and collect, and see margin by customer, feature, and vendor. It's event-driven and stays out of your request path.
• An analyst for the people who run pricing. Limitr Analyst works on your real policy, customers, and usage, so finance, revenue ops, and product can find where margin leaks, simulate a change, and forecast it before anything ships.
• Never a share of your revenue, and yours if you leave.

When to choose something else

• You need tax, revenue recognition, dunning, and payments in one vendor today: Stripe with Metronome, Chargebee, or Zuora. Limitr bills through Stripe or your own rails and can sit alongside them.
• Your pricing is simple and stable, and you only need to invoice it: a billing platform is less to adopt.
• You only need feature flags: a feature flag tool is enough.

If what we believe matters to you, we'd like to build with you. Start free, or book a demo.

Frequently asked questions

What's the best usage-based billing platform for AI companies? If you sell to businesses and your pricing keeps changing, start with Limitr: it meters, limits, prices, and bills AI usage at what it costs you and what you charge, enforces negotiated deals in the product, and never takes a share of your revenue. If one need dominates, look at Stripe with Metronome or Orb for invoicing at very high volume, Paid or Amberflo for AI cost visibility alone, or Stigg or Schematic for entitlement checks on top of existing billing.

Orb or Metronome? Both are mature, hosted usage billing platforms with strong enterprise contract support. Metronome comes with Stripe's payments, tax, and revenue recognition; Orb, now owned by Adyen, is known for computing billing from raw usage and for replaying history under proposed prices. Neither enforces limits inside your product.

Stigg or Schematic? Both manage plans, entitlements, and credits. Stigg checks them through a cached sidecar and integrates with existing billing, CRM, and CPQ tools; Schematic leads with credit-based pricing and developer experience, and is adding its own billing. Both are closed source with flat platform tiers.

Is there an open-source usage billing platform? Yes. Lago and Flexprice (AGPLv3) and OpenMeter (Apache 2.0) are open-source billing and metering systems. The Limitr engine (Apache 2.0) is open source too; it's the part that runs in your product and decides, prices, and counts usage.

Can a billing platform enforce limits in real time? Most report usage and alert by webhook, so your product enforces limits with code you maintain. Some check entitlements through a cached sidecar or SDK, and Kong enforces at its gateway. Limitr enforces in the same in-process step that prices and counts the usage.

Is Limitr a billing platform? Yes. Limitr meters usage, prices it, invoices it, and collects through Stripe or your own payment rails, with credits, refunds, contracts, and live margin. The difference is where the decisions live: in an open-source engine inside your product, configured by a policy you own, rather than in a vendor's system. And it's never priced on a share of what you bill.

Do these platforms take a share of revenue? Several price on billing volume, including Stripe, Metronome, Orb, Chargebee, and Flexprice. Stigg and Schematic charge flat platform tiers, Zuora and m3ter are contract-priced, and Lago and OpenMeter can be self-hosted. Limitr Cloud is priced on the customers and calls it governs, never on what you bill.

Sources

Vendor facts are from each company's own site and documentation where possible, checked November 2026. Stripe on Metronome · Stripe completes Metronome acquisition · Metronome alerts · Stripe pricing · Orb overview · Orb simulations · Adyen closes Orb · Chargebee ledger API · Lago on GitHub · Flexprice pricing · OpenMeter joins Kong · Kong entitlement enforcement · Zuora AI Monetization Suite · Zuora goes private · Salesforce and m3ter · Stigg sidecar · Stigg pricing · Schematic in your stack · Paid funding · Amberflo on AWS Marketplace