Metronome

1. 1

   You sign up on the Startup plan, which is self-serve, and get an API key. There is no minimum volume and no annual commitment, and pricing is published, though the depth of the product means most teams still talk to someone before going to production.

2. 2

   Your application streams raw usage events into Metronome's ingestion API: one event per API call, per token consumed, per GPU second, per row processed, whatever your unit of value actually is. Metronome is designed for volumes measured in millions of events, not thousands, and Stripe cites capability up to 100,000 events per second.

3. 3

   You define billable metrics with SQL-style queries over those events, which is the crucial design decision. Rather than pushing pre-aggregated counters, you push raw events and define the aggregation in Metronome, so when your pricing changes you rewrite a query rather than redeploying your product.

4. 4

   You build the commercial layer on top: rate cards holding your list prices, contracts that attach a customer to a rate card with overrides, commitments where a customer prepays for a volume at a discount, credit grants that burn down, minimums, and per-customer amendments. Self-serve customers and negotiated enterprise contracts run through the same pricing spine.

5. 5

   Metronome produces invoices and exposes both the running total and the underlying detail through APIs and embeddable dashboards, so your customers see spend accruing rather than discovering it. Payment is collected through a processor you connect, natively Stripe, and the accounting side flows out to your CRM, ERP, or data warehouse. Metronome never becomes the merchant of record and touches no tax obligation.

Percentage of billing volume plus a per-event ingestion charge on a self-serve Startup plan, with a negotiated Custom tier. Payment processing is charged separately by whichever processor you connect.

Value assessment: Work it at a $50 average ticket. At $10,000 a month you pay 0.8 percent, which is $80, plus event ingestion; assume a modest 200,000 events for $8, so $88 in Metronome fees. Add roughly $350 in Stripe processing across 200 transactions and you are at $438, an effective rate of 4.38 percent. At $100,000 a month across 2,000 transactions it is $800 plus perhaps $80 of events, plus $3,500 of processing, so $4,380, again 4.38 percent. That is essentially the same as Stripe Billing at 4.2 percent and materially cheaper than Paddle at 6 percent. But the comparison is misleading in both directions. If your pricing is subscription-shaped, Metronome costs slightly more than Stripe Billing for capability you will never use. If your pricing is genuinely consumption-driven, the event charge is the variable that decides everything, and a high-frequency product can find ingestion costing more than the percentage. The real value assessment is not the take rate at all: it is whether metering correctness and contract flexibility are worth an engineering dependency, and for an AI or infrastructure company they usually are.

Setup time

Weeks, not days, and the work is mostly on your side. Instrumenting your product to emit clean, idempotent usage events is the bulk of it. Defining billable metrics, rate cards, and contracts is fast once the events are trustworthy, which is exactly the ordering most teams get wrong.

Learning curve

Steep, and appropriately so. The product assumes you can express your unit economics precisely, write SQL over an event stream, and reason about late-arriving and corrected events. Teams that have not yet decided what they are actually charging for will struggle, because Metronome makes that vagueness explicit rather than hiding it.

Onboarding

Self-serve signup with published pricing on the Startup plan, but realistically most companies engage with the team before production because the implementation is consequential. The Custom tier includes a dedicated account manager and structured onboarding.

Migration notes

Metronome is a rating and metering layer rather than a payment vault, so the card credentials stay with your processor and no subscriber ever re-enters payment details when you adopt or remove it. That is the structural advantage of a billing layer over a merchant of record. What is hard to move is the instrumentation: once your product emits events in Metronome's shape and your pricing lives in its rate cards and contracts, replacing it means rebuilding both. Migrating in typically runs old and new billing in parallel for a cycle or two and reconciles the invoices, which is the only responsible way to change a usage-billing system.

Platforms

Web applicationREST APIEvent ingestion APIEmbeddable billing dashboard components

API

An API-first product where events, billable metrics, rate cards, contracts, commitments, credits, and invoices are all addressable, with webhooks for invoice and threshold events and ingestion designed for idempotency and replay at very high throughput.

Compliance

SOC 2GDPREnterprise security review posture consistent with its customer baseInherits Stripe's compliance programme following the acquisition

Data residency

United States hosted; regional arrangements are a Custom tier conversation.

SSO

SSO and role-based access control for team accounts.

Security notes

Metronome never handles card data or holds funds, since payment collection happens at your connected processor, which keeps it outside PCI scope and outside your money flow. The material risk is data integrity rather than payment security: a billing engine that mis-aggregates events produces wrong invoices, which is why the idempotency and replay design is the security story that actually matters here.

Channels

Email and in-app supportDedicated account manager on the Custom tierEnhanced service levels on negotiated agreements

Documentation

Detailed developer documentation covering event ingestion, billable metric definition, contracts, commitments, credits, and invoicing at docs.metronome.com.

Community

Primarily a direct-relationship vendor rather than a community-driven one, with a substantial body of published writing on usage-based pricing design.

Founded

2019

Headquarters

San Francisco, California

Ownership

Acquired by Stripe; the transaction completed in January 2026

Founders

Scott Woody, Kevin Liu, Ledion Bitincka

Employees

Roughly 100 to 150 at acquisition

Funding

$128M raised across seed through Series C from NEA, Andreessen Horowitz, General Catalyst, Workday Ventures, Activant Capital, and others, before being acquired by Stripe for roughly $1 billion.

Metronome is the best usage-based billing engine available and, for most small businesses, entirely the wrong purchase. It is built for the specific failure mode where consumption is the product, event volumes run into the millions, and enterprise customers negotiate commitments, credits, and rates that no plan catalogue can express, and the customer list of OpenAI, Anthropic, Databricks, and NVIDIA is the strongest validation any vendor in this category can offer. The published Startup plan at 0.8 percent of billing volume plus 4 cents per thousand events makes it genuinely self-serve, which distinguishes it from Orb, Lago, and Togai, all of which route to a sales call. Weigh three things before buying. The event charge, not the percentage, will decide your bill. There is no tax capability at all, so a merchant of record question remains entirely unanswered. And Stripe now owns it, which removes vendor risk and adds strategic risk in equal measure if you had planned to run it over someone else's processor. If your invoices are simple, buy Stripe Billing. If your invoices are the hardest engineering problem in your company, this is what that problem is solved with.

Written by the SaaSTracker editorial team. Awards, when shown, are judged against the published criteria in our methodology.

Metronome holds 1 award from the SaaSTracker editorial program. Badges may be displayed by the vendor; each embed links back to this profile.

<a href="https://saastracker.org/products/metronome"><img src="https://saastracker.org/badges/embed/metronome/innovation-summer-2026.svg" width="180" height="180" alt="Metronome: Innovation, Subscription Billing. SaaSTracker Summer 2026 Awards." /></a>