Orb as Streaming Billing Infrastructure
Orb
AI has split usage based billing into a true infrastructure layer and a software workflow layer. At the top end, vendors are no longer just generating invoices, they are ingesting raw token, API, and GPU events in real time, turning them into billable metrics, then feeding invoices and revenue data into finance systems. That is why competition now separates by throughput, data architecture, and how tightly billing is bundled with payments or ERP workflows.
-
Metronome sits in the highest performance tier. It serves AI heavy customers like OpenAI, Anthropic, Databricks, and NVIDIA, was built for millions of events per second, and became strategically important enough for Stripe to buy for about $1B. That raised the bar from billing software to core revenue infrastructure.
-
Orb competes in that same specialist tier by acting as a streaming meter, rating engine, and invoice generator. Customers send product events into Orb, define pricing logic with SQL style formulas, then let finance teams change plans, backdate migrations, model pricing changes, and sync results into NetSuite, QuickBooks, or Stripe.
-
Lower tiers compete on a different axis. Lago wins with open source control and self hosting. m3ter has leaned into mid market distribution through Paddle. Zuora and Chargebee bring incumbent finance relationships, while Zuora added Togai to improve metering, but these vendors start from subscription era systems rather than streaming first event pipelines.
The market is heading toward consolidation around a few billing control points. One group will own the highest throughput AI and infrastructure accounts, another will win bundled finance suites, and open source options will serve teams that want maximum control. Orb’s path is to stay credible at infrastructure scale while moving upward into contract to cash and pricing operations.