AI Billing
Metronome logo

Metronome

Usage-based billing and enterprise contract management for high-volume AI and software companies; now part of Stripe.

Invoice-basedEnterpriseBilling PortalMulti-PSP
Last verified: April 2026

Good fit if...

  • 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
  • Finance teams that need revenue recognition, credit memos, and ERP integrations alongside the billing platform

Pricing

Model
Enterprise; pricing not publicly disclosed
Free tier
No
Starting price
Contact sales
Revenue %
Not publicly disclosed
Per customer
Not publicly available
Per event
Not publicly available
Seat fees
Not publicly available
Transparency
Opaque

Canonical scenario — 100 customers, $2K MRR, 100K events, 5 seats

Line itemCost
Platform feeNot publicly available
Per customerNot publicly available
Seat feesNot publicly available
Event feesNot publicly available
Revenue %Not publicly available
Payment processingNot applicable
Total / monthNot publicly available — requires sales

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.


Technical profile

DimensionValue
Billing model
Invoice
Usage authorization
Post-usage
Usage tracking
Real-time metering + periodic invoice
Wallet architecture
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.
Multi-asset support
USD-with-labels
Payment processing
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
Customer portal
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.
Auto top-up
Platform-configured
Merchants configure credit top-up thresholds on behalf of customers. No customer-controlled self-service top-up interface is documented.
Integration model
Replaces stack
Profitability analytics
Aggregate
Open source
No
License
Proprietary
Deployment
Cloud only
Enterprise contracts
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.
Pricing models
Per-unit, Tiered, Volume, Subscription, Hybrid (subscription + usage), Prepaid credits / wallet, Dimensional, Custom / SQL-defined, Outcome-based

Strengths

  • +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

Limitations

  • 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

Not ideal for

  • ×Products needing real-time per-event spend control before work starts — Metronome bills post-consumption without a pre-authorization primitive
  • ×Early-stage teams without dedicated billing engineering resources; implementation requires SQL expertise and engineering time
  • ×Teams with monthly billing budgets under several thousand dollars; pricing is enterprise-only and requires a sales conversation
  • ×Products in regulated industries requiring HIPAA, FedRAMP, or ITAR compliance certification

Similar providers


Company

Founded
2019
Headquarters
San Francisco, CA, USA
Funding
Acquired by Stripe; acquisition completed January 14, 2026. Prior funding: ~$128M including $50M Series C (NEA, February 2025).

Sources