28 metering and usage-event data statistics that define modern revenue design


Usage-based and hybrid pricing have become mainstream in SaaS. A January 2025 Metronome and Greyhound Capital survey of 100 SaaS companies found that 85% had adopted usage-based pricing, while other 2026 research shows substantial variation depending on how pricing models are classified. For enterprise SaaS organizations managing complex pricing models, hybrid billing structures, and high-volume event ingestion, selecting the right usage-based billing engine directly impacts revenue accuracy, operational efficiency, and pricing agility.
The billing software landscape has consolidated significantly. Stripe completed its acquisition of Metronome in January 2026, Salesforce announced its acquisition of m3ter in June 2026 and completed it in July, and Adyen completed its acquisition of Orb on July 1, 2026. Our read of this activity is that the category is maturing rather than fragmenting. Enterprise buyers now face a choice between full-stack platforms that handle the complete usage-to-revenue workflow, point solutions focused on metering, and established subscription platforms that have extended into usage-based models.
For many enterprise teams, the incumbent system is not a vendor at all. Billing logic lives inside the product codebase, where it offers early flexibility and control and then becomes a standing engineering commitment as pricing models evolve, enterprise contracts diversify, and event volumes grow. That homegrown baseline is what most platforms in this guide are ultimately measured against.
This guide evaluates seven billing platforms through the lens of enterprise SaaS requirements: complex pricing model support, finance workflow automation, pricing iteration speed, and scalability for high-throughput scenarios.
Orb stands apart as the revenue design platform for modern software companies, providing usage-based billing infrastructure that automates the usage-to-revenue workflow end to end. Rather than requiring teams to assemble and reconcile separate metering tools, invoicing systems, and finance integrations, Orb delivers a unified platform, integrated with the payment gateway of your choice, where pricing becomes a strategic function shared across product, finance, and go-to-market teams.
Orb excels across AI and ML platforms billing for tokens and compute, cloud infrastructure providers with multi-dimensional usage, and developer tools with freemium-to-paid conversion flows. The platform handles hybrid seat-plus-usage models, prepaid credits with configurable expiration, and mid-cycle and backdated plan changes with configurable invoice treatment.
Stytch reports 75% reduction in time their ops team spends on billing operations. Vercel achieved an 80% reduction in engineering time required for billing across new products, alongside a 50% reduction in hiring needs for manual reconciliation. Replit has experienced 40x revenue growth since using Orb to monetize usage.
The same pattern shows up across finance-led and product-led teams. Supabase consolidated invoicing in Orb, improved invoice transparency, and reduced fees by roughly 0.4% of revenue. Pinecone replaced manual invoice calculation with a single source of truth for sophisticated multi-product usage-based pricing and avoided hiring a dedicated billing team. Dune moved from a simple binary model to granular usage-based pricing with tiers and credits, then evolved pricing multiple times without drawing on engineering resources. Opus moved from manual invoicing to automated credits and overages, with transparent balances for customers.
Orb is built around three connected motions: automated event-level billing that keeps up with complex contracts, pricing execution that teams can carry out without destabilizing systems or customer trust, and revenue growth decisions made on granular usage data. Orb calls this combination revenue design, and it is the reason pricing can be treated as a strategic asset rather than back-office plumbing.
Orb's foundation is usage-native rather than subscription-first. On its raw usage event ingestion paths, teams can query usage data at any time without pre-aggregation, change pricing logic without code deployments, and define metrics retroactively. For the highest-throughput workloads, Hosted Rollups aggregate data during ingestion so teams can sustain multimillion-event volumes. Finance and product teams can configure complex pricing without engineering involvement, so they can make price changes in minutes rather than waiting on a product sprint.
Metronome is a usage-based billing platform that became part of Stripe in January 2026 after the companies signed a definitive agreement in December 2025. The companies did not publicly disclose the purchase price; contemporaneous reporting valued the transaction at approximately $1 billion. The platform focuses on metering infrastructure and enterprise contract management for high-volume scenarios.
Metronome is used by organizations including OpenAI, Anthropic, Databricks, and NVIDIA for AI and infrastructure billing scenarios. The platform provides developer-oriented metering and API infrastructure while also enabling finance and business teams to manage pricing and enterprise contracts through its application.
Following its acquisition by Stripe, Metronome offers particularly close Stripe integration, while continuing to support enterprise invoicing and workflow integrations outside Stripe, including Salesforce, NetSuite, and AWS, Azure, and GCP marketplace invoicing on its Custom plan. Metronome performs metering, rating, and invoice generation, with finalized invoices and collection workflows able to integrate with providers such as Stripe and other enterprise billing channels. It sits in the billing infrastructure and metering category, where metering and rating are the center of gravity and adjacent finance workflows are commonly handled in connected systems.
Lago is the only open-source usage-based billing platform in this category, offering an AGPLv3 license with full code access and self-hosting capabilities.
Lago serves organizations including Mistral AI, Groq, PayPal, and Synthesia. The platform appeals to teams requiring open-source flexibility, self-hosting capabilities, or reduced vendor dependency. Cloud hosting is available for teams that prefer managed infrastructure.
Lago is designed for organizations where open-source is a requirement, data residency control is mandatory, or teams have engineering resources to manage self-hosted infrastructure. Lago provides official Salesforce CRM and NetSuite integrations. As with any self-managed deployment, infrastructure operations, upgrades, and customization remain an internal responsibility.
Chargebee is a billing and monetization platform spanning subscription, usage-based, and hybrid models, with usage-metering and rating capabilities offered alongside its established subscription billing product. The platform offers a free tier and transparent pricing with dunning and payment recovery features.
Chargebee serves software companies including Freshworks and Calendly. The platform has established credibility in subscription billing markets, with a large base of published customer reviews.
Per Chargebee's current pricing page:
Chargebee suits businesses that want subscription billing and usage-based pricing in one platform, particularly those already anchored on recurring revenue. It sits in the established subscription billing category, where recurring revenue management, invoicing, and finance familiarity are the core strengths and usage models are configured alongside them.
Maxio, formed from the combination of Chargify and SaaSOptics brought together by Battery Ventures in 2021, combines subscription billing with SaaS financial metrics and revenue recognition in a single platform.
Maxio says it serves more than 2,000 SaaS, AI, and subscription businesses and handles approximately $20 billion in SaaS and AI billings annually. The platform targets finance-led organizations where billing, metrics, and revenue recognition need to exist in a unified system.
Per Maxio's current pricing page:
Maxio is designed for finance-led SaaS teams seeking billing combined with financial metrics and revenue recognition. Maxio expanded its usage capabilities in 2026, including a new Metering experience in Beta released in June 2026 with Advanced Formulas for combining multiple usage signals.
Zuora is an established enterprise monetization and billing platform serving large organizations with global operations and complex subscription needs. It became privately held following its February 2025 acquisition by Silver Lake in partnership with GIC, at which point its Class A shares ceased trading on the NYSE.
Zuora serves large software and enterprise customers including Zoom, DocuSign, and Box. The platform handles large-scale global billing operations with extensive compliance requirements, and its SaaS offering specifically targets subscription, usage, and hybrid models for software organizations.
Enterprise deployments span quote-to-cash processes, ERP connections, and governance controls, so timelines and professional services costs vary with migration scope and configuration requirements. Zuora introduced Milo in July 2026, an AI-assisted implementation approach for quote-to-cash deployments.
Zuora is oriented toward enterprises that need configurable monetization, global billing operations, revenue recognition, and extensive quote-to-cash controls, with usage models configured on top of a subscription management foundation.
BillingPlatform is an enterprise billing solution for enterprise SaaS companies that need high-volume, multidimensional rating and revenue lifecycle functionality, with a heritage in complex telecommunications and media rating that informs its rating engine depth.
BillingPlatform highlights software customers including Cloudera and Snapdocs, along with N-able. The platform targets large enterprises requiring complex rating engines and high-volume transaction processing.
BillingPlatform is designed for large enterprises with high transaction volumes and requirements for advanced, multidimensional rating engines. Implementation effort depends on migration and integration complexity, and the platform now markets AI-assisted configuration intended to streamline deployments.
When evaluating usage-based billing software, enterprise SaaS companies face a fundamental choice: keep billing logic in the product codebase, adopt a point solution that handles one piece of the billing puzzle, or implement a full-stack platform that manages the complete usage-to-revenue workflow.
Orb delivers capabilities that address the core challenges of enterprise billing:
Orb provides built-in pricing simulations that let teams model pricing changes against real and historical usage data before deployment. Teams can compare scenarios and quantify customer and revenue impact ahead of launch, which reduces uncertainty around pricing changes and enables faster, more confident experimentation.
Orb's query-based billing architecture retains raw usage events on its native ingestion path rather than only pre-aggregated data, and its diff-based engine handles backdated changes to billing state by recalculating invoices and adjusting credit ledger entries atomically. This means teams can apply price changes retroactively and adjust pricing across past invoices. Organizations can query event data using SQL to define any billable metric, supporting unlimited pricing dimensions. Orb automatically incorporates backfilled and amended usage into billing, and for the highest-throughput workloads, Hosted Rollups aggregate data during ingestion so teams can sustain multimillion-event volumes.
Orb enables non-technical users to configure complex pricing models without code. Finance and product teams can execute price changes in minutes rather than waiting on a product sprint, which turns pricing into a first-class part of the product rather than a queue item in the engineering backlog.
When billing logic lives in the product codebase, engineering absorbs event pipelines, custom metrics for one-off enterprise contracts, backfill requests, and invoice debugging. Moving that surface into Orb gives those hours back: Knock saved six months of engineering time by fully automating usage-based billing with Orb, Vercel cut engineering time for launching billing on new products by 80%, and Replit stood Orb up in one month with a single engineer instead of delaying a launch to build internally.
Orb natively handles metering, invoicing, collection workflows, and revenue recognition in a unified system, while integrating with payment gateways such as Adyen and Stripe and with finance and tax systems including NetSuite and QuickBooks. That reduces the reconciliation burden of managing multiple billing vendors and provides a single data model from event ingestion through financial reporting.
With SOC 1 and SOC 2 Type II certification, 99.99% SLAs available for enterprise customers under terms defined in the MSA, role-based access controls, and immutable billing audit logs with timestamps and attribution, Orb provides the security, compliance, and reliability that enterprise organizations require. Orb's acquisition by Adyen closed on July 1, 2026; Orb continues as a standalone product, and customers can still choose their preferred payment processor.
For enterprise SaaS companies where pricing is a competitive advantage, Orb delivers the combination of billing accuracy, pricing agility, and operational efficiency that modern software businesses need.
Usage-based billing charges customers based on actual consumption rather than fixed subscription fees. Hybrid products can combine that variable component with subscriptions, commitments, seats, or fixed charges. Usage-based billing can better align customer charges with consumption and underlying variable costs and supports land-and-expand motions, although revenue and unit-economics predictability depends on usage patterns and pricing design. Vertice's July 2026 dataset notes that spend on consumption-priced tools can vary by as much as 37.6% month to month. Adoption is now widespread: a January 2025 Metronome and Greyhound Capital survey of 100 SaaS companies found 85% had adopted usage-based pricing, while other 2026 research shows the share varies considerably depending on how models are classified.
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.
Platforms that persist raw usage events rather than only aggregated data preserve flexibility for historical analysis, retroactive price changes, backdated adjustments, and historical invoice corrections. In Orb, raw usage events on its native ingestion path can be queried using SQL to define new metrics without code deployments, and its diff-based engine recalculates invoices and credit ledger entries when backdated changes are applied. That preserved event-level detail is also what lets finance tie usage to invoice line items and journal entries with a clear audit trail.
Building in-house looks attractive because it offers full control and avoids vendor fees, and it often works well at low volumes with a single metric. As products, contracts, and segments multiply, billing becomes its own product surface with backlogs, bugs, and uptime expectations, and every pricing change or enterprise exception competes with roadmap work. Teams that move to a dedicated platform typically recover that capacity: Replit avoided a 4 to 6 month launch delay by adopting Orb instead of building, Pinecone avoided hiring a dedicated billing team, and Supabase regained engineering focus alongside cost savings after choosing Orb over continuing to patch its homegrown system.
Modern billing platforms integrate finance workflows including accounts receivable aging, dunning management, and ASC 606-aligned revenue recognition reporting. Orb's NetSuite integration syncs invoices, credit notes mapped to NetSuite credit memos, and payment records, along with relevant customer and subscription information. Accounting period locks prevent later changes to closed periods, with backdated effects recorded as catch-up adjustments in the next open period.
Enterprise buyers commonly evaluate SOC reporting as part of vendor due diligence. SOC 1 is relevant when the service affects customers' internal control over financial reporting, while SOC 2 addresses controls such as security, availability, processing integrity, confidentiality, and privacy; specific requirements depend on the buyer and use case. Additional considerations include role-based access controls, complete audit logging with timestamps and user attribution, and infrastructure designed for audit readiness with immutable logs and version control on pricing plans.
Platforms with diff-based architecture, like Orb, enable retroactive changes effective as of a past date. Orb's diff-based engine automatically recalculates invoices and credit consumption when changes are applied, which handles common enterprise scenarios including late contract renewals, infrastructure outages requiring billing credits, and contract renegotiations that require historical adjustments.



See how AI companies are removing the friction from invoicing, billing and revenue.