Best usage-based billing software for IoT companies

IoT workloads place distinct demands on billing infrastructure. Large device fleets can generate substantial telemetry volumes, connectivity gaps can delay data arrival, and pricing may vary by sensor type, data volume, geographic region, device class, or other dimensions. These requirements benefit from billing architecture designed for usage-heavy and hybrid monetization rather than simple recurring subscriptions alone.

The right usage-based billing engine supports scalable event ingestion, device-level metering, flexible pricing logic, and explicit handling for late or backdated events across invoice states. This guide examines seven billing platforms through the lens of IoT requirements, including usage processing, dimensional metering, late-event behavior, pricing flexibility, integrations, and finance workflows.

Key takeaways

• Architecture built on raw usage events can increase IoT flexibility: Retaining granular raw usage events can support historical analysis, auditability, backfills, and eligible retroactive pricing workflows.
• Pricing simulation helps estimate rollout impact: Testing pricing changes against historical device usage before deployment can help estimate potential revenue and financial impact across customer segments without affecting production billing.
• Ingestion architecture matters at IoT scale: Sustained telemetry and burst patterns make event-processing capacity an important part of usage billing design.
• Late-arriving event handling matters for connectivity gaps: Late usage can require different treatment before invoice finalization, during any configured grace period, and after an invoice is finalized or posted.
• Device-level metering supports granular pricing: IoT billing can require tracking usage per device or endpoint to support models based on fleet size, data consumption, activity, or multiple usage dimensions.
• Billing architecture affects multiple teams: A dedicated usage billing platform can reduce engineering work around pricing changes while giving Finance and RevOps clearer ties between usage, invoice calculations, and downstream financial workflows.

1. Orb

Orb provides usage-based billing infrastructure built for companies with complex consumption patterns, making it well suited to IoT deployments that require scalable metering, flexible pricing execution, and auditable billing workflows.

Key capabilities for IoT billing

• High-throughput event ingestion: Orb documents event ingestion via API and S3 at volumes such as 250,000+ events per second and says its Enterprise platform is regularly stress-tested at that scale.
• Persistence of raw usage events: Orb's standard metering architecture retains granular raw usage events for query-based billing, historical analysis, and auditability. For exceptionally high-volume workloads, Hosted Rollups continuously aggregate configured event streams during ingestion for billing-scale processing.
• SQL-based custom metrics: Custom SQL supports flexible billing metrics, including averages, maximums, and custom calculations. This supports IoT pricing based on peak usage, throughput, device activity, or other product-specific measures.
• Dimensional pricing: 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. IoT providers can apply the same model to dimensions such as device type, geography, and data tier.
• Pricing simulation: Orb Simulations uses real product usage to model pricing changes before production and show projected customer and revenue impact without changing live billing.
• End-to-end billing execution: Orb combines metering, pricing, subscriptions, invoicing, reporting, and finance-oriented workflows around granular usage data, reducing the number of custom systems required between product usage and billing execution.

IoT-specific strengths

Orb's diff-based billing architecture supports a common IoT data pattern: usage arriving late because devices temporarily lose connectivity or transmit in batches. When late or corrected events are backfilled, Orb can recompute affected draft or pending billing. Finalized invoices can be handled through structured correction workflows such as credit notes, voiding, or void-and-reissue, while closed accounting periods can remain protected through accounting controls.

The platform also supports threshold billing, which can trigger an invoice when accrued usage charges reach a configured dollar threshold. Separately, usage and cost alerts can trigger webhooks at configured thresholds, while Spend Controls can notify customers and internal teams as spend approaches configured limits. These capabilities support prepaid, consumption-based, and hybrid IoT pricing models where visibility into usage and spend is important.

The usage-based billing operating model also matters beyond invoice calculation. By keeping granular raw usage events and pricing logic in a dedicated billing platform, Orb can reduce recurring engineering work around new metrics, backfills, pricing changes, and enterprise contract exceptions while giving Finance, Product, and RevOps a shared billing system of record.

Customer outcomes

Supabase now processes over 1.5 million invoices per month through Orb. Vercel reduced billing launch time for new products by 80%, while Stytch reduced time spent on billing each month by 75%. These examples demonstrate Orb's production scale and its ability to reduce billing-related engineering and operational work.

Pricing structure

Orb offers custom pricing across Core, Advanced, and Enterprise tiers. Pricing is based primarily on billings and events, with a platform fee for Advanced and Enterprise. Enterprise customers can also receive dedicated technical support and production readiness reviews.

Why Orb leads for IoT billing

Orb combines high-throughput ingestion, persistence of granular raw usage events, Hosted Rollups for exceptionally high-volume streams, dimensional pricing, SQL-based metrics, simulations, and auditable correction workflows in one billing platform. That combination addresses the technical and operational complexity of connected device monetization while helping Product iterate pricing, Engineering reduce billing infrastructure work, and Finance maintain traceability from usage through invoicing.

2. Lago

Lago is an open-source billing platform with positioning for IoT and telecommunications use cases, including custom usage metrics such as connected devices and data consumption.

Primary focus

• Open-source architecture: Lago is open source and supports self-hosting for organizations that prioritize deployment control, customization, data residency, or vendor independence.
• IoT-oriented metering: Lago supports custom usage metrics that can represent device counts, data consumption, and other consumption measures.
• Event-based billing: Lago supports usage event ingestion and event-based billing workflows.
• Deployment flexibility: Teams can operate Lago in their own infrastructure when self-hosting aligns with their architecture and operating model.

IoT billing considerations

Lago can fit IoT companies that value open-source software, customizable deployment, and direct control over billing infrastructure. Its device and data-consumption metrics map naturally to connected product models, while self-hosting gives infrastructure teams control over deployment and data residency.

Lago supports event-based billing and usage metering. Its IoT positioning emphasizes an open-source model, self-hosting, deployment flexibility, and IoT-oriented usage metrics.

Organizational fit

Lago is aligned with engineering-led IoT organizations that prioritize open-source control, customization, and self-hosted deployment options.

3. Metronome

Metronome became part of Stripe in January 2026 and provides usage billing infrastructure for companies with consumption-based monetization.

Primary focus

• Enterprise contract structures: Metronome supports commits, drawdowns, and custom contract structures used in enterprise usage agreements.
• SQL-based metrics: The platform supports flexible metric definition using SQL for custom usage calculations.
• Usage billing: Metronome supports event-based usage metering and rating for consumption models.
• Usage visibility: Metronome provides ongoing visibility into metered consumption and billing data.

IoT billing considerations

Metronome is relevant to IoT organizations with negotiated enterprise contracts, usage commitments, and custom pricing structures. Commit-based pricing can support customers that pre-purchase capacity and draw it down as devices or services consume usage.

Metronome focuses on usage metering, rating, and contract execution. For IoT teams that want a single usage-native billing core, Orb combines granular raw usage events, flexible pricing, invoicing, finance workflows, reporting, backfills, and pricing simulations in one platform.

Organizational fit

Metronome supports usage-based businesses from startups through large enterprises and can suit teams centered on metering, rating, and enterprise contract execution.

4. m3ter

m3ter positions itself as a usage billing platform that connects with existing CRM and ERP systems, including Salesforce and NetSuite.

Primary focus

• CRM and ERP integration: m3ter connects usage billing data with systems such as Salesforce and NetSuite.
• Traceability to raw usage events: m3ter supports traceability from charges back to raw usage events on record.
• Revenue leakage visibility: m3ter has published research on revenue leakage in usage-based businesses and positions billing accuracy as part of revenue protection.
• Usage calculations: The platform supports automated usage and billing calculations with visibility into metered consumption.

IoT billing considerations

m3ter can suit IoT companies that want usage billing data connected to established Salesforce or NetSuite workflows. Its integration-first model supports organizations that prefer to preserve existing sales and financial systems while adding metering and rating capabilities.

m3ter focuses on CRM and ERP connectivity, usage billing, and traceability. For IoT teams that want a unified usage-native billing core, Orb combines granular raw usage events, pricing execution, invoicing, simulations, backfills, and finance workflows in one platform.

Organizational fit

m3ter aligns with IoT providers that have significant Salesforce or NetSuite investments and want usage billing to fit into those existing operating workflows.

5. Chargebee

Chargebee provides a revenue platform spanning subscription billing, usage-based pricing, payment orchestration and gateway integrations, collections, and revenue recognition products.

Primary focus

• Revenue operations breadth: Chargebee provides billing, payment orchestration, collections, and revenue recognition capabilities across its product suite.
• Usage billing support: Chargebee supports usage ingestion and metered billing alongside recurring subscriptions.
• Payment gateway integrations: Chargebee supports integrations across multiple payment gateways for global collection.
• Revenue recognition: Chargebee RevRec supports automated revenue recognition workflows aligned with ASC 606 and IFRS 15.
• Established market presence: Chargebee has an established global customer base across subscription and revenue operations use cases.

IoT billing considerations

Chargebee can fit IoT companies seeking one vendor across subscription billing, usage charges, payment orchestration, collections, and revenue recognition. Its hybrid billing support is relevant to connected products that combine recurring platform fees with consumption-based charges.

Chargebee also documents configurable grace periods for usage, with usage arriving within the configured window included in the applicable billing flow. For IoT teams prioritizing usage-native pricing execution, Orb combines granular raw usage events, flexible metrics, simulations, backfills, and billing workflows in one platform.

Organizational fit

Chargebee aligns with organizations that want usage billing alongside a broad set of subscription and revenue operations capabilities in one product family.

6. Maxio

Maxio is a B2B SaaS billing platform that combines usage metering with revenue recognition, reporting, and financial operations capabilities.

Primary focus

• Finance operations: Maxio emphasizes revenue recognition, compliance, and financial reporting.
• ASC 606 support: Its revenue recognition workflows are designed to support ASC 606 and audit readiness.
• Reporting: Maxio offers custom dashboards and a broad set of one-click reports for financial analysis.
• Usage metering: Maxio supports event tracking and multi-attribute rating alongside subscription and hybrid pricing models.

IoT billing considerations

Maxio combines usage metering with finance, revenue recognition, and reporting. Its metering capabilities include event tracking, multi-attribute rating, and pricing flexibility, which can map to IoT products with multiple billable dimensions.

Maxio's March 2026 release documentation also describes a grace period before pending usage invoices are automatically issued. For IoT teams prioritizing a usage-native billing core, Orb combines persistence of raw usage events, flexible pricing execution, simulations, backfills, and high-scale ingestion.

Organizational fit

Maxio aligns with organizations that want metering alongside established finance operations, compliance workflows, and reporting.

7. Zuora

Zuora is an enterprise monetization platform spanning subscription, usage, hybrid billing, mediation, and revenue workflows.

Primary focus

• Enterprise monetization: Zuora supports subscription, hardware, recurring, and usage models for enterprise businesses.
• Usage billing: Zuora supports mediation, usage ingestion, and rating as part of its monetization stack.
• Global operations: The platform supports multi-currency and multi-entity operations.
• Revenue recognition: Zuora Revenue, a separate product from Zuora Billing, supports automated revenue management for ASC 606 and IFRS 15.

IoT billing considerations

Zuora can suit large enterprises that already operate subscription businesses and are adding connected-device or usage-based revenue streams. Its IoT-oriented capabilities include mediation, usage handling, and hybrid monetization across hardware, subscriptions, and consumption.

Zuora's documented Usage Billing flow applies invoice-state-specific handling to usage, including distinct behavior for usage received after an invoice is posted. For IoT teams prioritizing a usage-native billing core, Orb combines granular raw usage events, flexible usage pricing, simulations, backfills, and auditable billing workflows.

Organizational fit

Zuora aligns with large enterprises that want global subscription management, usage billing, mediation, and revenue workflows within an established enterprise monetization environment.

Why Orb stands out for IoT billing

IoT monetization combines technical and organizational complexity. Device fleets can generate sustained telemetry volumes, connectivity interruptions can delay events, pricing can span multiple dimensions, and enterprise contracts can introduce credits, commitments, overages, or custom terms. These pressures can create engineering bottlenecks, manual reconciliation, customer confusion, and revenue leakage when billing logic is fragmented across systems.

Orb's usage-based billing engine addresses these requirements through a usage-native architecture built around granular data and flexible pricing execution.

Persistence of raw usage events enables pricing flexibility. Orb's standard metering architecture preserves granular raw usage events for billing, analysis, and auditability. This gives teams a durable data foundation for eligible backfills, metric evolution, and historical pricing work.

Diff-based billing supports IoT data realities. Orb supports backfills and backdating. Affected draft or pending billing can be recalculated automatically, while finalized invoices use structured correction workflows that preserve the audit trail. This is especially useful when devices buffer data during connectivity gaps and transmit later.

Pricing simulation helps estimate rollout impact. Testing pricing changes against actual historical usage before deployment helps IoT providers estimate potential revenue impact across customer segments without changing production billing.

SQL-based metrics support IoT complexity. Billing on peak usage, averages, maximums, or other custom aggregations requires flexible metric definition. Orb's Custom SQL metrics can reduce application engineering work for new billable metrics once the necessary usage data is being captured.

Event ingestion scales with fleet growth. Orb documents API and S3 ingestion at volumes such as 250,000+ events per second and says its Enterprise platform is regularly stress-tested at that scale. For exceptionally high-volume streams, Hosted Rollups continuously aggregate configured incoming data for billing-scale processing.

Dimensional price groups support multi-dimensional IoT pricing. 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 same model can support IoT dimensions such as device class, geography, connectivity tier, or data plan.

One billing core reduces cross-functional friction. Pricing complexity can turn billing into a permanent engineering project and increase reconciliation work for Finance when usage data, pricing logic, and invoicing are fragmented across systems. Orb brings granular raw usage events, metric definition, pricing execution, invoicing, and reporting into one platform, helping Engineering, Product, Finance, and RevOps work from the same billing foundation.

Orb's finance workflows integrate with NetSuite to support accounting, reconciliation, and revenue recognition workflows, while customer-facing tools provide usage visibility that can help IoT customers understand consumption and spend across device fleets.

Frequently asked questions

What is usage-based billing and why is it important for IoT companies?

Usage-based billing ties some or all charges to measured consumption. IoT businesses may use pure usage pricing or combine usage charges with recurring and one-time fees. A fleet management company can charge per vehicle monitored, a smart meter provider can bill per data transmission, and an industrial sensor platform can price based on telemetry volume. This structure can align charges more closely with consumption or delivered value when usage varies materially across accounts.

What features matter in usage-based billing software for IoT businesses?

Important capabilities include scalable event ingestion, retention of granular raw usage events where historical analysis or auditability matters, device-level metering, clear late-event and invoice-state behavior, flexible metric definition, dimensional pricing, and integrations with CRM, ERP, payment, and finance systems. For organizations with evolving pricing, historical simulation and backfill support can also reduce the engineering work required to introduce new monetization models while preserving a clear connection between measured usage and billed amounts.

How can billing software manage large volumes of IoT device data?

Usage billing systems can provide ingestion, deduplication, transformation or mediation, and aggregation to turn device telemetry into billable usage. Orb's Hosted Rollups support hosted streaming aggregation for billions of events per day in exceptionally high-volume scenarios, while its standard metering architecture preserves granular raw usage events for usage-native billing.

What are the benefits of customer-facing usage dashboards for IoT services?

Usage dashboards can give IoT customers visibility into consumption and costs across device fleets. They can help customers understand usage by device, region, or time period, follow spend against thresholds, and connect invoice charges to measured consumption. Clear usage reporting can also make billing questions easier to investigate and support a more transparent customer experience.

How does usage-based billing software handle retroactive adjustments for IoT services?

Late-event behavior depends on the platform's backdating model, grace period, rating logic, and invoice state. Some systems include late events before finalization or within a configured grace period, while post-finalization usage may follow a different correction or billing workflow. Orb supports backfills and backdating for affected draft or pending billing and provides auditable correction workflows for finalized invoices. This model is particularly relevant to IoT deployments where devices can buffer and submit usage after connectivity interruptions.

Is usage-based billing suitable for all types of IoT products and services?

Usage-based billing is well suited to IoT products where consumption varies across customers and correlates with delivered value. Fleet management, industrial sensors, smart metering, and connected device platforms can use models based on device counts, telemetry, data transfer, transactions, or other measurable activity. Some IoT products with predictable usage may fit simpler subscriptions, while hybrid pricing can combine recurring charges with device, data, or other consumption-based fees.