Stripe Billing vs Lago: Pick a Billing Stack 2026

Stripe Billing vs Lago comes down to who meters

Stripe Billing and Lago both turn a SaaS price into an invoice, and they do not own the same part of the job. Stripe Billing is still Stripe's subscription and invoicing product. It was not discontinued and it was not renamed. What changed is the usage layer beside it. Stripe has completed its acquisition of Metronome, and its newsroom describes Metronome as the billing engine for the most complex usage-based models, according to Stripe (2026). The same note says Metronome's metering already supported usage at OpenAI, Anthropic, and NVIDIA. The current Billing pricing page then calls Metronome a Stripe product and tells you to contact Metronome for advanced usage-based billing. This guide treats that Metronome fee as Quote-based, because the pricing page does not print a Metronome rate.

Lago is still Lago. It was not folded into Stripe. Get Lago Corp. develops it, and the company had raised a Funding total: $22 million according to TechCrunch (2024), split in that report into a $15 million Series A led by FirstMark and a $7 million seed led by SignalFire. The same 2024 article named Mistral.ai, Together.ai, and Juni as early customers. That is a funding history, not a measure of how many invoices either product sends today.

Usage-based billing means you meter what a customer consumed, apply a price to that usage, and issue an invoice for the period. A subscription fee can sit on the same invoice. The buying choice is which system is allowed to do the metering, which system is allowed to collect the money, and which contract you can explain to finance. TL;DR: stay with Stripe Billing when Stripe already collects and your usage model fits basic meters or a deliberate move to Metronome, and choose Lago when you need the metering core under your own operation or a processor choice, with Premium priced only after a quote.

Key Takeaways

• Stripe Billing is still the product name. Advanced usage-based billing is Metronome, which Stripe has acquired and now lists as its own product, with the fee left as a sales conversation.

• Lago's open-source package has a published software license of no charge, and Premium on cloud or self-hosted deployment is Quote-based.

• Lago does not itself clear the card. Its payment guide lists official connections for Stripe Payments, GoCardless, and Adyen, plus community and custom paths.

• Stripe's pay-monthly tiers carry an annual commitment. Pay-as-you-go has no recurring platform fee, and one-off invoices are outside the Billing percentage.

• Stripe says basic meters remain for simpler usage, and it tells new complex usage designs to start on Metronome.

• Self-hosting Lago means your team runs the servers, backups, and upgrades. A free software license does not pay for that work.

Who this shortlist is for

This page is for a finance lead or an engineering lead at a B2B SaaS company that already sells usage, seats, credits, or a mix, and is close to naming the system of record for the invoice. You are past the slide that says "we might add usage later." You need to know whether the meter, the invoice, and the cash collection live in one vendor account or in two.

Red flags: you need a merchant-of-record contract that files and remits tax as part of the billing fee; you need a public dollar price for Premium from Lago before any sales conversation; you have nobody who can own signed webhooks, and you also refuse an annual Stripe Billing commitment.

An editorial comparison gives Stripe Billing an Editor score: 9.0/10 according to iTechGuides (2026), gives Lago 6.7/10, ranks them 5 and 28 on its invoicing list, and says that on 6 shared checks Stripe led 0, Lago led 1, and 5 were even, on a page last updated 10 October 2026 that also says vendors can pay for ranking positions. Use that only as someone else's rubric. It is not a test of meter accuracy, and this guide does not adopt the rank.

If Chargebee is still on the table, read Stripe Billing versus Chargebee. If Maxio is, read Stripe Billing versus Maxio. If Recurly is, read Recurly versus Stripe Billing. Those pairings answer a different contract question than the one on this page.

How we evaluated this billing choice

The weights below are our buying weights for this reader, not a score Stripe or Lago published. Metering and charge flexibility get 25 points because the search is about usage, not a simple seat plan. Invoice, credit, and dunning control get 20 points because a wrong credit or a missed failed payment shows up in cash. Who actually processes the payment gets 15 points because a billing tool that only calculates can still leave you a second vendor. Deployment and license get 15 points because self-hosting and the AGPL terms change who is on call. Published price and contract length get 15 points because a percentage of volume and a one-year tier are different risks from a quote. Webhooks, human review, and an audit trail get 10 points because finance still has to match the invoice to the product event log.

The points column repeats the weight so a committee can score later. We did not award either vendor a total. A blank commercial term stays blank.

A row in that table is not a product feature claim. It is the question the rest of this page tries to answer from public pages. Where a vendor page lists a capability as an add-on or as contact-sales, the profile says so. Where a limit is described only as "capped" with no number, this page does not invent the cap.

Head-to-head on the buying points

The matrix separates what each vendor states in public docs from the judgment in the paragraphs under it. A check in a marketing table is not the same thing as a limit written into an order form.

Neither column above is an orchestration layer. A configurable design from US Tech Automations can sit above the billing tool you pick: a signed webhook comes in, the flow compares the invoice with the usage file, and a person approves before a credit note or an access change is sent. You need API credentials and an export of the usage events before that flow can run.

Our read of the metering row is the disqualifier for many teams. Stripe's comparison of basic usage and Metronome says basic usage-based billing remains supported for existing users and fits pay-as-you-go models that bill on thresholds. It also says Metronome is the primary usage-based platform for all new integrations. Move to Metronome if you need prepaid credits or credit burndown, enterprise commits or ramp schedules, dimensional or composite pricing, or real-time usage visibility. On that page, basic usage shows prepaid credit drawdown, commits, ramps, dimensional pricing, real-time usage visibility, and real-time credit burndown as absent. Credits on the basic path are reconciled at invoice time, and Stripe says a customer can go past the balance during the cycle. High-volume ingestion on the basic path is marked limited, with Metronome recommended for enterprise volume. Metronome does not cover Stripe Connect, Adaptive Pricing, Workflows, or the Stripe Dashboard on that comparison, and Checkout is marked limited.

Lago's pricing page lists billable metrics, usage ingestion, real-time usage alerts, wallet alerts, entitlements, custom pricing units, plan overrides, a customer portal, and prepaid credits under Premium. Progressive billing, premium ingestion sources, tax integrations, automatic dunning, and several commercial integrations are marked as add-ons. Multiple billing entities and the data pipeline are included up to a cap, and the page does not publish the cap number. Do not treat "included up to a cap" as unlimited.

A review aggregator lists Lago at a Review score: 4.8/5 according to Toolradar (2026), based on 11 G2 reviews, and says it last checked that figure on 17 September 2026. Eleven reviews is a thin sample. It does not outweigh the contract and deployment differences above.

Price cards you can actually read

Two commercial shapes are on the public record. Stripe prints a percentage, four monthly tiers, payment-processing rates, and a small add-on. Lago prints a software license of no charge for the open-source package and does not print a Premium rate. Anything not printed is Quote-based. Pricing checked October 12, 2026.

Stripe's Billing pricing page lists pay-monthly fees of $620, $1,500, $2,950, and $5,750 per month on a one-year contract, paired with monthly Billing-volume caps of $100,000, $250,000, $500,000, and $1,000,000 (that is $700, $1,750, $3,500, and $7,000 if those caps are multiplied by the pay-as-you-go rate), a 0.67% charge on volume above a chosen cap, advertised savings of 11%, 14%, 16%, and 18%, a $10 monthly fee for a custom portal domain, an included basic-meter allowance of 100 million events per month, a maximum of three recovery and retention automations, card processing at 2.9% plus $0.30 per successful charge, ACH direct debit at 0.8% with a $5 cap, no recurring fee on pay-as-you-go, one-off invoices excluded from the Billing percentage, custom pricing left Quote-based, and a Pay-as-you-go rate: 0.7% according to Stripe (2026). Those dollar figures are what that page showed in this session. If your own Stripe agreement names other fees, the agreement controls. Confirm the page for your country before you sign.

The Billing percentage is not the card fee. Pay-as-you-go applies to Billing volume processed on Stripe and off Stripe, and it skips one-off invoices. Card and ACH rates are Stripe Payments, stacked on top when Stripe also collects. Lago's column is Quote-based for Premium because Lago's packaging guide says there is no universal monthly or annual Premium price. The open-source cell is the software license only. Infrastructure, engineering time, and any support contract are extra, and the guide says not to infer them.

The saving column copies the labels on Stripe's pricing page. The middle fee column copies the published tier fees. The second column is the cap multiplied by the pay-as-you-go rate, which is arithmetic, not a second price list Stripe printed. At the exact cap, the monthly tier is the lower published Billing fee. Cross the cap and the page adds 0.67% on the extra volume. Volume above the top published band is Quote-based custom pricing. None of this includes the card or ACH fee, and none of it prices Metronome.

Using only the rates cited above, take an illustrative month that is not a real customer: recurring Billing volume is $100,000, none of it one-off invoices, so the pay-as-you-go fee at 0.7% is $700, while the first pay-monthly tier costs $620 and Stripe advertises an 11% saving on that tier, and $700 minus $620 is $80. If that $100,000 is collected as 200 successful US card charges of $500, card fees are 2.9% of $100,000, which is $2,900, plus 200 times $0.30, which is $60, for $2,960 of card fees on top of the Billing fee. When each of those invoices is paid, Stripe sends invoice.paid, the event Stripe's subscription webhook guide describes as the notice that the invoice was paid and that you can provision access when the subscription is active.

Stripe Billing profile

Best fit: a team that already collects on Stripe, sells subscriptions plus simple usage thresholds, and wants the customer portal, quotes, invoice schedules, and revenue recovery in the same account. Pay-as-you-go fits low or uneven volume because there is no recurring platform fee. The monthly tiers fit a finance lead who wants a known Billing fee up to a known volume and can accept a one-year contract. Basic meters fit an existing integration that bills when usage crosses a threshold and does not need real-time credit burndown.

Limitations, from the pages above, are specific. Advanced usage is a second product conversation even though Metronome now sits inside Stripe, and that fee is Quote-based. Basic meters include a published event allowance and are the wrong place to start a new design that needs dimensional prices, commits, or real-time credit drawdown. One-off invoices do not count in the Billing percentage, so a mix of subscription invoices and manual invoices will not match a back-of-the-envelope percentage of all cash. The recovery tools are real and also capped. A custom domain for the portal is a separate monthly add-on. Metronome's comparison page shows gaps with Connect, Adaptive Pricing, Workflows, and the Dashboard. Card and ACH fees are not included in the Billing percentage.

Implementation starts in the Stripe account you already have. You define products, prices, and, if usage is simple, meters. You register a webhook endpoint in Workbench and verify signatures. The events that matter for this reader are invoice.paid, invoice.payment_failed, and invoice.created. A person should review the first billing cycle before you migrate live subscriptions, and again before you switch a customer from basic meters to Metronome, because both systems can invoice the same Stripe customer if you cut over carelessly. Prerequisites are the Stripe account, the webhook signing secret, and an export of usage events your product already trusts. Primary evidence is the Billing pricing page, the Metronome comparison, and the subscription webhook guide.

Lago profile

Best fit: a team whose pricing changes by dimension, credit wallet, or contract override, and that wants the metering core in a codebase it can read, either on its own infrastructure or on Lago's cloud. It also fits when cash collection must stay with more than one processor. Lago's payment-provider guide lists an exhaustive native set: GoCardless, Stripe Payments, and Adyen as official, Cashfree Payments and Moneyhash as community, plus a custom integration. The same page says you can forward Lago webhooks to another provider, and it names Paddle, Razorpay, and Authorize.net as examples of that pattern. Lago can therefore sit in front of Stripe Payments without replacing Stripe as the processor.

Lago publishes an open-source package under the AGPL-3.0 license with a License fee: $0 according to Lago (2026), while Premium for cloud and Premium for self-hosting are each a custom quote, recorded here as Quote-based. Get Lago Corp. develops the product, and the company was Founded: 2021 according to Lago (2026), by Anh-Tho Chuong and Raffi Sarkissian. The packaging guide is explicit that the zero-dollar figure is the software license. It does not include computers, backups, on-call engineering, or a support agreement. Review the AGPL terms for your own distribution model before you modify the code. That is a legal reading for your counsel, not a conclusion this page can make for you.

Limitations follow from the same pages. Premium prices, included volumes, and service levels live in a proposal, not on a rate card, so a total-cost comparison against Stripe's published tiers is incomplete until that quote arrives. Automatic dunning, tax integrations, progressive billing, premium ingestion, round-the-clock incident cover, an assigned solutions engineer, and forward-deployed services are add-ons or priced on demand. Multiple billing entities and the data pipeline stop at unpublished caps. The open-source path makes your team responsible for upgrades and security configuration. Lago's pricing page lists SOC 2 Type II, role-based access, and deployment on-premises or in a private network as part of the commercial story. Those are claims on that page, not a substitute for the order form.

Implementation is a deployment choice first. On the open-source path you size the database, the event intake, backups, and monitoring, then configure customers, plans, and billable metrics. On Premium cloud, Lago runs the service and you still confirm limits in the quote. Either way you connect one payment provider from the list above, or you build the webhook handoff. When a new invoice is generated, Lago sends invoice.created, as Lago's invoice overview states, and it sends invoice.one_off_created when the invoice is tied to an add-on. A person should review the invoice during the grace-period step the pricing page lists, before the payment provider is told to collect. Prerequisites are the API credentials, the webhook signature check, and a usage export your product team will stand behind. On its pricing page, Lago quotes Timothée Lacroix, CTO of Mistral AI, that Lago kept up with their releases and let them focus on their own work. That is one published quote, not a case study we ran.

Review before the ledger moves

The painful hour is not the vendor demo. It is the morning a usage invoice does not match the event log, and someone has to decide whether to collect, credit, or hold. A proposed US Tech Automations workflow starts when Stripe sends invoice.paid to an endpoint you registered, which is the event its subscription webhook guide ties to a paid invoice. The prerequisite is the webhook signing secret plus a read of amount, currency, and customer. The action compares those fields with the usage export for the same period and parks a mismatch. The output is a review queue. A person approves before any credit note or entitlement change is sent. This is a configurable design, not a live deployment, and it is not a measured result.

A second proposed US Tech Automations workflow starts when Lago emits invoice.created. The prerequisite is an API key that can read the invoice, a checked webhook signature, and a payment-provider connection already chosen from Lago's list. The action holds the invoice while the grace-period review is still open, compares units with the product event log, and writes an exception note. The output is an approval record a person must release before the payment provider collects. The same boundary applies: configurable, with a human review point, and no claim that a customer is running it today.

Building the same path in Zapier, Make, or n8n

The real alternative for many teams is not a second billing suite. It is a scenario in Zapier, Make, or n8n, or a worker your engineers already run. Those tools can keep a run history, retry a failed step, branch on an error, and store an audit trail when you configure them to do so. They do not remove the design work. Your team still has to make a replayed event idempotent so the same paid invoice cannot create two credit notes, decide who is paged, restrict who can edit the scenario, and keep the scenario alive after the person who built it leaves.

A proposed US Tech Automations design could configure one review queue for both the Stripe event and the Lago event, with the same approval before money or access changes, provided the signing secrets and the usage export are already available. That is a different operating shape. It is not a reason to discard a three-step alert that only tells a channel a payment failed and does nothing else to the ledger.

When NOT to use US Tech Automations: the reminders and retries already included with Stripe Billing are enough when every plan is a flat subscription and nobody is matching usage files; a team that self-hosts Lago and already reviews each invoice in Lago's own screens does not gain a control by adding another system to patch; and a short Zapier, Make, or n8n scenario that only notifies a channel on payment failure is the simpler tool when you do not need an approval gate before a credit note.

Mistakes that show up on the first invoice

• Treating the Billing percentage as the whole cost. Card and ACH rates on the same pricing page sit on top when Stripe collects.

• Putting one-off invoices into the Billing-volume math. The pricing page excludes them.

• Treating the open-source license as a hosted Premium subscription. The license figure does not include infrastructure or the Premium quote.

• Starting a new dimensional or prepaid-credit design on basic Stripe meters. Stripe's own comparison sends that design to Metronome.

• Signing a monthly tier without a plan for the month you cross the cap and pick up the higher marginal rate.

• Modifying Lago and shipping it without reading the AGPL terms that apply to your distribution.

• Comparing a Stripe tier fee with a Lago quote that uses a different volume assumption than the one in the order form.

• Cutting over to Metronome while basic usage billing is still invoicing the same customer.

Glossary for the buying meeting

• Billing volume: The base Stripe uses for the Billing percentage. On the pricing page it includes Billing transactions on and off Stripe and excludes one-off invoices.

• Meter: Stripe's basic usage object. Events land on a meter, and the invoice uses that total. The included allowance is the one cited in the pricing section.

• Billable metric: Lago's name for the usage figure a charge prices. The open-source package includes metric configuration.

• Prepaid credits: Usage paid before it is consumed. Stripe points real-time burndown at Metronome. Lago lists prepaid credits on the Premium page.

• Grace period: A Lago Premium item for holding invoice finalization. Confirm the exact rule in the quote. This page does not invent the number of days.

• AGPL-3.0: The license Lago states for the open-source software. Your counsel should read it before you change and ship the code.

• Webhook: A signed notice such as invoice.paid from Stripe or invoice.created from Lago. Your endpoint has to verify it and ignore duplicates.

• Dunning: The follow-up after a failed payment. Stripe includes reminders, Smart Retries, and a capped automation set. Lago lists automatic dunning as a Premium add-on.

Questions to settle before you sign

Is Metronome still a separate product from Stripe Billing?

Stripe has completed the acquisition, and the Billing pricing page treats Metronome as a Stripe product you contact for advanced usage-based billing. Basic meters remain documented for simpler usage. The Metronome price itself is Quote-based on that page.

Does Lago publish a dollar price for Premium?

Premium from Lago is Quote-based on both cloud and self-hosted deployment, so there is no public Premium rate to set next to Stripe's tiers. The open-source software license is a separate line, cited in the Lago profile, and it does not include hosting.

Do one-off invoices count toward Stripe's Billing percentage?

They do not. The pricing page says the Billing percentage includes Billing transactions processed on Stripe and off Stripe, and it excludes one-off invoices. A month full of manual invoices will not produce the percentage a subscription month produces.

Can you self-host Stripe Billing the way you can self-host Lago?

You cannot self-host Stripe Billing. It runs as Stripe cloud. Lago is the product in this pair with a self-hosted open-source package and a self-hosted Premium option that is still Quote-based.

Can Lago collect a card without using Stripe at all?

Lago is not the payment processor. Its guide lists official integrations for Stripe Payments, GoCardless, and Adyen, plus community providers and a custom webhook path, so Stripe is one processor you can attach rather than the only one.

Should a new usage-based product start on Stripe's basic meters?

Start there only when the model is pay-as-you-go usage billed from thresholds and you do not need the items Stripe lists as reasons to move. Stripe says Metronome is the primary platform for all new usage-based integrations, including prepaid credit burndown, commits, ramp schedules, dimensional pricing, and real-time usage visibility.

What to decide this week

Write down who meters, who collects, and which contract you can actually sign. If the meter must understand credits, dimensions, or commits, Stripe's own docs point that work at Metronome and a quote. If the meter must run in your environment or in front of more than one processor, Lago's open-source license is the public software price and Premium is a quote you still have to read. Keep a person between the paid event and any credit note. Then see how US Tech Automations configures this for that review step, with your API credentials and an approval point before the ledger changes.