Lago vs Metronome: Open-Source Billing vs an Enterprise Usage-Billing Specialist Now Inside Stripe

Lago vs Metronome

Lago is open-source usage-based billing infrastructure you can self-host or run on Lago Cloud. Metronome is a closed-source enterprise usage-billing and quote-to-cash platform, acquired by Stripe in a deal that closed January 14, 2026. Both meter usage well at scale. The difference is architectural control: billing logic you own and can audit, or billing logic that now lives inside the world's largest payments company.

If you're evaluating both, the honest framing: Metronome is the more mature product for complex enterprise contracts, rate cards, commits, and revenue recognition. Lago is the option where you can read the rating engine, run it on infrastructure you control, and keep billing logic independent of a payment processor's roadmap. Stripe's own usage-based billing docs now route most advanced use cases, prepaid credits, enterprise contracts, dimensional pricing, straight to Metronome. That's a tell about where Stripe wants this to go.

What each platform actually is

Lago is open-source: metering, rating, invoicing, prepaid credits and wallets, entitlements, subscription management. AGPLv3 license, code on GitHub. Deploys self-hosted or on Lago Cloud.

Metronome is a closed-source, cloud-only enterprise usage-billing platform built for complex rate cards, commits, credits, contracts, and revenue operations. OpenAI, Anthropic, Databricks, Confluent, and Nvidia have run billing on it. As of January 14, 2026, it's a Stripe product.

We covered the acquisition's architecture story in depth in Why Stripe paid $1B for Metronome instead of fixing Billing: the short version is that Stripe Billing's 2018 architecture caps out around 1,000 events per second, built for pre-aggregated subscription usage, not the 100,000+ events per second that AI-scale metering requires. Buying Metronome was cheaper than rebuilding. What that piece didn't cover in detail is how the two products stack up feature by feature, which is what this page is for.

Deployment: self-hosted vs. cloud-only

Lago runs on your own infrastructure or on Lago Cloud. Metronome is hosted SaaS. Its public documentation describes an enterprise cloud service; there's no public self-hosted deployment path.

For most SaaS teams that's a non-issue. For healthcare companies under HIPAA, financial services firms with data residency requirements, and government contractors under security review, it's disqualifying regardless of how strong the product is otherwise. With Metronome now inside Stripe, billing data increasingly shares infrastructure with the world's largest payment processor, worth naming explicitly if data co-mingling is a compliance question for you.

Self-hosted Lago gives you the billing database, the event pipeline, the webhook infrastructure, and the rating engine's source code under your control. AGPLv3 means the code is auditable, which matters when a billing calculation error has direct revenue and compliance consequences.

Enterprise contracts: Metronome's real strength

This is the category to be honest about upfront. Metronome's rate cards and commits system is built specifically for negotiated enterprise deals: custom pricing per customer, minimum commitments, credit burndowns against commits, contract amendments and ramps. Metronome's internal positioning calls enterprise contract complexity its wedge, and that's accurate. It's the strongest enterprise usage-billing and contract-complexity story in the market, which is exactly why it shows up in mature, finance-led evaluations.

Lago supports custom deals, commitments, discounts, and versioned plans, but if your primary requirement is deeply negotiated, amendment-heavy enterprise contracts at Metronome's depth, that's a real gap, not a talking point to argue around. The honest question to ask is whether your contracts need that specific depth today, or whether you're buying for a future enterprise motion you haven't built yet.

Usage metering and event ingestion

Both platforms handle high-cardinality usage events and dimensional metering well. Metronome's ingestion is built for enterprise scale, with usage events aggregating into billable metrics through a mature pipeline.

Lago ingests through REST, batch, SDK, Kafka, Redpanda, Kinesis, and S3. The pipeline is open-source, so custom deduplication or event transformation logic gets built directly into code your team owns rather than requested from a vendor. The practical difference isn't raw ingestion capability, both handle serious volume, it's who implements changes to that pipeline when your metering logic needs to evolve.

Prepaid credits and revenue recognition

Metronome's credit and commit balance model is strong: prepaid balances, commit thresholds, burndown tracking. Its production checklist and finance workflows reflect real depth in revenue recognition, an area where Metronome is stronger than Lago today. If ASC 606 or IFRS 15 workflows sit at the center of your billing project and finance owns the buying decision, that depth matters and Lago should be evaluated honestly against it, not oversold against.

Lago's wallet is native to the billing and entitlement system: credits expire and roll over on configurable schedules, trigger real-time consumption alerts, and gate product access the moment a balance hits zero, because the wallet and the entitlement layer are the same system rather than two systems synced after the fact. For AI companies where credit balance and access control need to move together instantly, that native connection is the differentiator. For finance teams whose primary requirement is RevRec maturity, Metronome currently has the edge.

PSP neutrality: a pre-existing condition, now formalized

Here's a detail worth being precise about: Metronome required Stripe Payments before the acquisition. It wasn't payment-processor neutral to begin with, the Stripe tie was already there. The acquisition didn't create a new dependency so much as formalize one that already existed.

Stripe's own usage-based billing documentation now explicitly points advanced use cases, prepaid credits, enterprise contracts, dimensional and composite pricing, to Metronome. Stripe Billing handles simpler recurring billing; Metronome is positioned as the answer for anything usage-heavy. If you're on Stripe already and want billing and payments in one increasingly unified stack, that's a coherent reason to pick Metronome. If you want billing logic that doesn't assume a specific payment processor, Lago integrates with Stripe, Adyen, GoCardless, and others without routing through any of them by default.

Pricing: what you actually pay

Lago's open-source core is free to self-host; you pay for your own infrastructure and the engineering time to run it. Lago Cloud is a flat monthly fee that doesn't scale with revenue.

Metronome doesn't publish pricing. Its model has historically combined a platform access fee with a rate per volume of events ingested, plus, in some structures, a percentage of what customers bill through the platform. Exact terms require a sales conversation, standard for enterprise-motion vendors, but worth factoring into a build-vs-buy comparison: a percentage-of-revenue or per-event component means the bill grows with your growth, where Lago Cloud's flat fee doesn't.

Lago vs Metronome: feature comparison

When Lago is the right choice

Self-hosted deployment is a requirement: regulated industries, data residency mandates, air-gapped environments Metronome's cloud-only model can't satisfy. PSP neutrality matters on a multi-year horizon, and you don't want billing logic implicitly tied to Stripe's payments roadmap. Billing logic is a strategic asset your engineering team wants to read, audit, and modify directly rather than request changes to. Your credit and entitlement logic needs to move in real time, not just be tracked accurately. Cost predictability matters more than a percentage-of-revenue model as you scale.

When Metronome is the right choice

Enterprise contract complexity, custom rate cards, commits, amendments, ramps, is a primary requirement today, not a someday feature. Revenue recognition and finance workflows are central and mature RevRec tooling outweighs deployment flexibility. You're already deep in the Stripe ecosystem and want billing and payments converging into one stack. You want a specialist's enterprise depth without owning infrastructure, and Stripe's ownership isn't a constraint for your organization.

The honest read

Metronome earned its enterprise reputation before the acquisition: OpenAI, Anthropic, Databricks, Confluent, and Nvidia didn't pick it by accident. Nothing about Stripe's ownership makes that product depth disappear.

What changed is what you're buying alongside it. A billing specialist that already required Stripe Payments is now formally part of Stripe, at the same time Stripe's own docs are actively routing customers toward it. If PSP independence and self-hosted deployment matter to your billing strategy, Lago is the platform in this comparison that doesn't have that trajectory.

Mistral and Blacksmith run usage-based billing on Lago. Read the documentation, deploy the open-source version, or book a demo to walk through your pricing model.