Best usage-based billing software in 2026

Usage-based billing has shifted from an emerging pricing model to core infrastructure for modern software companies. Stripe completed its acquisition of Metronome on January 14, 2026, in a deal reported by the press as valued at approximately $1 billion, confirming what AI, SaaS, and cloud infrastructure companies already knew: the ability to meter, rate, and invoice based on actual consumption is now a strategic priority, not a billing afterthought.

For companies billing on API calls, tokens, compute hours, or data transfer, choosing the right usage-based billing platform determines whether pricing accelerates growth or becomes an engineering bottleneck. The landscape has consolidated significantly in 2026, with three major acquisitions reshaping competition and creating clearer categories of solutions.

Most evaluations resolve into five categories: homegrown billing stacks built inside the product codebase, revenue automation platforms designed around finance workflows, billing infrastructure and metering systems focused on usage aggregation and rating, payments-first billing tools that begin with card processing, and legacy subscription platforms designed for seat-based recurring revenue. Homegrown systems remain the most common alternative of all. The categories differ mainly in how much of the path from raw usage events to cash they own, and that ownership question is usually what determines how quickly a company can change its pricing later.

This guide evaluates seven platforms across market traction, feature completeness, architectural approach, pricing accessibility, and recent innovation. Each platform is assessed for specific use cases, from AI companies billing on tokens to enterprise SaaS managing hybrid seat-plus-usage models. The ranking and the "best" framing reflect Orb's editorial assessment against those criteria rather than an externally validated benchmark, and vendor capabilities and pricing were checked against current vendor documentation and other primary sources as of August 2026.

Key takeaways

• Raw usage event retention makes corrections easier, but it does not guarantee them: Retaining granular usage events can make replay, re-rating, auditing, and historical corrections substantially easier. Retroactive pricing capability still depends on each platform's metric versioning, recomputation, adjustment, and invoicing architecture. Metronome, for example, documents that billable metrics are not retroactive and that new metrics apply to future collection and aggregation rather than historical data.
• Metering responsiveness matters most for AI products with variable COGS: For AI products with high variable cost of goods sold, prepaid credits, or hard spend limits, timely metering and usage enforcement can be especially important. Metering behavior, entitlement or credit enforcement, and invoice cadence are three separate concerns.
• 2026 acquisitions signal market maturity: Stripe completed its Metronome acquisition on January 14, 2026, Orb became part of Adyen on July 1, 2026, and Salesforce announced its agreement to acquire m3ter on June 8, 2026 and completed that acquisition on July 1, 2026. Usage-based billing is now strategic infrastructure for payments and CRM ecosystems.
• Open-source options have reached enterprise readiness: Lago displays SOC 2 Type II status and AI customers including Mistral AI and Groq, indicating that open-source billing can meet enterprise compliance expectations.
• Finance workflow integration can simplify month-end close: Native revenue recognition, accounts receivable automation, and ERP integrations can reduce manual reconciliation and simplify portions of the month-end close when implemented correctly. Maxio, for example, cites a customer reporting a five-day revenue close after implementation, which is a customer-specific outcome rather than a universal guarantee.
• Building in-house is still the most common alternative: Custom billing logic offers real flexibility early on, but as products, metrics, credits, and enterprise contracts multiply, it typically becomes a permanent engineering commitment with its own backlog, edge cases, and audit exposure. Replit chose Orb rather than building a new system internally, an approach it expected would delay a key product launch, and went live in about a month with one engineer.
• Pricing simulation reduces transition risk: The ability to test pricing changes against historical usage data before deployment helps teams estimate revenue and customer-level impact before rollout, reducing the risk of churn and revenue leakage during transitions.

1. Orb

Orb is a revenue design platform built for companies with complex usage-based and hybrid pricing models. Unlike billing systems that bolt usage features onto subscription foundations, Orb's architecture centers on raw usage event ingestion, treating pricing as a strategic function across product, finance, and go-to-market teams.

Key capabilities for usage-based billing

• SQL-based billable metrics: Define billing metrics using custom SQL queries, enabling complex aggregations like averages, maximums, minimums, and custom calculations beyond simple event counts.
• Native raw-event path plus Hosted Rollups for high-volume ingestion: Orb's native ingestion path persists raw usage events. For the highest-throughput workloads, Hosted Rollups aggregate configured usage data as it is ingested, supporting multimillion-event streaming workloads for AI and cloud infrastructure products generating massive telemetry.
• Pricing simulation: Test pricing changes against real historical usage before deployment, comparing scenarios and forecasting revenue and customer impact without affecting production billing.
• Backfilling and backdating: Apply price changes or usage corrections retroactively. Because every invoice is a query over immutable raw usage events, late or corrected data can be backfilled and affected billing state is recomputed automatically. Invoices already issued are preserved and corrected through automated adjustments such as credit notes or reissuance rather than manual reconciliation, all through Orb's accuracy-first architecture.
• 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.

Use cases

Orb serves AI companies billing for tokens, per-action usage, or compute. Cloud infrastructure providers with multi-dimensional usage patterns across storage, compute, and bandwidth by region use Orb to manage pricing complexity. Developer platforms with freemium-to-paid conversion flows and enterprise software transitioning from seat-based to usage-based models also benefit from the platform's flexibility.

Vercel reduced the time to build and launch billing for new products by 80%, with a three-week implementation, and cut hiring needs for manual reconciliation by 50% while unlocking pricing agility across 60+ SKUs. Replit reports 40x revenue growth since using Orb to monetize usage, and was able to adjust pricing for its Autoscale launch up to a week beforehand. Stytch reported a 75% reduction in time spent on billing each month.

Pricing structure

Orb uses custom pricing based primarily on two key metrics, billings and events. Advanced and Enterprise tiers also include a platform fee for added functionality and support. Orb directs prospective customers to its interactive demo, documentation, and SDKs for evaluation, then to Sales for a consultation and plan recommendation.

Why Orb leads the list

Orb stands out for combining granular usage data with flexible correction and pricing workflows. Its native raw-event path keeps usage queryable, while streaming rollups support extreme scale. Orb also supports re-rating, backdating, and invoice corrections, reducing manual reconciliation when usage or pricing changes retroactively.

Orb positions this as revenue design: engineering can step back from billing operations, product teams can iterate on pricing, and finance can work from explainable usage data. Its price evolution tools let non-engineers model, schedule, cancel, and apply pricing changes, while Orb says teams can evolve pricing models without engineering tickets.

Customer examples reinforce that value:

• Knock: Saved six months of engineering time by automating usage-based billing.
• Supabase: Reduced fees by roughly 0.4% of revenue and shifted engineering effort back to product.
• Pinecone: Consolidated multi-product usage pricing into one source of truth and avoided hiring a dedicated billing team.
• Dune: Introduced granular tiers and credits while continuing to evolve pricing without engineering support.
• Opus: Replaced manual invoice calculations with automated credits and overages.

‍Orb officially became part of Adyen on July 1, 2026. Orb continues operating as a stand-alone product, and customers can still use their preferred payment processor.

2. Stripe Billing + Metronome

Stripe Billing is a subscription management platform that already supported native usage-based and hybrid billing before the Metronome acquisition. Stripe says it spent the prior two years extending Stripe Billing with first-class support for usage-based and hybrid models, with thousands of customers using it, and basic usage-based billing continues through Stripe's own Meters API. Metronome, whose acquisition closed on January 14, 2026 in a deal reported at approximately $1 billion, materially expands Stripe's capabilities for enterprise metering, rating, contracts, and usage monetization. The combined offering provides integrated payments, billing, tax, and revenue recognition within the Stripe ecosystem.

Key capabilities

• Unified payments ecosystem: Access to 100+ payment methods and 135+ currencies through Stripe Payments integration, with availability varying by market.
• High-volume event ingestion: Metronome documents support for high-volume event ingestion without required pre-aggregation, and supports billable metrics defined with a custom SQL query for enterprise usage scenarios.
• Smart Retries: Machine learning optimization for payment retry timing to improve collection rates.
• Revenue recognition: Stripe Revenue Recognition is available for ASC 606 compliance within the same account.
• Enterprise contracts support: Metronome brings capabilities for committed spend, credit drawdown, and enterprise contract structures.

Use cases

Stripe Billing serves teams already using Stripe Payments who want deeper usage billing without migrating payment infrastructure. The platform works for SaaS companies adding or scaling usage components alongside existing subscription models. Companies processing significant payment volume through Stripe benefit from the integrated ecosystem without managing multiple vendor relationships.

Pricing structure

Stripe Billing charges 0.7% of billing volume on pay-as-you-go plans, or $620 to $5,750 per month for volume-based tiers with one-year contracts. Metronome's Startup plan is priced at $0.04 per 1,000 ingest events plus 0.8% of billing volume, with a Custom plan available for companies scaling revenue or transforming their pricing.

Organizational fit

Stripe Billing with Metronome fits organizations that prioritize ecosystem integration over billing specialization. Teams already on Stripe Payments gain a clear upgrade path as usage complexity grows. The acquisition consolidation means future product direction aligns with Stripe's broader platform strategy. Metronome documents that billable metrics are not retroactive, so metric changes affect future collection and aggregation rather than historical data. A common pattern among companies with multi-metric AI and infrastructure pricing, commit-and-overage structures, drawdowns, or reseller and marketplace hierarchies is to keep Stripe for payments and run the billing and invoicing layer on Orb, where invoices are computed over raw usage events and can be simulated, backdated, and amended.

3. Lago

Lago is an open-source usage-based billing platform licensed under AGPLv3. The platform provides complete billing infrastructure that can be self-hosted or used as a managed cloud service.

Key capabilities

• Open-source foundation: Full source code access with AGPLv3 licensing enables self-hosting, modification, and audit of billing logic.
• Seven aggregation methods: COUNT, COUNT_UNIQUE, LATEST, MAX, SUM, WEIGHTED SUM, and CUSTOM aggregations support diverse metering requirements.
• Event-based architecture: Lago supports event-based metering for high-volume ingestion scenarios.
• Progressive billing: Threshold-triggered invoicing issues invoices when usage crosses configured amounts rather than waiting for cycle end.
• SOC 2 Type II: Lago displays SOC 2 Type II status, signaling enterprise-grade security compliance despite the open-source model.

Use cases

Lago serves AI companies like Mistral AI and Groq that require billing infrastructure with full data control. Organizations with data residency requirements, compliance constraints, or vendor lock-in concerns benefit from self-hosting capabilities. Developer-led teams that want to audit and customize billing logic find the open-source model valuable.

Lago's GitHub repository has accumulated over 9,500 stars, indicating strong developer community engagement.

Pricing structure

Lago offers a forever-free open-source core providing fundamental billing features, which can be self-hosted. Premium packages are priced by company stage, required features, and usage dimensions such as events, invoices, or active customers, and can be cloud-hosted or self-hosted. Fixed tiers are not published publicly.

Organizational fit

Lago fits teams with engineering resources to deploy and maintain self-hosted infrastructure. The free open-source core makes it accessible for startups, while SOC 2 Type II status and premium features serve larger organizations with compliance requirements. Self-hosted deployment carries ongoing responsibility for infrastructure, upgrades, uptime, and security, which is the same category of permanent ownership that leads many teams to a managed, usage-native platform such as Orb once billing becomes business-critical.

4. Chargebee

Chargebee is a subscription management platform with native support for usage-based and hybrid billing models. The platform serves organizations with subscription-first business models as well as teams combining recurring, one-time, and consumption charges.

Key capabilities

• Revenue recognition compliance: Native ASC 606 and IFRS 15 support for finance teams managing recognized, deferred, and unbilled revenue.
• Chargebee Copilot: A public-beta AI assistant that answers product questions, retrieves data, completes supported tasks through natural language, and can connect users with Chargebee Support and create a support ticket.
• Entitlements management: Feature gating combined with usage billing for product-led growth motions.
• Payment gateway flexibility: Integration with 40+ payment gateways beyond a single payment provider.
• Usage infrastructure: Metered usage ingestion, usage aggregation, schemaless usage, custom SQL metering, usage limits and overages, and hybrid usage plus recurring plus one-time charging, with up to 500 million usage events per month on Enterprise Plus. Chargebee reported in its Winter 2026 G2 announcement that its usage infrastructure supports high-volume event processing.
• Dunning automation: Configurable retry logic and customer communication for failed payments.

Use cases

Chargebee serves SaaS companies with established subscription businesses adding usage-based pricing components. Organizations with hybrid models combining base subscriptions with usage charges benefit from the platform's subscription management depth. Companies requiring payment processor flexibility beyond a single provider use Chargebee for multi-gateway support.

Chargebee says it reached 27 consecutive quarters as G2's #1 vendor in Subscription Management in Winter 2026. Independent funding data from Inc42 lists approximately $468.6 million in total funding across eight rounds.

Pricing structure

Chargebee Billing's current Flow plan starts at 0.80% of monthly billing value with no platform fee on pay-as-you-go pricing, and includes 100 million usage events per month. A commit-monthly option is also available, shown in Chargebee's example at $99 plus 0.65% at the selected billing volume. Enterprise Plus uses a custom annual commitment.

Organizational fit

Chargebee combines mature subscription management with native usage and hybrid billing, and its percentage-based Flow pricing reduces fixed platform cost at lower billing volumes. Organizations whose pricing is anchored in seats and recurring plans tend to find that model familiar. Where requirements center on highly specialized metrics, frequent metric changes, historical corrections, and simulation over past usage, usage-native platforms such as Orb are typically the stronger anchor, because those workflows are computed directly over raw usage events.

5. Maxio

Maxio is a billing and financial operations platform formed after Battery Ventures brought Chargify and SaaSOptics together in 2021, combining subscription billing and SaaS financial operations under a single platform, with the Maxio brand emerging afterwards. The platform emphasizes unified billing and GAAP-compliant financial reporting.

Key capabilities

• Native revenue recognition: ASC 606 and IFRS 15 compliance built into billing workflows rather than requiring separate tools.
• SaaS financial reporting: Built-in metrics including MRR, ARR, churn, and LTV with finance team dashboards.
• Usage-based billing: Usage-based billing is included across Maxio's plans. Its newer high-volume Maxio Metering experience, including Advanced Formulas for combining multiple usage signals, was described as beta and initially available by request in Maxio's May 2026 and June 2026 product updates.
• ERP integrations: 85+ integrations including NetSuite, Salesforce, and HubSpot with unlimited users at no extra charge.
• Accounts receivable: AR aging reports and collection workflows for finance operations.

Use cases

Maxio serves finance teams at B2B SaaS companies that need billing and revenue recognition in a unified system. Organizations preparing for audits or requiring detailed financial reporting benefit from native GAAP compliance. Companies with complex revenue recognition requirements around multi-element arrangements and service period allocations find value in the integrated approach.

Maxio says it serves more than 2,000 customers and processes $20 billion in SaaS and AI billings annually.

Pricing structure

Maxio's current public pricing lists Grow at $599 per month for up to $100,000 in monthly billings, and Scale at custom pricing above that level. Maxio also provides sandbox functionality for testing.

Organizational fit

Maxio fits finance-led organizations where revenue recognition accuracy is as important as billing execution. Companies with CFOs driving tool selection and audit preparation requirements benefit from unified billing and financial reporting. Its higher-volume metering experience and Advanced Formulas were described as beta in mid-2026 product updates. Teams whose primary requirement is high-volume, multi-metric usage billing today often pair or replace that model with a usage-native core such as Orb, which computes billing over raw usage events and still syncs invoices, credit memos, and revenue data into ERPs like NetSuite and QuickBooks.

6. Zuora

Zuora is a highly configurable enterprise quote-to-cash and monetization platform that has served large organizations since 2007. The platform provides recurring billing, mediation, rating, subscription, usage, and hybrid pricing, and revenue recognition with extensive configuration options.

Key capabilities

• High-volume processing: Supports large-scale usage event processing with built-in mediation and rating engines.
• 50+ pricing models: Supports usage, tiered, volume, overage, and complex hybrid pricing structures.
• Invoice processing: Supports enterprise-scale invoice generation for large billing operations.
• Milo implementation agent: Launched July 28, 2026 to support quote-to-cash implementations, with Zuora saying Milo is available for every Zuora deployment.
• Revenue recognition: ASC 606 compliance with detailed waterfall reporting.

Use cases

Zuora serves Fortune 500 companies and large enterprises with complex billing requirements. Organizations with established governance for billing changes, detailed approval workflows, and extensive configuration needs use Zuora. Companies like Zoom and Box run their subscription businesses on the platform.

Zuora was named a Leader in the 2026 Gartner Magic Quadrant for Recurring Billing Applications, released August 12, 2026, and says it was positioned highest for Ability to Execute. Zuora was acquired by Silver Lake and GIC for $1.7 billion in February 2025, with the transaction closing February 14, 2025.

Pricing structure

Zuora primarily uses sales-led pricing, but its current AWS Marketplace listing publishes 12-month packages at $75,000 for Launch, $175,000 for Scale, and $250,000 for Enterprise. Negotiated direct contracts may differ.

Organizational fit

Zuora is primarily suited to organizations with enterprise-scale monetization complexity, dedicated implementation resources, and demanding integration or governance requirements. Implementation duration varies by scope, and its July 2026 Milo implementation agent supports quote-to-cash deployments. Multi-entity transformations typically involve broader change management. Teams that treat pricing as a frequently used growth lever generally favor platforms where pricing changes are configuration rather than projects, which is where Orb's simulations, backfills, and price evolution workflows fit.

7. m3ter

m3ter is a usage-based pricing and metering platform. Salesforce announced a definitive agreement to acquire m3ter on June 8, 2026 and completed the acquisition on July 1, 2026. The platform focuses on the metering and rating layer rather than end-to-end billing, integrating with existing invoicing and ERP systems.

Key capabilities

• Usage data normalization: Flexible metering layer that transforms raw usage events into billing-ready data.
• Warehouse-oriented exports: Data Warehouse Sync performs scheduled batch exports to cloud storage for downstream use in systems such as Snowflake, BigQuery, and Redshift.
• Salesforce integration: m3ter expanded its Salesforce connector on March 4, 2026, before the acquisition agreement, with support for Revenue Cloud Advanced, Revenue Cloud Billing, Agentforce Sales, and Salesforce CPQ. Following the July 2026 acquisition, Salesforce plans to bring m3ter's metering and rating capabilities natively into Agentforce Revenue Management.
• Account hierarchies: Support for complex enterprise relationships with parent-child billing structures.
• ERP connectivity: Integration with NetSuite and other financial systems for invoice generation.

Use cases

m3ter serves Series B and later SaaS companies with complex enterprise usage billing and existing billing infrastructure. Organizations that want to add sophisticated metering without replacing their current invoicing system benefit from the dedicated metering layer approach. Companies using Salesforce for CRM gain a path to native metering inside Agentforce Revenue Management following the acquisition.

Customers include ClickHouse, Matillion, Snyk, and Entrust.

Pricing structure

m3ter does not publish fixed dollar pricing. Its commercial model combines a core monthly platform fee based on needs and allowances with optional add-ons, support, and related components.

Organizational fit

m3ter fits organizations that have existing billing and invoicing systems but need more sophisticated metering capabilities. Companies heavily invested in Salesforce benefit from the deepening product alignment. Teams seeking end-to-end billing platforms may find that a metering-focused layer involves additional integration for invoicing, collections, accounts receivable, and revenue reporting, whereas Orb combines metering, pricing, subscriptions, invoicing, AR, and reporting in one system. Salesforce's completed acquisition further positions m3ter for organizations prioritizing CRM-integrated usage visibility.

Why Orb stands out for usage-based billing

Orb is built for companies that treat pricing as a strategic product capability, not just a billing function.

Key strengths include:

• Granular usage and corrections: Orb keeps raw usage queryable, supporting backfilling and backdating with automatic recomputation of unfinalized billing. Finalized invoices can be corrected through credit notes, voids, and reissuance, preserving the audit trail.
• Pricing simulation: Teams can test pricing changes against historical usage before launch to estimate customer and revenue impact without relying on engineering.
• High-volume metering: Hosted Rollups supports large streaming workloads, while Orb advertises billions of events per day and 250K+ events per second at scaled ingestion. Custom SQL metrics support averages, maximums, and other complex calculations.
• Integrated finance workflows: Orb combines billing with accounts receivable, ASC 606-aligned revenue recognition, and native NetSuite integration, helping reduce reconciliation between billing and accounting systems.
• One source of billing truth: Usage events, pricing logic, invoices, and reporting live in one system, so product, sales, engineering, and finance can work from the same underlying data.

For enterprise requirements, Orb maintains SOC 1 and SOC 2 Type II certifications, offers role-based access controls and immutable billing audit logs, and supports customer hierarchies. Qualifying enterprise agreements can also include 99.99% SLAs.

Frequently asked questions

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

Subscription billing manages recurring customer agreements and may include fixed, seat-based, tiered, usage-based, or hybrid charges, along with minimum commitments, overages, or prepaid credits. Usage-based billing specifically calculates some or all charges from measured consumption, such as API calls, tokens processed, storage used, or compute hours consumed. The two are not mutually exclusive: Stripe Billing and Chargebee both support usage-based models within their subscription billing products, and platforms like Orb support hybrid pricing that combines usage, fixed fees, and per-seat charges.

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

Building looks attractive because it offers full control, product-specific tailoring, and no vendor fees, which is why so many teams start there. The cost that tends to be underestimated is permanence. As products, metrics, credits, wallets, commits, and enterprise exceptions accumulate, billing becomes its own product surface with backlogs, uptime and security expectations, and a high blast radius when something goes wrong, and every pricing change competes with roadmap work. The outcomes companies report after moving to a dedicated platform illustrate the difference: Knock saved six months of engineering time, Pinecone avoided hiring a dedicated billing team, and Replit went live on Orb in about a month with one engineer instead of delaying a key product launch.

Can usage-based billing software handle retroactive price changes?

Platform architectures vary significantly. Retaining raw usage events can make replay, re-rating, and historical corrections easier, but retention alone does not guarantee retroactive pricing: Metronome, for example, documents that billable metrics are not retroactive and that new metrics apply to future collection and aggregation rather than historical data. Conversely, versioned aggregates, adjustments, re-rating logic, snapshots, or external source-of-truth data can support corrections without exposing every raw usage event indefinitely. Orb applies price changes and usage backfills retroactively, recomputing unfinalized billing state automatically while preserving issued invoices and correcting them through credit notes or other explicit adjustments. The differences that matter in evaluation are retention windows, backdating, deduplication, invoice-amendment semantics, and automated re-rating for scenarios like late renewals, contract renegotiations, and billing credits for service outages.

What integrations matter most for usage-based billing?

Critical integrations include payment processors for collection, ERP systems like NetSuite for financial reporting, CRM platforms like Salesforce for sales visibility, and data warehouses for analytics. Integrations also differ in whether they create native transaction records or require manual import and reconciliation. NetSuite integrations that create standard invoice and credit memo objects can reduce month-end close complexity compared to summary-level imports, though the size of that benefit depends on implementation quality and the surrounding finance process.

How long does implementation typically take for usage-based billing platforms?

Implementation timelines range from weeks to months and depend on migration scope, number of products and SKUs, contract heterogeneity, CRM, CPQ, ERP, tax, and revenue-recognition requirements, customer migration, approval and compliance needs, entity and currency count, and internal resourcing rather than on a vendor's architectural origin alone. Orb customers report implementation times measured in weeks: Vercel reports three weeks, Stytch reports two weeks, and Replit was up and running in about a month with one engineer plus UI and wrap-up support. Enterprise platforms have historically involved longer projects, and Zuora's July 2026 Milo implementation agent supports quote-to-cash deployments. Time to production depends primarily on scope, data readiness, and internal resourcing rather than on architecture category alone.