Best usage-based billing software in 2026

Usage-based and hybrid pricing have become mainstream across AI, infrastructure, and SaaS. Metronome's 2025 research found that 85% of the software companies it surveyed had adopted some form of usage-based pricing, and Deloitte reports in 2026 that 83% of AI-native SaaS companies offer it. In 2026, the category also saw major consolidation: Stripe completed its acquisition of Metronome on January 14, 2026, Adyen completed its acquisition of Orb on July 1, 2026, and Salesforce announced a definitive agreement to acquire m3ter in July 2026. These acquisitions show that consumption-based monetization has become strategically important to major financial-services and enterprise-software platforms.

For companies billing on tokens, API calls, compute hours, or storage, choosing the right usage-based billing engine determines whether pricing becomes a competitive advantage or an operational burden. This guide evaluates seven platforms across event ingestion capacity, architectural approach, pricing flexibility, enterprise contract support, and total cost of ownership.

Most options in this market fall into a handful of categories: homegrown billing logic maintained inside the product codebase, metering and rating infrastructure, payments-first billing tools, established subscription platforms that have added usage capabilities, revenue automation tools focused on invoicing and collections, and usage-native platforms that cover metering, pricing, invoicing, and reporting in one system. Knowing which category a product comes from explains most of the differences in this guide, because each category was designed around a different starting point. The most common alternative to any of these platforms is still custom billing code, so build-versus-buy economics belong in the evaluation alongside vendor comparisons.

Key takeaways

• Evaluate ingestion and correction behavior, not vendor origin stories: For high-volume workloads, compare ingestion limits, backfill windows, deduplication, aggregation, replay, and rerating behavior rather than relying only on whether a vendor began as a subscription or usage-billing product. Published limits differ widely: Stripe documents up to 10,000 meter events per second through API v2 event streams, Chargebee documents up to 200,000 requests per second, and Metronome documents a 110,000 events per second default, while Orb's Enterprise platform is regularly stress-tested at 250,000+ events per second, with Hosted Rollups available for substantially higher sustained volumes.
• Pricing simulation prevents revenue surprises: Testing pricing changes against historical usage data before deployment helps teams quantify revenue impact and avoid costly mistakes during price migrations.
• Raw usage event retention can enable retroactive flexibility: Platforms that store raw usage events, rather than only aggregated totals, can enable retroactive pricing changes, backdated adjustments, and historical invoice corrections when combined with appropriate rerating and adjustment workflows. Storage alone is not sufficient: Metronome operates a 34-day historical ingest window for draft invoices, and Chargebee states that new events are not billed once an invoice is finalized.
• Open-source options exist for data-residency requirements: Self-hosting can support data-residency and sovereignty requirements, although compliance still depends on the organization's own controls and operating environment, and running the infrastructure requires engineering capacity.
• Implementation timelines depend on scope, not vendor category: Migration complexity, integration count, contract structures, and deployment scope drive timelines far more than the label a vendor uses to describe itself.
• Build versus buy is a long-term ownership decision: In-house billing usually starts as a contained project and becomes a permanent engineering commitment as products, metrics, credits, commitments, and enterprise exceptions accumulate. The relevant question is not whether a team can build billing, but whether it wants to own, staff, and audit it indefinitely.

1. Orb

Orb is a revenue design platform purpose-built for usage-based and hybrid billing at AI and infrastructure companies, with customers including Vercel, Replit, Supabase, Perplexity, and Pinecone. Adyen completed its acquisition of Orb on July 1, 2026. Orb stands out for combining query-based usage billing, pricing simulation, high-throughput ingestion, pricing execution, and finance workflows in a single platform.

Key capabilities for usage billing

• Raw usage event storage: Orb's standard query-based ingestion architecture persists granular raw usage events rather than only pre-aggregated counters. For extreme-volume workloads, Hosted Rollups provide a separate streaming-aggregation path that rolls up incoming usage while retaining the dimensions needed for billing.
• Retroactive billing workflows: Orb's persistent raw usage event architecture supports backfills, backdated price and contract changes, and historical corrections with substantially less manual reconciliation.
• SQL-based metrics: Define billing metrics using SQL queries, supporting complex aggregations like averages, maximums, minimums, and custom calculations beyond simple event counts.
• Pricing simulation: Test pricing changes against historical usage data before deployment with Orb Simulations, comparing scenarios side by side and quantifying revenue impact across customer segments.
• Dimensional price groups: Orb's dimensional price groups support pricing across multiple usage dimensions, such as region, instance type, and environment, using a single pricing configuration for dimension combinations.
• Diff-based billing engine: Preview subscription changes with draft invoices, run dry-runs of API calls, and roll back changes before they are finalized.
• End-to-end billing core: Metering, pricing, subscriptions, invoicing, accounts receivable, and revenue reporting run in one platform, with clean exports into ERPs such as NetSuite and QuickBooks and integrations with tax providers, so fewer systems sit between product usage and cash collection.

Event capacity and performance

Orb's Enterprise platform is regularly stress-tested at 250,000+ events per second, and Hosted Rollups provide a streaming-aggregation path for substantially higher sustained volumes, with Orb describing production workloads at 1M+ and multimillion-event-per-second scale. That architecture is designed for AI companies billing for tokens and API calls, where event volumes can spike unpredictably, and both ingestion paths are built for that volatility.

Customer results

Orb publishes the following outcomes for usage-heavy businesses:

• Vercel achieved an 80% reduction in the time required to build and launch billing for new products, plus a 50% reduction in hiring needs for manual reconciliation.
• Stytch reports a 75% reduction in time its ops team spends on billing operations.
• Replit has seen 40x revenue growth since implementing usage-based pricing with Orb.
• Knock saved six months of engineering time by fully automating usage-based billing with Orb, freeing its team to focus on core product work.
• Supabase moved invoicing into Orb and reduced fees by roughly 0.4% of revenue while improving invoice transparency and reducing billing-related support.
• Pinecone replaced manual invoice calculation with Orb, avoided hiring a dedicated billing team, and gave every function a single source of truth for multi-product usage-based pricing.

Pricing structure

Orb offers custom pricing across Core, Advanced, and Enterprise tiers, with billings and events as its two primary pricing metrics. Enterprise includes dedicated technical support, which Orb says can extend to production readiness reviews and guidance.

What differentiates Orb for usage billing

Orb's query-based architecture is designed to make backfills, backdated changes, historical rerating, and structured corrections first-class workflows rather than manual reconciliation projects. When a customer disputes a charge or a contract renegotiation requires backdated adjustments, Orb automatically recalculates the affected unfinalized billing state from the underlying raw usage events. For already-issued invoices, Orb preserves the finalized accounting record and handles corrections through credit notes, voiding, void-and-reissue, or other explicit adjustments as appropriate. Orb states that finance teams can execute price changes in minutes rather than waiting for engineering sprints, using its price evolution tooling.

Orb frames this combination as revenue design: automated, event-level billing that keeps up with complex contracts, pricing execution that product and finance can run themselves, and granular usage data that supports simulations, upsell analysis, and intentional monetization. Because those three capabilities run on the same raw usage events, engineering, product, and finance work from one set of numbers instead of reconciling several. Orb also says the Adyen acquisition, which closed on July 1, 2026, will let it build offerings that connect billing with Adyen's global financial infrastructure.

2. Metronome

Metronome is a usage-based billing platform serving enterprise customers including OpenAI, Anthropic, Databricks, and NVIDIA. Stripe completed its acquisition of Metronome on January 14, 2026; the purchase price was reported at roughly $1 billion but was not publicly disclosed by Stripe. Metronome now gives Stripe a first-party product for more sophisticated usage-based billing requirements.

Key capabilities

• SQL-based billable metrics: Define custom aggregation logic for complex billing scenarios.
• Enterprise contract management: Handle multi-year contracts, commitments, ramp schedules, and custom rates at scale.
• 34-day historical ingest window: Apply retroactive corrections and rerate draft invoices within a defined time period.
• High-volume processing: Metronome's documentation gives a default of 110,000 events per second for AI-scale deployments.

Organizational fit

Metronome serves large enterprises with sophisticated contract structures and high-volume usage metering requirements. The acquisition gives Stripe customers a first-party option for advanced usage-based billing and negotiated contracts.

Pricing structure

Metronome currently packages its product as Startup and Custom. Startup is listed at 0.8% of billing volume plus $0.04 per 1,000 ingest events, and Stripe's pricing page describes included startup allotments in some markets. Custom pricing is not published.

Why it made the list

Metronome serves companies including OpenAI, Anthropic, Databricks, and NVIDIA, and Stripe currently reports 35B+ usage events processed per month across the Metronome platform. The acquisition signals market validation and provides distribution advantages through Stripe's existing customer base.

Metronome sits primarily in the metering and rating layer of the stack, so invoicing experience, collections, and financial reporting are commonly handled in adjacent systems. Teams that want metering, pricing, invoicing, accounts receivable, and reporting in a single platform, and that expect frequent metric-definition changes, backfills, and simulations over historical raw usage events, tend to weigh that scope difference carefully.

3. Stripe Billing

Stripe Billing is the subscription and usage billing product from Stripe, the payments infrastructure company. It is a practical starting option for early-stage teams already using Stripe for payment processing.

Key capabilities

• Meters API: Native usage-based billing support for consumption-based pricing models.
• Unified payments and billing: Single platform for payment processing, subscription management, and usage billing.
• Global payment methods: Supports 100+ payment methods and 135+ currencies, with reach to 195 countries.
• Documented high-volume ingestion: Stripe documents up to 10,000 events per second through API v2 meter event streams, and says higher volumes of up to 200,000 events per second are also supported.
• Published pricing: Public pay-as-you-go pricing at 0.7% of Billing volume.

Organizational fit

Stripe Billing supports early-stage companies with simple usage scenarios. Teams already on Stripe payments can add usage billing without integrating a separate vendor.

Positioning within the Stripe portfolio

Stripe Billing is a broad recurring-billing product that also provides Meters-based usage billing, while Metronome is Stripe's dedicated product for more sophisticated usage-based monetization, including negotiated enterprise contracts. Companies with complex commitment structures, custom rate cards, multi-metric hybrid plans, or heavy rerating requirements generally look for a usage-native billing core that stores raw usage events and can recompute billing as contracts and definitions change, which is the pattern Orb is built for while payments continue to run on Stripe.

Pricing structure

Stripe's current US Billing pricing is 0.7% of Billing volume for pay-as-you-go, with paid monthly and custom arrangements also available. Payment-processing charges are separate; for example, Stripe's standard US domestic-card rate is 2.9% + $0.30 per successful transaction, and rates differ by country, international-card status, and currency conversion.

Why it made the list

Stripe Billing maintains a 4.4/5 G2 rating, and for developer-led teams already using Stripe it is a practical starting option. Its published pricing makes it accessible for early-stage usage billing needs. Invoicing costs are a separate line from processing fees, which is why usage-heavy businesses often revisit the economics as billing volume grows; Supabase, for example, reduced fees by roughly 0.4% of revenue after moving invoicing into Orb.

4. Lago

Lago is one of the more established open-source usage-based billing platforms, offering self-hosting capability under an AGPLv3 license. Customers include Mistral AI, Groq, PayPal, and Synthesia.

Key capabilities

• Open-source codebase: Full code access with AGPLv3 licensing for self-hosted deployments.
• Self-hosting option: Deploy on-premise or in specific cloud environments for data residency and infrastructure-control requirements.
• Seven aggregation methods: COUNT, COUNT_UNIQUE, LATEST, MAX, SUM, WEIGHTED SUM, and CUSTOM aggregations.
• Event capacity: Lago advertises up to 1 million events per second.

Organizational fit

Lago serves engineering-led teams that prioritize vendor independence, data residency, or cost control through self-hosting. The platform requires engineering capacity to deploy and maintain, which is the same capacity trade-off that applies to any self-operated billing infrastructure.

Community validation

Lago has accumulated more than 10,000 GitHub stars, indicating strong developer community adoption. The platform raised $22 million in funding to support continued development.

Pricing structure

The open-source edition is self-deployable under AGPLv3. Lago Premium, available in cloud and self-hosted deployments, is not publicly priced.

Why it made the list

Lago differentiates through its open-source and self-hosting model. It is not the only open-source option in the category, since OpenMeter and Flexprice also maintain open-source offerings, but Lago is among the most established. For organizations that need source availability, modification rights, and deployment control, Lago's self-hosted model offers that level of ownership, while private-cloud and residency controls are also available from proprietary platforms. Self-hosting remains an ongoing operational commitment, since uptime, scaling, security, and audit expectations for billing infrastructure do not go away when the software is free.

5. Chargebee

Chargebee is an established subscription billing platform that has added usage-based billing capabilities. The company says it has raised more than $480 million in funding, and in December 2025 it reported 27 consecutive quarters as a G2 leader in subscription management.

Key capabilities

• Subscription plus usage hybrid billing: Combine seat-based and consumption-based pricing in unified invoices.
• Revenue recognition: ASC 606 and IFRS 15 compliant revenue reporting.
• Payment gateway integrations: Supports 40+ payment gateways for global collections.
• High-volume ingestion: Chargebee documents up to 200,000 requests per second on live sites, plus custom SQL metering.
• Native usage architecture: Following a major usage-billing expansion launched in June 2025, Chargebee detailed its native, ground-up usage architecture in January 2026, targeting AI use cases.

Organizational fit

Chargebee serves mid-market companies transitioning from pure subscription models to hybrid pricing. Teams familiar with traditional subscription billing may find Chargebee's interface intuitive while adding usage components.

Pricing structure

Chargebee's current Billing pricing lists a Flow pay-as-you-go plan at 0.80% of monthly billing value with a $0 platform fee, including 100M usage events per month. Enterprise Plus is custom and based on an annual commitment.

Why it made the list

Chargebee's market tenure, 4.4/5 G2 rating, and recent investment in native usage billing capabilities make it a viable option for subscription-first companies adding consumption-based pricing. Its pay-as-you-go Flow economics also keep entry costs predictable for teams evaluating the platform.

Chargebee documents that new events are not billed once an invoice is finalized. Correction behavior of this kind matters most for businesses with frequent late-arriving usage, mid-period amendments, or metric definitions that change after a period closes, which is where a raw usage event foundation and explicit rerating workflows carry the most value.

6. Zuora

Zuora is a long-standing enterprise monetization and recurring-billing platform, serving large organizations including Zoom and Box. Silver Lake and GIC took the company private in February 2025 in an approximately $1.7 billion transaction.

Key capabilities

• 50+ pricing models: Supports usage, tiered, volume, overage, and custom pricing configurations.
• Enterprise revenue recognition: Full ASC 606 and IFRS 15 compliance with multi-entity support.
• Global operations: Multi-entity, multi-currency capabilities for international deployments.
• Processing capacity: Zuora reports scalability to 3 billion raw usage events per day and 400,000+ invoices per hour. Both are vendor-reported capacities.

Organizational fit

Zuora is designed for large enterprises with complex billing requirements, established finance processes, and dedicated implementation teams. Zuora says Gartner named it a Leader in the 2026 Magic Quadrant for Recurring Billing Applications, placed highest in Ability to Execute.

Implementation considerations

Implementation length depends on migration complexity, integration count, and contract structures. Zuora's July 2026 Milo announcement describes AI-powered tooling that it says is available for every new implementation. Deployments of this scope generally still involve dedicated project teams and significant configuration effort.

Pricing structure

Zuora does not publish a universal direct-sales list price. An AWS Marketplace listing currently offers a Launch package at $75,000 for 12 months.

Why it made the list

Zuora's long track record since 2007, enterprise customer base, and analyst recognition support its position for organizations that want the deepest traditional feature set and are prepared to invest in implementation. It holds a 3.9/5 G2 rating. Platforms in this category were designed first for recurring subscription billing, with usage capabilities layered on over time, so companies whose primary value metric is consumption often pair or replace them with a usage-native billing core that ingests raw usage events and still feeds invoices and revenue data back into the ERP.

7. Maxio

Maxio is a finance-focused billing platform. Battery Ventures brought Chargify and SaaSOptics together in 2021, and the Maxio brand was publicly unveiled in 2022. Maxio says it serves 2,000+ customers, supports $20 billion in SaaS and AI billings annually, and processes 5 billion usage-tracking events per month; its January 2026 B2B growth report separately describes $17 billion or more in billings under management.

Key capabilities

• Billing plus SaaS metrics: Combines subscription billing with ARR, MRR, and churn tracking in a single product.
• GAAP/IFRS revenue recognition: Full ASC 606 and IFRS 15 compliant revenue schedules.
• 2026 metering releases: Maxio announced Metering (Beta) on May 22, 2026, a re-architected high-volume variable-usage system, and followed with Advanced Formulas on June 17, 2026.
• Finance-first design: Built for CFO-led decisions with audit-ready reports and compliance workflows.

Organizational fit

Maxio serves finance teams that want unified billing and SaaS metrics without integrating separate systems. The platform is particularly relevant for companies where the CFO drives billing platform decisions.

Pricing structure

Grow tier starts at $599/month for up to $100K in monthly billings. Scale tier and enterprise pricing are custom for higher volumes.

Why it made the list

Maxio's combination of billing, revenue recognition, and SaaS metrics addresses a specific need for finance-led organizations, and the May and June 2026 metering releases signal active investment in usage billing capabilities. Finance-first platforms are typically strongest once billable quantities are already computed, so companies whose pricing depends on how usage is metered and rated in the first place often anchor on a usage-native billing platform and use it to feed those downstream finance workflows.

Why Orb stands out for usage-based billing

For companies where usage-based pricing is central to the business model, Orb combines metering, pricing, invoicing, and finance workflows in one platform.

Key strengths include:

• Raw-event metering: Orb’s raw usage event architecture persists and queries raw usage events rather than reducing them to aggregated totals. For extreme-volume workloads, Hosted Rollups uses streaming aggregation while retaining billing-relevant dimensions.
• Rerating and corrections: When late events, backdated changes, or retroactive pricing affect an unfinalized billing period, Orb automatically recalculates the billing state. For finalized invoices, Orb preserves accounting history through credit notes, voiding, void-and-reissue, and other adjustment workflows.
• Pricing simulation: Teams can use pricing simulations to test pricing changes against historical usage, compare scenarios, and estimate revenue impact before deployment.
• High-volume AI billing: For AI companies charging by tokens, API calls, or compute, Orb Enterprise is regularly stress-tested at 250,000+ events per second. Hosted Rollups provides a separate streaming-aggregation path for substantially higher sustained volumes.
• Complex pricing models: Orb’s SQL-based metrics system supports dimensional pricing, prepaid credits, hybrid models, and other aggregations that go beyond simple event counting.
• Usage-to-cash workflow: Orb covers metering, pricing, subscriptions, invoicing, accounts receivable, and revenue reporting, with integrations and exports for systems such as NetSuite, QuickBooks, and tax providers.
• Less engineering dependency: Orb says finance and product teams can configure pricing without engineering involvement, including dimensional pricing, prepaid credits, and hybrid models.

Published customer examples include:

• Pinecone: Moved from teams working from different data to a shared source of truth for multi-product usage-based pricing.
• Replit: Implemented Orb in one month with one engineer and retained the ability to make pricing changes shortly before launch.
• Dune: Shifted from a binary pricing model to granular usage-based pricing with tiers and credits without expensive code changes.
• Vercel: Used Orb to support pricing agility across 60+ SKUs.

Billing platforms differ in how they handle historical events and finalized invoices. For example, Metronome documents a 34-day historical ingest window, Chargebee states that new events are not billed once an invoice is finalized, and Zuora provides its own event-level auditability and adjustment workflows.

Orb became part of Adyen when the acquisition closed on July 1, 2026. Orb says it will continue operating as a stand-alone product.

Frequently asked questions

What is the primary difference between usage-based and subscription-based billing?

Subscription-based billing charges a fixed amount per billing period, typically monthly or annually, regardless of actual product consumption. Usage-based billing charges customers based on what they actually use, whether that's API calls, compute hours, storage, or tokens. Many modern pricing models combine both approaches in hybrid structures where customers pay a base subscription plus usage-based overages.

How does usage-based billing software help with revenue recognition compliance?

Usage-based arrangements can create ASC 606 and IFRS 15 complexity because recognition depends on when and as performance obligations are satisfied and on how variable consideration is treated, not simply on invoice timing. Deloitte's 2026 guidance notes that usage-based and outcome-based software arrangements can require different judgments depending on fixed fees, stand-ready obligations, and contract structure. Platforms with native revenue-recognition capabilities or accounting integrations can track usage at granular intervals and generate revenue recognition schedules that map consumption to accounting periods. Revenue recognition is packaged differently across the market, appearing as a native capability for some vendors, a separate module for others, and an ERP-dependent workflow elsewhere. This automation can reduce manual reconciliation and improve auditability, though judgment and internal controls still apply.

Can usage-based billing platforms handle retroactive pricing changes and corrections?

Capability varies significantly by platform, and it depends on more than the raw usage event versus aggregated distinction. Retained inputs, pricing and version history, invoice state, correction APIs, adjustment objects, and replay windows all matter. Metronome documents a 34-day historical ingest and rerating window for draft invoices, and Chargebee states that new events are not billed once an invoice is finalized. For enterprises with complex contracts and frequent amendments, raw usage event retention can be especially valuable and is an important evaluation criterion alongside those workflow details, since it is what makes backfills, backdated changes, and historical rerating repeatable rather than manual.

Should we build usage-based billing in-house or buy a platform?

Building in-house offers full control, tailoring to the product, and no vendor fees, and it often works well at low volumes with a single metric and a couple of tiers. The cost usually appears later. As products, metrics, credits, commitments, enterprise exceptions, and grandfathered plans accumulate, billing becomes its own product surface with backlogs, on-call expectations, uptime requirements, and audit obligations, and every pricing change competes with roadmap work. Orb's published customer examples describe that trade-off directly: Replit decided against building a new system in-house because it would have delayed a key product launch, and stood up Orb in one month with a single engineer; Knock saved six months of engineering time; Pinecone replaced manual invoice calculation and avoided hiring a dedicated billing team. The question is less whether a team can build billing than whether it wants to own and operate it permanently.

What integrations should I look for in a usage-based billing solution?

Critical integrations include payment processors for collections, accounting systems like NetSuite for revenue recognition, CRM platforms like Salesforce for customer data synchronization, and data warehouses for analytics. API quality matters as much as integration breadth: evaluate whether integrations create native objects in downstream systems or require manual mapping. Orb, for example, owns the billing logic while exporting cleanly into ERPs such as NetSuite and QuickBooks, integrating with tax providers, and feeding warehouses for revenue reporting, so finance keeps its existing systems and gains event-level detail behind every invoice line.