Billing as Data Infrastructure

The real wedge is system design, not feature checklist. Legacy billing platforms were built to update a customer record a few times per month, then cut an invoice, while usage native systems sit in the product data path, ingesting raw events like API calls, tokens, or compute seconds continuously, rating them instantly, and feeding finance an auditable bill. That is why incumbents can add usage features yet still feel slow and awkward for AI and developer tools companies.

• Chargebee has pushed its infrastructure forward, promoting ingestion of up to 200,000 usage events per second. But its own docs still describe standard site thresholds around 1,000 events per second burst, which shows how usage support is being layered onto a broader subscription system rather than defining the whole product architecture.
  4 chargebee 6 chargebee
• Zuora filled the gap by buying Togai in April 2024. The point of the deal was to add a developer facing metering and rating engine to Zuora’s finance heavy stack, including event ingestion, auditable usage records, and support for up to a billion events per day. That is retrofit by acquisition, not greenfield design.
  2 sacra 7 zuora 8 sacra
• The newer set, Lago, Orb, and Metronome, starts from the opposite direction. They treat billing as an always on event pipeline between product activity and the invoice, which is why they are better suited to hybrid pricing, prepaid credits, caps, token billing, and real time spend controls. Stripe buying Metronome for about $1B validated that architecture.
  1 sacra 3 sacra 5 stripe 8 sacra

The market is heading toward billing stacks that behave more like data infrastructure than back office software. Incumbents will keep winning where revenue recognition, approvals, and multi entity controls matter most. But the center of gravity in high growth software is moving to platforms that can meter product activity in real time first, then layer invoicing and accounting on top.