Usage-based pricing has become a major component of AI and infrastructure monetization, often as part of a hybrid model. In G2's 2026 study of 108 AI-selling companies, 85% used hybrid pricing, while 95% retained subscriptions as a pricing foundation and 73% used a usage-based component. As consumption-based pricing grows more complex, with dimensional pricing across regions, instance types, and custom metrics, the billing infrastructure you choose determines whether pricing becomes a competitive advantage or an operational bottleneck. This guide evaluates seven usage-based billing platforms through the lens of what modern software companies actually need: accurate metering at scale, flexible pricing execution, and financial workflows that close the books without manual reconciliation.

Key takeaways

• Query-based architecture enables deterministic billing: On Orb's standard query-based ingestion path, raw usage events are stored immutably and re-queried at invoice time, supporting backfills, backdated changes, and event-level auditability without re-ingesting the underlying events. For extreme-volume workloads, Hosted Rollups aggregate configured event data during ingestion.
• Pricing simulations reduce revenue risk: Testing pricing changes against historical usage data before deployment helps predict revenue impact across customer segments.
• Event throughput varies significantly by platform: Orb's Hosted Rollups deployments handle 1M+ billing events per second in production, and Orb's standard Enterprise ingestion path is regularly stress-tested at 250K+ events per second. Other published figures range from up to 110K to up to 1M events per second. All of these numbers are vendor-reported and are not necessarily benchmark-equivalent, so they should be compared with care.
• The most common alternative is still homegrown billing: In-house billing logic offers early flexibility, but as products multiply, contracts diversify, and usage models evolve, it tends to become a permanent engineering investment with its own backlog, edge cases, and on-call surface.
• Finance integration depth matters for month-end close: Native NetSuite integration with structured transaction records substantially reduces manual reconciliation between billing and accounting systems.
• Custom SQL metrics unlock complex billing logic: Defining billable metrics using SQL queries enables sophisticated aggregations like averages, maximums, and dimensional calculations beyond simple event counts.
• Enterprise contracts benefit from backdating and rerating: Backdating and rerating can be important for enterprise billing, particularly for late-arriving usage and retroactive contract amendments created by late renewals, infrastructure outages, or renegotiations.

1. Orb

Orb is the revenue design platform built for companies where usage-based billing is the primary revenue model, not an afterthought. Adyen completed its acquisition of Orb on July 1, 2026. Orb says it continues to operate as a stand-alone product, with no service interruption and continued customer choice of payment processor, and Adyen has said it is running Orb under an incubator model that preserves operational continuity and multi-PSP support in the first phase, with a longer-term intent to converge billing and payments. Where some platforms layer usage metering onto subscription-first architectures, Orb's billing engine stores raw usage events on its standard ingestion path and computes invoices at query time, enabling deterministic billing that can be audited, corrected, and evolved without data loss.

Key capabilities for usage-based billing

• Query-based billing architecture: On the standard ingestion path, raw usage events are stored immutably, and invoices are generated by querying event history. This enables audit trails where usage-based invoice line items trace back to the specific usage events that generated the charge, while fixed-fee charges trace to their pricing and subscription configuration.
• SQL-defined billable metrics: Define complex billing logic using SQL queries, supporting aggregations like averages, maximums, minimums, and custom calculations that go beyond simple event counts.
• Pricing simulations: Run side-by-side pricing experiments using real historical usage data to predict revenue impact before making changes live through Orb Simulations.
• Backdated changes and backfills: Orb automatically recalculates affected unfinalized billing state when contract terms change, usage corrections arrive late, or pricing needs retroactive adjustment. Issued invoices are preserved and corrected through structured credit note, void, void-and-reissue, or explicit adjustment workflows, so accounting history stays intact.
• Dimensional pricing: Price across multiple independent variables like region, instance type, and environment using a single pricing configuration for dimension combinations.
• Credits, commitments, and hybrid models: Support for prepaid credit balances and drawdowns, minimum commitments with overages, and platform fees combined with usage charges, so enterprise contract structures are configured rather than coded.
• Hosted Rollups: Continuously ingest billions of events daily for high-throughput scenarios, pre-aggregating configured event data during ingestion for cloud-scale workloads.

Use cases and customer outcomes

Orb excels for AI companies billing for tokens, API calls, agents, and compute usage. Cloud infrastructure providers use dimensional pricing to handle multi-axis billing across storage, compute, and bandwidth by region. Developer platforms leverage threshold billing for self-serve activation and expansion motions.

Vercel reports an 80% reduction in engineering time required for billing across new products, alongside pricing agility for 60+ SKUs and a 50% reduction in hiring needs for manual reconciliation. Stytch achieved a 75% reduction in ops team billing work. Replit has experienced 40x revenue growth since using Orb to monetize usage, and stood the platform up in one month with a single engineer rather than delaying a launch to build billing internally.

Teams also cite the cross-functional effects. Knock saved six months of engineering time by automating usage-based billing with Orb. Pinecone moved to a single source of truth for multi-product usage-based pricing and avoided standing up a dedicated billing team. Dune moved from a simple binary model to granular usage-based pricing with tiers and credits, evolving pricing repeatedly without drawing on engineering resources. Supabase reduced billing fees by roughly 0.4% of revenue while improving invoice transparency, and Opus replaced manual invoice calculation with automated credits and overages backed by transparent customer-facing balances.

Financial operations and compliance

Orb's finance workflows include native NetSuite integration that creates standard transaction records (invoices, credit memos, customer deposits, sales orders) rather than summary imports. Revenue recognition reporting provides recognized, deferred, and unbilled revenue views. Accounting period locks prevent retroactive changes to closed periods, with adjustments flowing forward instead.

Orb maintains SOC 1 Type II and SOC 2 Type II reports, with a 99.99% SLA available for enterprise customers. Supabase processes over 1.5M invoices per month through Orb.

Pricing structure

Orb uses custom pricing based on billings volume and events ingested, with a platform fee on Advanced and Enterprise plans. The platform includes dedicated technical support with migration and production readiness guidance for enterprise deployments. Teams can begin sending billable events within hours, including backfilled historical and mid-cycle usage, while full production implementation timelines scale with project scope and integration complexity.

Why Orb leads for usage-based billing

Orb positions itself as a revenue design platform rather than only a billing engine, treating pricing as a real-time strategy function integrated across product, finance, and GTM teams. The query-based architecture means teams can evolve pricing without re-ingesting historical data, run simulations against actual customer usage, and maintain event-level audit trails from usage-based invoice line items back to raw usage events. Because metering, pricing, invoicing, AR, and reporting run on the same usage-native core, engineering stops being the billing team, product can treat pricing as part of the product, and finance can explain every number back to source events.

2. Metronome

Metronome is a usage-based billing platform now owned by Stripe. Stripe agreed to acquire Metronome in December 2025 in a deal reported at approximately $1 billion by Upstarts citing eight sources, though neither company publicly disclosed the consideration. Metronome said the acquisition was complete on January 13, 2026. The deal positions Metronome as Stripe's enterprise metering solution within the broader Stripe ecosystem.

Primary capabilities

• Event ingestion at scale: Metronome's current documentation says its infrastructure supports up to 110,000 events per second, with a default ingest rate limit that begins at 5,000 events per second and can be raised for higher-volume workloads.
• Enterprise contract support: Handles complex negotiated pricing with committed-use deals and contract amendments, including prepaid and postpaid commits.
• Prepaid credits and wallets: Manages credit drawdown, expiration, and balance tracking.
• Stripe integration: Native connection to Stripe Payments for unified billing and collection.
• Custom metrics: Supports flexible, SQL-based billable metric definitions for complex billing scenarios.

Use case positioning

Metronome supports enterprise organizations with complex contract structures and high-volume usage data, and the platform supports hybrid billing models combining usage with committed spend. Following the Stripe acquisition, Metronome and Stripe position the combined offering from small startup and self-serve use cases through global public companies.

Organizational fit

Metronome has deep support for enterprise contracts and high-scale usage, and now positions its product across startup, self-serve, and enterprise use cases as part of Stripe. Its current pricing page publishes a startup model of 0.8% of billing volume plus $0.04 per 1,000 ingested events, with custom enterprise pricing available. The native Stripe integration is aimed at Stripe users rather than being a requirement for all customers.

Platforms in the metering and rating category generally focus on usage aggregation and rating, with invoicing UX, collections, AR aging, and revenue recognition handled in adjacent systems. Teams that also want pricing simulations over historical raw usage events, safe backfills after already-invoiced periods, and finance workflows in the same platform tend to evaluate Orb as the end-to-end billing core.

3. Chargebee

Chargebee is a broad billing and revenue platform with longstanding subscription-billing roots that now offers a native usage-metering and rating engine alongside subscription management, invoicing, revenue recognition, and payments functionality. The platform serves 6,500+ customers, and Chargebee says it has been recognized in G2 implementation rankings for seven consecutive years.

Primary capabilities

• Subscription management core: Mature capabilities for recurring billing, plan management, and subscription lifecycle handling.
• Native usage metering: Event-based metering and rating at up to 200K events per second per site, according to Chargebee.
• Revenue recognition: Built-in support for ASC 606 and IFRS 15 compliance through Chargebee RevRec.
• Dunning management: Automated payment retry logic and collections workflows.
• Integration ecosystem: Payment gateway and accounting system integrations.

Use case positioning

Chargebee works well for companies with subscription-first models that want to add usage-based components, and it also supports usage-led billing directly. The platform handles hybrid pricing where base subscriptions combine with metered overages. Self-service checkout and customer portal capabilities support product-led growth motions.

Pricing structure

Chargebee uses billing-volume-based pricing with pay-as-you-go and committed options. Its current primary pricing page markets a Flow plan at $0 platform fee plus 0.80% of monthly billing value, alongside committed and custom plans.

Organizational fit

Chargebee is a broad billing and revenue platform with particular depth in subscriptions and hybrid models, and its current usage product is marketed from early-stage through enterprise-scale workloads. Chargebee says its usage-based billing powers 500+ businesses ranging from early-stage startups to large AI companies. Teams with mature subscription requirements often evaluate Chargebee alongside usage-first platforms such as Orb, where raw usage events, dimensional pricing, and simulations sit at the center of the architecture.

4. Lago

Lago is the only open-source usage-based billing platform in this comparison, offering self-hosted deployment options alongside managed cloud services.

Primary capabilities

• Open-source core: Full code visibility, with the billing core licensed under AGPLv3 and available for self-hosted deployment. Some ancillary developer and agent tooling, such as Lago's agent toolkit and MCP server, is MIT-licensed rather than AGPLv3.
• Event-based metering: Lago publishes ingestion of up to 1M events per second for high-volume scenarios.
• Prepaid credits: Credit management with expiration handling and balance tracking.
• Flexible pricing models: Support for usage-based, subscription, and hybrid billing.
• API-first design: RESTful API architecture and SDKs for developer-led implementations.

Use case positioning

Lago targets teams that require infrastructure control and want to avoid vendor lock-in. Self-hosting can support data-residency and infrastructure-control requirements, subject to the organization's own compliance architecture and controls. The open-source model allows customization of rating logic for specialized billing requirements.

Pricing structure

The self-hosted billing core is free under the AGPLv3 license, and cloud-hosted deployments are offered commercially. Premium features and enterprise support are available under separate licensing terms.

Organizational fit

Lago is designed for engineering teams comfortable managing billing infrastructure in-house. Organizations with strict data sovereignty requirements or specialized customization needs often evaluate open-source options alongside managed platforms, weighing the ongoing engineering ownership of running billing infrastructure against the control it provides. Teams that would rather keep engineering focused on the core product typically look to a managed usage-native platform such as Orb, where new metrics, backfills, and pricing changes are configured instead of maintained as internal infrastructure.

5. m3ter

m3ter is a usage pricing infrastructure platform focused on complex metering scenarios for enterprise organizations. Salesforce completed its acquisition of m3ter on July 1, 2026, bringing its metering and rating technology into Salesforce's broader revenue-management strategy.

Primary capabilities

• Usage data store: Centralized repository for usage data across multiple sources, with unaggregated data retained to support analysis and experimentation.
• Flexible pricing configuration: Support for all pricing model types including tiered, volume, and dimensional.
• Revenue-recognition enablement: m3ter supplies bookings, usage, billing, and revenue-event data to ERP or dedicated RevRec systems, where revenue recognition itself is performed.
• Billing-contract configuration: Enterprise pricing and commitments, including account-specific pricing, commitments, prepayments, and schedules. This is distinct from full contract-lifecycle management covering drafting, negotiation, e-signature, and legal repository functions.
• Data warehouse integration: Connects to analytics platforms including Snowflake, BigQuery, and Redshift for downstream usage insights.

Use case positioning

m3ter targets organizations with complex metering requirements that span multiple products and data sources. The platform supports finance and billing operations teams managing sophisticated pricing structures, and deliberately leaves invoicing and revenue recognition to downstream systems.

Pricing structure

m3ter uses quote-based pricing, with a core platform fee based on requirements plus optional add-ons, enhanced support, and implementation services.

Organizational fit

m3ter is designed for enterprise organizations with dedicated pricing and billing operations teams. The platform addresses scenarios where metering complexity requires specialized infrastructure alongside separate invoicing and revenue systems. Organizations that prefer to consolidate metering, invoicing, AR, and revenue reporting into one usage-native platform, with fewer systems in the path from product usage to cash collection, tend to shortlist Orb.

6. Maxio

Maxio, formed from the merger of Chargify and SaaSOptics, is a billing platform with native revenue recognition and financial reporting capabilities.

Primary capabilities

• Unified billing and finance: Combined subscription billing with revenue recognition in a single platform.
• ASC 606 compliance: Native support for revenue recognition standards without third-party integrations.
• Financial reporting: Built-in SaaS metrics, forecasting, and investor-ready reporting.
• Subscription management: Plan management, upgrades, downgrades, and renewal handling.
• Usage billing support: Metered, usage-based, and hybrid billing capabilities alongside subscriptions.

Use case positioning

Maxio targets finance-led organizations where revenue recognition and financial reporting are primary requirements. The platform supports CFOs and finance teams managing audit readiness and investor reporting alongside billing operations.

Pricing structure

Maxio publishes a Grow plan at $599/month for up to $100K in monthly billings, while its Scale plan uses custom pricing that scales with billing volume and feature requirements.

Organizational fit

Maxio is designed for SaaS companies where finance teams drive billing platform decisions. Organizations preparing for audits, fundraising, or IPO often prioritize native revenue recognition capabilities. Companies standardizing on subscription-first finance platforms frequently add Orb as the usage-native billing and experimentation layer, ingesting raw usage events, powering complex hybrid pricing, and feeding invoice and revenue data into ERPs such as NetSuite and QuickBooks.

7. Stripe Billing

Stripe Billing is the subscription and recurring billing product within the broader Stripe payments platform, offering native integration with Stripe Payments. Stripe's revenue suite now also includes Metronome for advanced usage-based billing, though Stripe's Billing pricing page lists advanced usage-based billing through Metronome separately, so Metronome's capabilities are not automatically bundled into ordinary Stripe Billing.

Primary capabilities

• Payment-native billing: Direct integration with Stripe Payments for collection.
• Metered subscriptions: Usage reporting and billing for consumption-based pricing.
• Subscription management: Plan creation, proration, and lifecycle management.
• Tax calculation: Stripe Tax integration for automated sales tax handling.
• Developer experience: Comprehensive API documentation and SDKs.

Use case positioning

Stripe Billing works well for teams already using Stripe Payments who want to minimize implementation complexity, and Stripe says thousands of customers already use Stripe Billing for complex usage models. The distinction worth drawing is between core Stripe Billing metering and the wider Stripe plus Metronome suite, which adds multidimensional rates, negotiated contracts, sales-led models, product catalogs with thousands of SKUs, and deeper revenue analytics.

Pricing structure

As of August 2026, Stripe Billing's US pricing lists 0.7% of Billing volume for pay-as-you-go. Monthly annual-contract plans on a one-year term are $620, $1,500, $2,950, or $5,750 per month, covering up to $100,000, $250,000, $500,000, and $1,000,000 of monthly Billing volume respectively, with 0.67% on additional Billing volume. Basic usage-based billing remains available through Stripe's Meters API as part of Billing pricing, with up to 100M events per month included. The pay-as-you-go option has no recurring monthly fee, and the Billing fee is separate from payment-processing charges.

Organizational fit

Stripe Billing is designed for organizations prioritizing straightforward implementation with minimal infrastructure decisions. For teams already using Stripe Payments, Stripe Billing is an obvious option to evaluate because it keeps billing inside the same ecosystem. A common pattern as usage models grow more complex is to keep Stripe for payments and run Orb as the usage-based billing core, with raw usage events, multi-metric and hybrid plans, account hierarchies for resellers and marketplaces, and invoices that sync onward to payment and finance systems.

Why Orb stands out for usage-based billing

For companies where usage-based billing drives revenue strategy, Orb delivers capabilities that define the category. The query-based billing architecture stores raw usage events immutably on the standard ingestion path rather than aggregating and discarding data, which means teams can trace usage-based invoice line items back to the specific events that generated the charge. For extreme-volume workloads, Hosted Rollups aggregate configured event data during ingestion.

This architectural decision enables pricing simulations that test changes against historical usage, backdated adjustments for contract amendments, and audit trails that support demanding compliance reviews. When a customer disputes a charge or a contract needs retroactive modification, Orb recalculates affected unfinalized billing state from source events, while issued invoices are preserved and corrected through structured credit note, void, void-and-reissue, or adjustment workflows.

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.

The Experience Kit powers customer-facing implementations including real-time usage dashboards, pricing calculators for self-serve plan selection, and checkout flows with draft invoice previews. Customers can drill from usage-based invoice line items back to the specific usage events that generated the charge, which is what turns a variable bill into something a customer can plan around.

For finance teams, Orb's NetSuite integration creates native transaction records that map directly to ERP objects, including line-level service-period dates and a preserved ERP audit trail, which substantially reduces manual reconciliation and data transformation. Revenue recognition reporting handles recognized, deferred, and unbilled revenue views with accounting period locks that prevent retroactive changes to closed periods.

Frequently asked questions

What is usage-based billing and how does it differ from traditional subscription models?

Usage-based billing ties some or all charges to measured consumption of a product or service, while subscription billing primarily charges for recurring access or entitlements. Hybrid models combine both, and subscriptions themselves can be seat-based, tiered, or include allowances alongside variable charges. Consumption-based models can align pricing more closely with customer value when the usage metric tracks value received. Usage-based components are now widely used by AI companies billing for tokens, cloud providers charging for compute resources, and API platforms metering requests, most often as part of a hybrid structure.

What are the most critical features to look for in usage-based billing software?

Core requirements include real-time event ingestion at scale, flexible metric definition beyond simple counts, support for hybrid pricing models, backdated change capabilities for contract amendments, and native accounting integration. For enterprise deployments, audit trails, compliance attestations such as SOC 1 Type II and SOC 2 Type II reports, and SLA guarantees become essential considerations.

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

Building in-house looks attractive because it offers control and avoids vendor fees, and early versions are usually straightforward. The cost tends to arrive later, when credits and wallets, minimum commitments with overages, hybrid platform fees, grandfathered plans, and account-specific enterprise terms all coexist. At that point billing becomes its own product surface with backlogs, edge cases, and uptime expectations, and every pricing change competes with roadmap work. Replit chose Orb rather than building internally, avoiding a launch delay and standing up billing in one month with a single engineer, while Knock saved six months of engineering time and Pinecone avoided hiring a dedicated billing team.

Can usage-based billing software handle complex pricing models like dimensional pricing?

Platforms vary significantly in dimensional pricing support. Orb's dimensional price groups support pricing across multiple usage dimensions using a single pricing configuration for dimension combinations. This enables scenarios like pricing compute differently by region, instance type, and environment simultaneously. Platforms differ in how they model multi-dimensional rates and in how many separate metric definitions each dimension combination requires.

How does usage-based billing software integrate with existing accounting and CRM systems?

Integration depth varies by platform. Native integrations create standard transaction objects in accounting systems like NetSuite, which can substantially reduce manual mapping and reconciliation, though mapping between usage, SKUs, accounting accounts, tax categories, CRM objects, and ERP records may still be required. Basic integrations may only sync summary data requiring additional reconciliation. CRM integrations typically sync customer and subscription data for sales visibility into usage patterns.