Finance & Treasury · Finance, Risk & Compliance
Should you build or buy Usage-Based Billing (Metered Billing Infrastructure)?
Usage-based billing infrastructure (also called metered billing) captures usage events from a product, applies pricing rules, generates invoices, and handles the downstream workflows around revenue recognition, dunning, and customer billing portals. It's the financial plumbing that lets SaaS and API-first companies charge customers based on what they actually consume rather than a fixed subscription.
The build-vs-buy decision for Usage-Based Billing (Metered Billing Infrastructure) turns on how proprietary your pricing model is relative to what vendor platforms support out of the box, and how much the Lago open-source option and AI-assisted implementation have actually lowered the cost and complexity of self-hosting; the two factors are genuinely close enough to require fresh analysis.
Build it, buy it, or bridge?
When building makes sense
Usage-based billing logic is one of the more genuinely company-specific problems in the finance stack. The pricing model — token counts, compute minutes, API call tiers, storage thresholds, credit burn-down — encodes your product's revenue strategy in ways that vendor defaults often can't accommodate cleanly at the edges. For API-first companies with a clear usage model and data engineering capacity, the build case has gotten real. Lago's open-source self-hosted option has reached production maturity and is in use across a meaningful number of engineering-forward teams. AI-assisted implementation has lowered the cost of building custom rating logic, and the 2–3x cost advantage over Orb or Zenskar at meaningful scale is hard to ignore. The strongest build case is a company with a well-defined pricing model that needs to experiment with it frequently — building the rating engine means pricing changes happen on your timeline, not a vendor's.
When buying makes sense
Buying metered billing infrastructure earns its keep when your requirements extend past pure metering into the compliance and integration surface that vendors have spent years building out. ASC 606 revenue recognition automation, multi-currency support, enterprise ERP connectors, and dunning workflows at scale are genuinely hard to build well, and platforms like Zuora Billing and Orb are sold into exactly that complexity. For earlier-stage companies without dedicated data engineering, getting to billing production quickly matters more than owning the stack. A vendor like Orb or Metronome (now Stripe) lets you ship a metered billing system in days rather than weeks. The buy case is also strong when your pricing model is straightforward enough that vendor configuration handles it cleanly, and when the compliance overhead of ASC 606 would require hiring finance engineers you don't need for anything else.
The desk read
Usage-based pricing encodes the company's revenue model in its metering logic. Token counts, compute minutes, API call tiers, storage thresholds, the rating rules are proprietary in a way that few other billing decisions are. That specificity, combined with Lago's open-source self-hosted option reaching production maturity, has shifted the build conversation for engineering-forward teams. Platforms like Orb and Zenskar are excellent infrastructure, but when the alternative is a maintained open-source project that Stripe itself has bet on, the calculus deserves a fresh look.
Buying earns its keep when the requirements extend beyond pure metering into revenue recognition compliance (ASC 606 automation), multi-currency support, enterprise ERP connectors, or dunning at scale. Zuora Billing is sold into exactly that complexity, which is why the pricing reflects it. For earlier-stage API-first companies with a clear usage model and engineering bandwidth to self-host, the gap between build and buy has narrowed considerably since 2024. The vendor advantage is no longer in the rating engine; it's in the compliance and integration surface that sits around it.
Frequently asked
What is Usage-Based Billing (Metered Billing Infrastructure)?
Usage-based billing infrastructure captures usage events from a product, applies pricing rules, generates invoices, and handles the downstream workflows around revenue recognition, dunning, and customer billing portals. It's the financial plumbing that lets SaaS and API-first companies charge customers based on what they actually consume rather than a fixed subscription.
When does building Usage-Based Billing (Metered Billing Infrastructure) make sense?
Building is defensible for API-first companies with a clear usage model, engineering bandwidth to self-host, and a pricing model complex enough that vendor defaults would require significant custom configuration anyway. Lago's open-source maturity and AI-assisted implementation have lowered the barrier materially, and the cost advantage over Orb or Zuora is 2–3x at meaningful scale.
When does buying Usage-Based Billing (Metered Billing Infrastructure) make sense?
Buying makes sense when requirements extend to ASC 606 automation, multi-currency, enterprise ERP connectors, or dunning at scale — areas where vendors have years of production hardening. It's also the right call when you need to ship billing quickly and don't have dedicated data engineering capacity to build and maintain the infrastructure.
What are the main Usage-Based Billing (Metered Billing Infrastructure) vendors?
Representative vendors include Metronome (now Stripe), Orb, Lago, Zuora Billing. B4 Pro scores the full set.
What makes Lago different from other metered billing vendors?
Lago is open-source and self-hostable, which makes it effectively free at the base tier and removes the percentage-of-billings pricing that Orb and Metronome charge. It has reached production maturity with real engineering teams running it in the wild. The trade-off is that you own the infrastructure, compliance integrations, and ongoing maintenance rather than buying those from a vendor.