Lago vs Metronome
Lago is an open-source billing platform (AGPLv3 core, managed cloud tiers) for usage-based and subscription pricing, self-hostable with an active community, SOC 2 Type II certified, and expanding into AI billing agents and white-label billing. Metronome is a usage-based billing platform for high-volume AI and software companies (acquired by Stripe in January 2026) with real-time metering, SQL-defined billable metrics, and enterprise contract management for multi-year deals and commitments. Both handle usage-based billing at scale; Lago leads on deployment flexibility and open-source transparency, while Metronome leads on contract complexity and metering throughput. At the canonical scenario (100 customers, $2K MRR, 100K events, 5 seats), neither Lago's cloud nor Metronome publish list pricing; both require a sales conversation.
Choose if...
- →Engineering-led teams that need billing code transparency, auditability, and the option to self-host without vendor lock-in
- →Companies with compliance or data residency requirements that rule out SaaS-only billing platforms
- →Teams adopting open-source billing infrastructure who want a managed upgrade path to a commercial cloud tier when they scale
- →Platforms that want to offer white-label billing to their own customers via Lago Embedded
- →AI and infrastructure companies with high event volumes that need enterprise contract management alongside usage-based billing
- →Teams already on Stripe that want native integration between metering infrastructure and payment collection post-acquisition
- →Companies with complex multi-dimensional pricing (model × region × tier) that requires SQL-defined billable metrics
- →Sales-led GTM motions with custom contracts, committed spend, and multi-year deals alongside a self-serve tier
Feature comparison
| Dimension | Lago | Metronome |
|---|---|---|
| Billing model | Invoice | Invoice |
| Usage authorization | Post-usage Lago's documented model is observe-only. The platform can react to consumption (block or grant more credits) but there is no primitive to query wallet state and block an action before it runs, because the authoritative balance moves at invoice finalization. | Post-usage |
| Wallet architecture | Add-on Lago supports up to 5 active wallets per customer with individual priorities and usage restrictions. Wallet balance (`balance_cents`) updates when an invoice is finalized, not on event ingestion. The `ongoing_balance_cents` estimate refreshes every 5 minutes and is a premium feature. | Add-on Prepaid credit burndown (commits) is a documented feature for credit-based billing. The core platform remains invoice-based; credits reduce invoice amounts rather than being debited atomically per event. |
| Payment processing | Integrated Lago provides native connectors for Stripe, Adyen, and GoCardless. Payment collection is handled by the connected PSP at pass-through rates; Lago orchestrates invoicing and routing. | Not applicable Metronome orchestrates billing and invoicing but does not collect payments directly. Payment collection is performed by the merchant's PSP (most commonly Stripe) at the PSP's published rates. The Stripe acquisition is expected to deepen this integration over time. |
| PSP agnostic | Partial | Partial |
| Customer portal | Hosted portal Pre-authenticated hosted portal showing invoices, usage, and wallet data. This is a premium feature unavailable in the AGPLv3 self-hosted tier. No self-service payment initiation or real-time balance top-up. | Build-your-own Metronome provides signed-URL embeddable dashboard components and a cost preview API. There is no drop-in self-service portal; customers integrate the components into their own product UI. |
| Open source | Partial The AGPLv3 core covers metering, subscriptions, usage-based billing, coupons, entitlements, and core wallet mechanics. The customer portal, credit notes and refunds, automatic dunning, tax integrations, CRM/accounting integrations, Lago AI agents, and Lago Embedded are commercial features unavailable in the free self-hosted tier. | No |
| Deployment | Both | Cloud only |
| Enterprise contracts | Basic Enterprise tier offers 24/7 support, a dedicated solutions engineer, and on-prem or VPC deployment. Lago does not publish enterprise contract management features (commitments, true-ups, amendments) equivalent to Metronome or Orb. | Full support Metronome's enterprise contract management covers multi-year deals, commitments, amendments, true-ups, backdating (34-day window), and multi-product contracts. This is one of Metronome's primary differentiators among usage-based billing platforms. |
| Profitability analytics | Aggregate | Aggregate |
Pricing comparison
- Model
- AGPLv3 self-hosted core (free); Business and Enterprise cloud tiers require sales
- Free tier
- Yes
- Starting price
- Free (AGPLv3 self-hosted core); cloud tiers require sales
- Model
- Enterprise; pricing not publicly disclosed
- Free tier
- No
- Starting price
- Contact sales
Canonical scenario — 100 customers, $2K MRR, 100K events, 5 seats
| Line item | Lago | Metronome |
|---|---|---|
| Platform fee | Not publicly available (cloud Business/Enterprise tiers); $0 for AGPLv3 self-hosted | Not publicly available |
| Per customer | $0 | Not publicly available |
| Seat fees | Not publicly available | Not publicly available |
| Event fees | $0 | Not publicly available |
| Revenue % | $0 | Not publicly available |
| Payment processing | Pass-through | Not applicable |
| Total / month | Not publicly available for cloud tiers. Self-hosted: $0 license cost plus infrastructure (a few hundred dollars/month on a major cloud at this scale) plus engineering time for deployment and maintenance. | Not publicly available — requires sales |
Lago: Lago's cloud Business and Enterprise tiers both require a sales conversation; prices are not published. Historical community discussions reference a starting cloud price of ~$3,000/month. The AGPLv3 self-hosted core is free to run but does not include the customer portal, credit notes and refunds, automatic dunning, tax integrations, CRM/accounting integrations, Lago AI agents, or Lago Embedded. Self-hosting at this event volume requires Postgres, Redis, and compute for 5+ services plus engineering for setup and ongoing maintenance. Payment processing fees are charged by the connected PSP at pass-through rates.
Metronome: Metronome does not publish pricing. This scenario cannot be computed from public information. Payment processing is performed by the customer's PSP (typically Stripe) at the PSP's published rates; Metronome does not collect payments directly. Enterprise pricing requires a sales conversation.
Lago: strengths and limitations
- +AGPLv3 core is fully auditable, forkable, and self-hostable at no license cost — code transparency matters for compliance-oriented buyers
- +Flexible deployment: self-hosted Docker Compose, managed cloud, on-premise, VPC, or custom infrastructure — suits data residency requirements
- +Extensive native integration ecosystem — Stripe, Adyen, GoCardless, Salesforce, HubSpot, NetSuite, Xero, and cloud marketplaces
- +Lago AI agents perform operational billing actions (discounts, invoice voids, payment retries) with an MCP server for machine-driven operations
- +Lago Embedded enables platforms to offer white-label billing features to their own customers without building billing from scratch
- +Active open-source community — 9,500+ GitHub stars, 183 total releases, latest v1.45.1 released April 7, 2026; SOC 2 Type II certified
- −Invoice-based architecture — wallet balance updates when an invoice is finalized, not on event ingestion; no real-time per-event debit
- −Material feature set gated behind paid tiers — the free AGPLv3 core excludes the customer portal, credit notes and refunds, automatic dunning, tax integrations, and CRM/accounting connectors
- −Cloud pricing is not publicly listed — Business and Enterprise tiers both require sales; historical community references cite a ~$3,000/month starting point
- −Self-hosting a production deployment still requires engineering for infrastructure, webhook wiring, payment provider setup, and release upgrades
- −No pre-usage authorization primitive — the platform can react to consumption after the fact but cannot gate individual events before they run
- −No native independent asset types — custom units like tokens or GPU hours are labels over USD-backed credit balances, not separate monetary primitives
Metronome: strengths and limitations
- +Enterprise contract management covering multi-year deals, commitments, amendments, true-ups, and multi-product billing in one platform
- +SQL-based billable metrics let teams author complex aggregation logic without bespoke engineering pipelines
- +High-throughput streaming aggregation architecture processes billions of usage events monthly, with publicly named customers including OpenAI, Anthropic, Databricks, and NVIDIA
- +Multi-motion GTM: unified support for self-serve, sales-led enterprise contracts, and cloud marketplace billing across AWS, Azure, and GCP
- +Real-time pending invoice visibility through a cost preview API and in-product invoicing before cycle end
- +Post-acquisition Stripe ecosystem access, including global payments infrastructure, tax, analytics, and revenue recognition
- −Post-usage invoicing model — usage accumulates and is invoiced at cycle end; no real-time wallet debit that reserves funds before each event is consumed
- −SQL and engineering dependency — setting up usage events and billable metrics requires SQL expertise; non-technical teams cannot manage pricing without developer involvement
- −34-day event backfill window constrains retroactive corrections and pricing changes for usage events older than five weeks
- −Pricing not publicly available — enterprise pricing requires a sales conversation with no published starting figure
- −Customer portal requires integration — signed-URL embeddable dashboards are provided, not a drop-in self-service billing page
- −Missing compliance certifications — HIPAA, FedRAMP, and ITAR are not publicly listed, limiting healthcare and US government applicability
Which one should you pick?
Choose Lago if your team needs code transparency, self-hosting, or data residency compliance. The AGPLv3 core can be audited, forked, and run on your own infrastructure at no license cost; Metronome does not offer this. Lago's broad PSP ecosystem (Stripe, Adyen, GoCardless), extensive integrations, and SOC 2 Type II certification make it suitable for compliance-oriented teams. Lago's AI billing agents and MCP server also address automation scenarios that Metronome's current roadmap is still developing.
Choose Metronome if enterprise contract management is a core requirement: multi-year commitments, custom amendment workflows, backdating (34-day window), true-ups, and multi-product deals handled in one billing platform. Metronome's SQL-defined billable metrics support aggregation logic that Lago's metering does not cover at the same depth. The post-acquisition Stripe ecosystem integration will connect Metronome to global payment collection, tax, and revenue recognition without a separate PSP setup.
Metronome's customer base (OpenAI, Anthropic, Databricks, NVIDIA) reflects a focus on large enterprise companies with complex pricing. Lago's customer base (Mistral AI, PayPal, Groq, Synthesia) spans early-stage AI companies to large enterprises, with a notable presence among open-source-friendly engineering organizations. The right choice depends more on deployment constraints and contract complexity than on metering capability.