7 Best Usage-Based Billing Platforms for SaaS in 2026: Deep Comparison

Cristian Curteanu
34 min read
7 Best Usage-Based Billing Platforms for SaaS in 2026: Deep Comparison

Photo by Maximus Beaumont on Unsplash

Table of Contents

What Is Usage-Based Billing Software?

Usage-based billing software is infrastructure that tracks how much of a product each customer consumes, applies pricing logic — linear, tiered, volume, matrix, or committed-spend — and generates invoices based on actual consumption rather than a fixed fee. It sits between your event sources (APIs, infrastructure metrics, application telemetry) and your payment processor, handling the metering, aggregation, pricing calculation, and invoice generation in between.


Key Takeaways

  • The independent metering layer has been bought. OpenMeter went to Kong, Metronome to Stripe, and Orb is going to Adyen, all within about nine months. Ask who owns a vendor before you ask what it costs.
  • Data ownership splits the market in two. Self-hosted deployments (the ABAXUS open core, and Lago’s open-source edition) keep usage data inside your infrastructure. Every vendor-hosted option, including managed clouds from ABAXUS and Lago, stores it on the vendor’s servers.
  • Percentage-of-revenue pricing compounds. A platform charging 0.5% of revenue costs $50,000/year at $10M ARR and $150,000/year at $30M ARR, independent of what it costs the vendor to process your events.
  • Rate limits are a design input. Stripe documents 1,000 meter-event calls per second per account in live mode, and a v2 event stream of up to 10,000 events per second by default. Check the limit of any hosted API against your peak, not your average.
  • Stripe Billing began as payments. Its Meters API is now joined by Metronome for advanced usage-based pricing, but a payments-first architecture is still the starting point.
  • The right choice changes as you scale. A platform that works well at $1M ARR may cost too much, process too slowly, or hold data in the wrong place at $20M ARR. Evaluate against your 3-year trajectory, not today’s volume.

The Case for Getting This Decision Right

Usage-based pricing is now a standard option for B2B SaaS. OpenView’s research tracked the share of SaaS companies with a usage-based component rising through 2022 and 2023, though published figures vary by report (45% in the State of Usage-Based Pricing research, 61% in a TechCrunch summary of OpenView’s 2022 survey), so treat any single number as directional. See OpenView’s 2023 pricing data for the primary source.

The billing infrastructure underneath that model is not a commodity decision. A misconfigured metering pipeline produces invoices customers can’t verify, support teams can’t explain, and finance can’t audit. And every hosted metering API has a throughput ceiling you should know before you commit. Stripe, for example, documents 1,000 meter-event calls per second per account in live mode, and up to 10,000 events per second on the v2 event stream, with higher volumes handled through sales.

The platform you choose determines whether you can explain every charge, whether your usage data stays in your infrastructure, and whether your billing fees stay flat as revenue grows. These are architectural decisions with a 5-year cost that is invisible at selection time.


What Changed: The Independent Metering Layer Was Acquired

Between September 2025 and July 2026, three of the best-known independent usage-billing vendors changed hands. If you evaluated this category a year ago, your shortlist is out of date.

VendorNew ownerStatus
OpenMeterKongAnnounced Sep 3, 2025. Being folded into Kong Konnect as Metering & Billing; the open-source project continues.
MetronomeStripeCompleted Jan 14, 2026. Runs standalone and inside Stripe Billing for advanced usage-based pricing.
OrbAdyenAnnounced Jun 11, 2026 for $335M in cash, with close guided for around July 1, 2026. I could not find a completion notice, so confirm the closing status before relying on it.

What this means for a buyer: the meter sits upstream of the money, so it keeps getting acquired by whoever owns the payments or API layer. None of these deals is a verdict on product quality. The practical risks are roadmap drift, pricing changes after integration, and a vendor whose priorities now include selling you its parent company’s payments product. Lago has published its own take on the Orb deal; read it with the vendor’s incentive in mind.

The durable defence is owning the data contract (your event schema, your idempotency keys, your ledger) so that changing engines is an adapter swap, not a migration. That is the case for self-hosted, open options, and it is the position ABAXUS is built around.


How to Choose a Usage-Based Billing Platform

Usage-based billing platforms are not interchangeable. The right choice depends on where your usage data needs to live, how complex your pricing logic is, how much engineering you want to own, and what event volume you’re planning for. Before evaluating any platform, answer seven questions:

  1. Data residency — does your usage data need to stay in your own infrastructure, or is cloud-hosted acceptable? For healthtech SaaS, any usage event that carries patient context triggers HIPAA obligations the moment it crosses a third-party API.
  2. Pricing model complexity — do you need linear rates only, or tiered, volume, committed-spend, ramp schedules, and custom enterprise structures?
  3. Event volume — how many usage events per month today, and at 3× growth? Cloud platforms have shared-infrastructure rate limits that cannot be raised on request.
  4. Engineering capacity — how much does your team want to own, configure, and maintain? Self-hosted platforms shift operational overhead to your team.
  5. Transaction volume economics — at what revenue level does percentage-of-revenue pricing become a significant line item? Run the math at your 3-year ARR projection.
  6. Integration requirements — what does the platform need to connect to? CRM, ERP, Stripe, accounting — the integration ecosystem varies significantly.
  7. Migration path — how easily can you export your data if you need to switch? Your data portability risk is proportional to the maturity and data policies of the vendor. After the 2025–2026 acquisitions, add: who owns this vendor in 12 months?

At a Glance

ABAXUSLagoOrbChargebeeMetronomeStiggStripe Billing
DeploymentSelf-hosted Core, or ABAXUS Cloud (hosted by us)Self-hosted or cloudCloud onlyCloud onlyCloud onlyCloud onlyCloud only
Open sourceOpen core (license to be announced)Yes (AGPL-3.0)NoNoNoNoNo
Pricing modelCore free; Cloud from $12K/yrFree OSS; cloud and Premium by quoteNot fully publicPlan fee + % overage (verify)Starter rates plus custom enterpriseTiered plans0.7% of billing volume (pay as you go)
Transaction feesNoneNone (self-hosted)VariesOverage % above plan capNegotiatedStripe pass-through0.7% pay as you go
Data ownershipCore: in your infra. Cloud: ABAXUS-hostedSelf-hosted: in your infraVendor’s infraVendor’s infraVendor’s infraVendor’s infraVendor’s infra
Pricing logicTiered, volume, hybrid, customTiered, volume, committedTiered, volume, matrix, customSubscription-first + usageComplex enterprise contractsFeature-based + usageLinear, tiered, volume
Event throughputYour infra ceiling (Core)Your infra ceilingHigh (managed)ModerateVery high (managed)Moderate1,000 calls/s v1; 10,000 events/s v2 stream
Best forOwning the data contract, modular self-hosting, no per-transaction feesOpen source with self-host optionAPI/dev tool companies, managed cloud (now Adyen-owned)Subscription + usage hybrid, non-technical operatorsEnterprise committed-spend contracts, now inside StripePLG SaaS, entitlements + StripeTeams already on Stripe, simple models
Not ideal forTeams that want a long track record and a large integration catalog todayTeams needing enterprise SLAsStrict data residency, very high event volumesPure usage-based productsSmaller companies / early stageHigh-volume metering, non-Stripe stacksTeams that need a payments-independent meter

1. ABAXUS

Open-core usage billing: a free self-hosted engine, plus ABAXUS Cloud if you would rather not run it.

Disclosure: this guide is published by the ABAXUS team. We have tried to describe every platform, ours included, in terms a buyer can verify.

ABAXUS is a metering, pricing and invoicing engine written in Go on PostgreSQL. The core is free and self-hosted: deploy it in your own Kubernetes cluster, co-located with your event sources, and every usage event, aggregate and invoice lives in your own database. ABAXUS Cloud is the same engine hosted and operated by ABAXUS, for teams that want the open core without running it. ABAXUS is in beta with limited seats, so treat it as an early-stage choice.

The architecture is modular. Major components, including storage and messaging, sit behind adapters; the defaults are PostgreSQL and a Postgres-based queue, so the default deployment is one Go service and one database. On the self-hosted core, you define how ABAXUS is composed inside your own VPC.

Strengths

You own the data contract. Idempotency keys are mandatory, meters are versioned, plans are immutable and the ledger is append-only. Because the engine is open core and the schema is yours, a future vendor change is an adapter-level decision, not a re-platforming project. After a year of acquisitions in this category, that matters.

Self-hosted data control. On the Core, usage events never leave your cluster. For healthtech SaaS with patient context in usage events, that removes a third-party processing boundary from the billing layer. (ABAXUS Cloud is hosted by us, so the same claim does not apply there; choose Core if events must stay in-house.)

No per-transaction fees. Core is free. ABAXUS Cloud is priced per tier, not as a percentage of revenue, so cost does not rise with the revenue you bill.

Exact, traceable invoices. DECIMAL(20,10) arithmetic, no floats. Every invoice line traces to raw events through SHA-256 checksums. Backfills are adjustment entries, never overwrites.

Modular by design. Storage and messaging adapters mean you can start on the defaults and swap a component when your platform standards or scale require it, without rewriting pricing or invoice logic.

Weaknesses

You operate it (Core). Self-hosting means your team runs upgrades, backups and on-call. If you want zero operational overhead, use ABAXUS Cloud or a different vendor.

Newer, smaller ecosystem. Chargebee and Stripe have years of prebuilt integrations. ABAXUS integrates through its API, so expect more initial setup, and expect fewer public case studies.

Beta, solo-founder-led. ABAXUS is pre-GA with limited seats. The open core is the mitigation: you can read, fork and run the code without us.

Cloud-tier features are early. Spike control, agentic dispute resolution and prebuilt ingestion connectors are part of the ABAXUS Cloud offering and are still being built out. Ask for the current state before you plan around them.

Pricing

TierPriceNotes
Core$0, self-hostedNo event or customer caps. Community support on GitHub.
Cloud Growth$12K/yr standard ($4.2K/yr for early adopters)250 billed customers, 100M events/month, 4-hour response SLA
Cloud ScaleCustomHigher volumes, multi-region, compliance reviews

Early adopter program: 65% off Cloud, locked for life, limited seats. See full pricing →

Who ABAXUS is for

Engineering-led SaaS teams billing on API calls, compute, tokens or other high-volume metered dimensions that want to own the data contract and avoid percentage-of-revenue fees. A strong fit for healthtech SaaS with PHI in usage events (self-hosted Core) and for teams that want an inspectable, modular engine rather than a black-box API.

Who should look elsewhere

Teams that want a battle-tested vendor with a large integration catalog today. Companies below roughly $2M ARR where fee savings do not justify a migration. Products with flat-rate pricing and little metered volume.


2. Lago

Open source usage-based billing, self-hosted or cloud.

Lago is open source (AGPL-3.0) software for usage-based billing. It provides a full billing API with metering, pricing logic, invoice generation, and a customer portal. The self-hosted version is free; a cloud-hosted version is available for teams that want the open source foundation without the operational overhead.

Strengths

Genuinely open source. The billing engine is published under the AGPL-3.0 license: inspect the code, fork it and run it without a vendor dependency. AGPL has a condition worth reading before you adopt it: if you modify Lago and let users interact with it over a network, you must offer them your modified source. Running an unmodified copy carries no such duty. Have your counsel confirm what that means for your use.

Strong developer experience. The API is well-documented, actively maintained, and designed to be integrated by engineers. The community is active; the changelog is transparent about what is and is not supported.

Self-hosted data control. Like ABAXUS, the self-hosted deployment keeps all usage data in your own infrastructure. For teams where data residency matters but open source is preferred over a commercial license, Lago is the primary option.

Progressive complexity. Lago handles most common billing models — per-unit, tiered, volume, graduated, package — and the configuration is accessible without requiring custom code for standard use cases.

Weaknesses

Community support on the open source tier. The self-hosted version is community-supported. If you need guaranteed SLAs, priority incident response, or dedicated support, you are on the cloud plan — which changes the cost comparison.

Paid tiers are quote-based. Lago Cloud and Lago Premium (customer portal, prepaid credits, entitlements and RBAC, available on self-hosted too) are priced by quote, so the cost comparison with proprietary platforms is not visible until you talk to sales.

Enterprise readiness. Lago’s strengths are on the developer and startup end of the market. Complex enterprise contract structures, committed-spend agreements with custom exceptions, and deep ERP integrations are less mature than in enterprise-focused platforms.

Pricing

Self-hosted open-source edition: free (AGPL-3.0). Cloud and Premium: by quote, not publicly listed. Confirm current terms on getlago.com.

Who Lago is for

Development teams that want an open source billing foundation they can inspect, modify, and run themselves. Early and growth-stage companies that want to avoid proprietary vendor lock-in from the start. Teams where the engineering capacity exists to own and maintain the billing infrastructure.

Who should look elsewhere

Companies that need enterprise-grade SLAs, deep pre-built ERP integrations, or complex committed-spend contract structures. Companies where the engineering team cannot own the billing infrastructure deployment.


3. Orb

Cloud-native, API-first billing built for developer tools and API companies.

Orb is a managed cloud billing platform, agreed to be acquired by Adyen in June 2026, with strong support for complex usage-based pricing. It is designed with engineering teams in mind — the API is well-documented, the pricing engine handles sophisticated models, and developer experience is a primary focus. Orb positions itself as the billing layer for developer tools, AI products, and API businesses.

Strengths

Sophisticated pricing engine. Orb supports a wide range of pricing structures: tiered, volume, bulk, matrix pricing (billing on multiple dimensions simultaneously), and committed-spend with overage. Pricing configuration is accessible through code or API rather than a complex UI workflow.

Real-time metering. Event ingestion is designed for high-throughput API products. Usage data is available near real-time, and the platform handles aggregation and state management for real-time billing dashboards.

Strong developer documentation. The API reference, SDKs, and integration guides are among the strongest in the category. Engineering teams evaluating Orb typically find that integration friction is low.

Pricing simulations. Orb allows teams to model the revenue impact of pricing changes against historical usage data before rolling them out — a capability that reduces the risk of pricing model changes.

Managed infrastructure. No deployment, no database management, no upgrade cycles. The full billing pipeline is managed by Orb.

Weaknesses

Data lives in Orb’s infrastructure. For companies with data residency requirements or strong data sovereignty preferences, this is a fundamental constraint. Your usage events, customer data, and billing history are stored on Orb’s systems.

Cloud-only deployment. No self-hosted option. If your security requirements or regulatory environment require data to remain in your own infrastructure, Orb is not available.

Ownership is changing. Adyen has said Orb will run under an incubator model with multi-PSP support continuing “initially”, and has described the longer-term intent as convergence of billing and payments. If you use a payment processor other than Adyen, ask what the multi-PSP commitment is after the initial phase.

Hosted ingestion has throughput limits. As with any shared-infrastructure API, confirm Orb’s ingestion limits against your peak event rate.

Pricing

Pricing is not fully public; confirm current terms directly, and ask whether they change under Adyen ownership.

Who Orb is for

API companies, developer tool businesses, and AI products that want a sophisticated billing engine without infrastructure ownership. Teams where data residency is not a constraint and the cost of percentage-of-revenue pricing is acceptable relative to the engineering time saved.

Who should look elsewhere

Companies with data residency requirements. Teams that want a meter independent of any payment processor. Teams whose peak event rate needs verifying against shared API ingestion limits. Products that need their billing data in their own infrastructure for analytics, compliance, or operational reasons.


4. Chargebee

Subscription billing with usage-based capabilities — best for hybrid models.

Chargebee is one of the most established names in SaaS billing. It started as a subscription billing platform and has added usage-based capabilities over time. The result is a mature, well-integrated platform that works best for companies whose billing model is primarily subscription-based with usage-based components layered on top.

Strengths

Mature ecosystem. Chargebee has pre-built integrations with a large number of CRMs, accounting platforms, payment gateways, and other SaaS tools. For companies that need billing to connect to Salesforce, NetSuite, QuickBooks, and a dozen other systems, Chargebee’s integration library reduces implementation work significantly.

Subscription management depth. Trial management, plan changes, proration, dunning, renewal automation — among the most complete in the market. For companies with complex subscription models, this depth is hard to replicate.

Non-technical accessibility. Chargebee’s UI allows operations, finance, and sales teams to configure pricing plans, create coupons, manage customers, and generate reports without engineering involvement. This is a genuine capability advantage for companies where billing operations are not owned by engineering.

Revenue recognition compliance. Built-in support for ASC 606 and IFRS 15 revenue recognition, plus tax compliance tools, makes Chargebee relevant for companies with audit requirements.

Weaknesses

Subscription-first architecture. Chargebee’s data model and workflow are built around subscriptions. Usage-based billing is an add-on to that model, not the primary design. For companies running pure usage-based models — no subscription base — the fit is less natural.

Plan caps and overage fees. Third-party trackers describe a free entry tier up to a billing threshold, a paid plan with a monthly fee and billing cap, and a percentage overage above it, but they disagree on plan names and amounts. Model your real volume against the current pricing page before comparing.

Less developer-first. The API is functional but less cleanly designed than platforms built specifically for engineering teams. Integration via API requires more workarounds for common usage-first patterns than engine-first tools.

Pricing

Tiered plans with billing caps and overage fees, plus custom enterprise pricing. Published figures from third parties conflict, so use Chargebee’s own pricing page as the source of truth.

Who Chargebee is for

SaaS companies with primarily subscription-based models that need usage components — seat-based subscriptions with usage overages, for example. Companies that want billing configured and managed by non-engineering teams. Companies that need deep pre-built integrations with accounting, CRM, and ERP systems.

Who should look elsewhere

Companies running pure usage-based models where the subscription-centric architecture creates friction. Companies where billing is owned by engineering and developer experience is the primary evaluation criterion. Companies with full data control requirements or strict data residency constraints.


5. Metronome

Enterprise usage-based billing for large-scale committed-spend contracts.

Metronome is purpose-built for enterprise usage-based billing and, since January 14, 2026, is part of Stripe. It is aimed specifically at companies handling large committed-spend contracts, complex custom pricing structures, and enterprise-grade billing at significant transaction volume. It is used by infrastructure companies, cloud platforms, and AI businesses with enterprise customer bases.

Strengths

Enterprise contract structures. Metronome’s design is optimized for the complexity of large enterprise deals: committed-spend agreements, prepaid credits, draw-down balances, custom contract terms, ramp schedules, and amendments. Managing this contractual complexity at scale is where Metronome has the most differentiated capability.

Real-time usage at enterprise volume. The platform is designed to handle very high event volumes and produce accurate, real-time usage data for large customer accounts.

Enterprise audit trails. Usage data, contract terms, and billing calculations are maintained with the level of detail that enterprise finance teams and auditors require.

Integrations with enterprise financial systems. Deep integrations with Salesforce CPQ, enterprise ERP systems, and financial reporting tools are more mature than in earlier-stage platforms.

Weaknesses

Designed for large companies. The enterprise focus means the platform is overkill — and priced accordingly — for companies below a certain scale. Early-stage and growth-stage companies evaluating Metronome are typically not the target customer.

Sales-led process. Enterprise evaluation is a sales engagement, which adds time and friction for teams that want to move quickly.

Cloud-only, now Stripe-owned. Your usage data lives in Metronome’s systems. Metronome continues to run standalone and as the advanced usage-based engine inside Stripe Billing, but you are now buying from a payments company; ask about roadmap commitments to non-Stripe payment processors.

Less flexible for simpler models. The platform’s strengths are in enterprise contract complexity. Simple usage-based models run more efficiently on lighter platforms.

Pricing

Custom enterprise pricing through sales. Third-party trackers report published Starter-plan rates in 2026, but the sources disagree on timing; check metronome.com.

Who Metronome is for

Enterprise companies handling committed-spend contracts, ramp structures, and complex custom pricing at significant scale. Infrastructure companies, cloud platforms, and AI businesses with large enterprise customer bases where billing complexity is a primary operational challenge.

Who should look elsewhere

Early-stage and growth-stage companies — the pricing and sales process are not calibrated for this part of the market. Companies with simple pricing models that do not require enterprise contract management. Companies with data residency requirements.


6. Stigg

Pricing and entitlements platform for product-led growth SaaS.

Stigg approaches billing from a different angle than the other platforms on this list. Where ABAXUS, Lago, Orb, and Metronome focus on the metering-to-invoice pipeline, Stigg focuses on the product-facing layer: feature entitlements, pricing plan configuration, and customer-facing usage portals. It is built for PLG SaaS companies where billing and feature access logic need to be tightly coupled to product behavior.

Stigg integrates with Stripe for payment processing rather than handling payments directly — it sits between your product and Stripe, managing what customers can do on each plan and feeding usage data into Stripe Billing for invoicing.

Strengths

Entitlements as a first-class feature. Stigg’s core differentiation is its entitlements engine: a system for defining what customers on each plan can access, how many of a given resource they can consume, and what happens when they hit a limit. Most billing platforms treat this as a configuration concern — Stigg makes it a product.

Customer portal and in-app upgrade flows. Stigg ships a white-label customer portal widget that surfaces usage, plan details, and upgrade options directly inside your product. For PLG companies where the upgrade path runs through the product rather than a sales conversation, this reduces the custom UI work significantly.

Pricing plan management without engineering. Product and growth teams can modify pricing plans, feature flags, and entitlement rules through Stigg’s UI without engineering deployments. For companies iterating on pricing frequently, this operational flexibility has real value.

Real-time feature access checks. The SDK provides low-latency feature access checks that gate functionality based on current plan entitlements, usage limits, and custom rules — the link between billing and product that most billing platforms require you to build yourself.

Weaknesses

Not a standalone billing engine. Stigg does not process payments directly — it requires Stripe as the payment backend. If your payment infrastructure is not Stripe, or if you need billing logic that exceeds Stripe Billing’s capabilities, Stigg’s architecture becomes a constraint.

Cloud-only, data on Stigg’s infrastructure. Like the other SaaS billing platforms, your usage data, entitlement state, and customer plan information live in Stigg’s systems.

Less suited to high-volume metered billing. Stigg’s metering capabilities are functional but less optimized for products generating very high event volumes. For dev tools or API companies billing on billions of monthly events, Orb or ABAXUS are better architecturally matched.

Stripe dependency limits payment flexibility. Stripe’s own rate limits, API constraints, and pricing apply through the Stigg integration. The ceiling Stigg can reach is ultimately bounded by what Stripe Billing supports.

Narrower pricing model support. Complex enterprise contract structures, multi-region committed-spend, and matrix pricing are outside Stigg’s core focus.

Pricing

Tiered plans based on tracked customers and features. Starter tier available; pricing scales with usage. Third-party trackers list a Growth plan from a few hundred dollars per month; confirm current rates on stigg.io.

Who Stigg is for

Product-led growth SaaS companies that need feature entitlements and access control tightly integrated with billing. Teams building freemium-to-paid conversion flows where in-product upgrade prompts are the primary monetization mechanism. Companies already on Stripe that want to add sophisticated plan management and customer portals without building the UI themselves.

Who should look elsewhere

Companies not using Stripe. Teams with data residency requirements. Dev tools and API companies at high event volumes where Stripe Billing’s throughput becomes a bottleneck. Enterprises with complex committed-spend contracts that exceed what Stripe Billing can model.


7. Stripe Billing

Payments infrastructure with a metering API, and now Metronome behind it for advanced usage-based pricing.

Stripe Billing is the billing module of the Stripe payments platform. Many SaaS teams start here because Stripe is already in their stack. Since Stripe completed its Metronome acquisition in January 2026, the picture has two layers: basic usage-based billing through the Meters API, included in Billing pricing, and Metronome for advanced usage-based and enterprise pricing.

The constraints that matter at scale are architectural: usage data lives in Stripe’s infrastructure, billing is priced as a percentage of billing volume, and meter ingestion has documented rate limits. Per Stripe’s docs, the v1 meter events endpoint allows 1,000 calls per second per account in live mode, and the v2 event stream accepts up to 10,000 events per second by default, with higher volumes arranged through sales. Those limits are generous for most products; verify them against your peak rate, not your monthly average.

Strengths

No additional vendor onboarding. If you already use Stripe for payments, Billing adds metering to an existing relationship.

Broad global payment support. Stripe’s rails cover many currencies, local payment methods and tax tooling. No purpose-built billing platform matches this breadth.

Developer-familiar API. Integration friction is low for teams with existing Stripe experience.

Dunning and subscription management. Smart Retries and subscription lifecycle management are mature.

An upgrade path. Teams that outgrow basic metering can move to Metronome without leaving the Stripe ecosystem.

Weaknesses

Percentage-of-volume fee. Stripe’s pricing page lists pay-as-you-go Billing at 0.7% of billing volume, with a pay-monthly option that lowers the rate at higher volume. At $10M of billing volume, 0.7% is $70,000 per year, on top of payment processing fees.

All usage data lives with Stripe. For regulated industries, this creates third-party data exposure that HIPAA, SOC 2 and enterprise customer audits may flag.

Coupled to Stripe. Using Stripe’s metering is a bet on Stripe as your payments layer. If you may move processors, keep the meter independent.

No self-hosted option. There is no way to run Stripe’s billing logic inside your own infrastructure.

Pricing

Pay as you go at 0.7% of billing volume, or a pay-monthly subscription with volume tiers; payment processing fees apply separately. The Meters API includes up to 100M events per month in Billing pricing. Confirm current terms on stripe.com/billing/pricing.

Who Stripe Billing is for

SaaS companies already on Stripe that want simple to moderately complex usage-based billing without a new vendor, with Metronome as the path for enterprise complexity.

Who should look elsewhere

Teams that need the meter to be independent of their payment processor. Companies with data residency requirements. Companies where a percentage-of-volume fee is becoming a notable cost line.


Detailed Comparison by Dimension

Event Ingestion and Metering

All seven platforms support usage event ingestion, but the implementation details differ significantly and determine the ceiling you can grow to.

ABAXUS (self-hosted Core) places the event pipeline inside your own infrastructure, with ingestion through its REST API (single events, batches of up to 500, and backfills) and adapters for storage and messaging. There is no shared-vendor rate limit; the ceiling is the infrastructure you give it. Idempotency keys are mandatory, so retries and replays are safe. Prebuilt connectors for existing event sources are part of ABAXUS Cloud and still being built out.

Lago (self-hosted) similarly keeps the event pipeline in your infrastructure, with the data model and operational overhead that comes with running the deployment yourself.

Orb and Metronome have built sophisticated managed metering infrastructure for high-throughput API workloads. For companies that want this capability without building it, the managed option is faster to production, but shared-infrastructure limits apply and both vendors now have new owners.

Chargebee’s metering layer is functional but less optimized for high-volume event streams — it works well for usage components on top of subscription billing, less well for products generating millions of events per day.

Stigg handles metering for entitlement enforcement and passes usage data to Stripe Billing for invoicing. The metering layer is designed for plan management and feature gating rather than high-volume event ingestion.

Stripe Billing accepts events through the Meters API, limited to 1,000 calls per second per account on the v1 endpoint, with a v2 event stream of up to 10,000 events per second by default. For context: a developer tools company with 1,000 customers each generating 10,000 API calls a day averages about 116 events per second, well under both limits on average, so the question is peak load and batching strategy, not the daily mean.

Pricing Engine Flexibility

PlatformLinearTieredVolumeMatrix / Multi-dimCommitted-spendCustom enterprise
ABAXUS✓✓✓✓PartialPartial
Lago✓✓✓PartialPartialPartial
Orb✓✓✓✓✓✓
Chargebee✓✓✓LimitedLimitedLimited
Metronome✓✓✓✓✓✓ — core strength
Stigg✓✓Limited✗✗✗
Stripe Billing✓✓✓✗✗✗

Data Ownership

This is the dimension where the market splits cleanly into two categories:

Full data control: ABAXUS Core (self-hosted) and Lago’s self-hosted edition. Your data, your infrastructure, your retention policy, your security perimeter. For healthtech SaaS, this means usage events never cross into a third-party API from the billing layer; confirm your specific HIPAA position with your compliance counsel.

Vendor-hosted: ABAXUS Cloud, Lago Cloud, Orb, Chargebee, Metronome, Stigg and Stripe Billing. Usage data is stored and processed in the vendor’s cloud. Data export is available, but the primary copy is outside your control.

For most companies, vendor-hosted is acceptable. For companies in regulated industries, for companies with enterprise customers who audit data handling, and for companies that have made data sovereignty a strategic commitment, the distinction is material.

Pricing Model Economics

PlatformCost structureTransaction feesScales with revenue?
ABAXUS CoreFree (self-hosted)NoneNo
ABAXUS CloudAnnual tierNoneNo
Lago (self-hosted)Free (AGPL-3.0)NoneNo
Lago (cloud / Premium)By quoteVariesVaries
OrbNot fully publicVariesAsk
ChargebeePlan fee + overage %Above plan capPartially
MetronomeCustomNegotiatedNegotiated
StiggTiered by customersStripe pass-throughPartially
Stripe Billing% of billing volume0.7% pay as you goYes
ABAXUS: open-core usage billing you can run yourself

ABAXUS: open-core usage billing you can run yourself

A free, modular, self-hosted metering and billing engine. Use ABAXUS Cloud if you would rather we run it.

See how it works

Total Cost of Ownership at Scale

The comparison table shows the fee structure. The table below shows what that fee structure costs at different ARR levels — a calculation most teams fail to run before selecting a platform.

Assumptions: a platform charging 0.5% of revenue (illustrative); Stripe Billing pay-as-you-go at 0.7%; ABAXUS Cloud Growth at its $12,000/yr standard price (early adopters pay $4,200). Real contracts vary, and Stripe offers volume-tiered monthly plans, so use these as a shape, not a quote.

Your ARRABAXUS Cloud Growth (fixed)0.5% platformStripe Billing (0.7%)
$1M$12,000$5,000$7,000
$3M$12,000$15,000$21,000
$5M$12,000$25,000$35,000
$10M$12,000$50,000$70,000
$20MCustom (Cloud Scale)$100,000$140,000
$30MCustom (Cloud Scale)$150,000$210,000

The crossover for ABAXUS Cloud Growth vs. a 0.5% platform is approximately $2.4M ARR, and vs. a 0.7% platform approximately $1.7M. The self-hosted Core has no license fee at all; its cost is the engineering time to run it.

These numbers do not include operational overhead. Self-hosting requires an engineer to own the deployment, which is a real cost, and we do not have customer data to say where the break-even sits for your team. Estimate it from your own on-call and upgrade load.


Recommendation by Use Case

You want to own the data contract, run a modular engine yourself, and avoid percentage-of-revenue fees → ABAXUS. Free self-hosted core in your own cluster, with ABAXUS Cloud if you would rather not operate it. Early-stage and pre-GA, so weigh that honestly.

You want an established open-source engine you can self-host or buy managed → Lago. AGPL-3.0 licensed, with cloud and Premium tiers by quote. Read the AGPL terms against how you plan to modify and deploy it.

You want a managed billing service for an API or developer tool company → Orb. Strong developer experience and a sophisticated pricing engine. Confirm the post-Adyen roadmap and your payment-processor flexibility first.

You have a subscription-first model with usage components and need broad integrations → Chargebee. Mature ecosystem, non-technical configurability, subscription management depth and revenue recognition tooling.

You are an enterprise with complex committed-spend contracts at high volume → Metronome. Built for ramp schedules, draw-down balances and custom pricing exceptions, now inside Stripe.

You are building a PLG product and need entitlements, feature flags and in-app upgrade flows integrated with Stripe → Stigg. The product-facing layer, not a high-volume meter.

You are already on Stripe with simple pricing → Stripe Billing. Lowest vendor overhead, with Metronome as the upgrade path. Keep the meter independent if you may change payment processors.


Migrating Between Platforms

Platform migrations have a cost proportional to the data volume and schema complexity you need to move. Before selecting a platform, understand the migration path out:

Self-hosted platforms (the ABAXUS Core, Lago’s self-hosted edition) are the easiest to migrate from — your data is already in your own database, in schemas you control. Export and transform as needed.

Hosted platforms (ABAXUS Cloud, Orb, Chargebee, Metronome, Stigg, Stripe Billing) provide data export APIs, but the primary copy lives on their systems. The migration path involves: exporting historical billing data, mapping to the new schema, running parallel systems for a billing period to validate accuracy, and cutting over invoicing.

The parallel-run period is non-negotiable. Any billing platform migration that skips a parallel run where both systems process the same events and outputs are compared will discover discrepancies after the cutover — in customer invoices. Budget 4–8 weeks for a parallel run before full cutover.



ABAXUS is an open-core usage-based billing engine: a free, modular, self-hosted core, and ABAXUS Cloud if you want us to run it. Idempotent ingestion, versioned pricing and SHA-256 traceable invoices, with no per-transaction fees. See how it works → · Pricing →

Facts about other vendors were checked in October 2026 against vendor and press sources linked above. Pricing and ownership change quickly; verify with the vendor before deciding.

Frequently Asked Questions

Stop debugging billing. Start shipping product.

Your billing layer should be invisible infrastructure. In 30 minutes we map your event sources, identify your data contract gaps, and show you exactly what fixing the architecture looks like. No sales pitch.