Lago vs Orb in 2026: Usage-Based Billing, Credits & TCO
What changed for Lago, Orb and Metronome after the Stripe and Adyen deals, what self-hosting Lago really takes, and when a PostgreSQL credit ledger you own gets cheaper.

On this page

Lago vs Orb is a choice between two kinds of usage based billing software. Lago is open-core and you can host it yourself. Orb is a managed product that Adyen now owns. The short answer: rent one of them while your pricing still changes every month, and model a ledger you own once usage revenue nears $10M a year.
Most teams also weigh Lago vs Metronome and plain Stripe Billing. That got harder in 2026, when payment processors bought both leading enterprise metering vendors within six months.
In January 2026, Stripe completed its acquisition of Metronome, the metering product built around multi-dimensional AI token rate cards and enterprise commits. Five months later, on June 11, Adyen announced a $335M all-cash acquisition of Orb, and the deal closed on July 1, 2026.
Only Lago is still independent. That leaves three paths: rent a cloud that belongs to a processor, self-host Lago's AGPL-3.0 stack (Rails, Go, ClickHouse), or own a usage and credit ledger in PostgreSQL 17 with direct Stripe PaymentIntents and ACH capped at $5 per payment.
As CEO at Idealogic, I review billing architectures across fintech, SaaS development, AI software development, product development, and custom software development. Alongside SaaS pricing models and payment processing software, this guide compares Orb, Lago and Metronome on storage internals, credit locks and ASC 606 deferred revenue, then works a 36-month TCO at $10M a year in usage ARR ($30M over 36 months) and 150M monthly events.
The short version
- Both big metering vendors now belong to a processor. Metronome is Stripe's enterprise tier next to Stripe Billing (0.7% pay-as-you-go fee). Orb is an Adyen subsidiary ($335M, closed July 2026) that pairs SQL metrics and simulations with Adyen acquiring.
- Orb suits RevOps teams that change pricing often: SQL expressions, backdated contract changes and simulations. Lago (AGPL-3.0 OSS plus Launch, Scale and Enterprise cloud plans) isn't tied to a processor and syncs with Stripe, Adyen, GoCardless and others.
- Self-hosting Lago is free to license, not free to run. getlago/lago combines a Rails API, a Go events processor, PostgreSQL, Redis and, at high volume, ClickHouse, all under AGPL-3.0 copyleft. Lago Premium keeps progressive billing, multi-entity billing, the customer portal and dunning.
- In our worked model, the owned ledger comes out $30.6k to $140.1k cheaper. At $10M a year in usage ARR and 150M events a month, 36 months on an owned PG17 FORCE RLS ledger with direct
PaymentIntentscosts $92,400 at CEE rates, against $123,000 for Lago AGPL on EKS, $184,650 for Lago Cloud Enterprise and $232,500 for Orb Enterprise. It also skips $210,000 in 0.7% Stripe Billing fees. Vendor quotes are assumed.
Usage based billing software in 2026: Lago vs Orb vs Metronome
Usage based billing software meters customer events (API calls, tokens), rates them against a price book, and turns them into invoices, credits and revenue entries. Orb and Metronome are managed products owned by Adyen and Stripe; Lago is open-core and self-hostable.
In the model below, one product streaming 150,000,000 events a month ends up with 36-month totals about $140,000 apart. The gap comes from how each vendor ingests events, locks credits, and ties itself to a payment processor.
1. Orb (withorb.com, Adyen): SQL metrics, Simulations & bps pricing
Adyen paid $335M for Orb in a deal that closed in July 2026. Orb is built for RevOps teams that keep reworking hybrid contracts:
- SQL billable metrics and matrices. Your services emit raw JSON (model, region, cache_hit, tokens), and Orb evaluates SQL expressions across model x tier x region rate matrices. No code deploy needed.
- Backdated changes and simulations. A backdated contract edit recomputes the historical usage stream, and Orb's simulations replay 90 days of production telemetry against a candidate price card.
- Adyen alignment and pricing. Orb still syncs with several PSPs and now pairs threshold top-ups with Adyen acquiring. In November 2026, Orb's pricing page listed a self-serve Business plan at $6 per credit (Orb's own billing unit, not the credits you sell) and a custom Enterprise plan. Enterprise terms aren't public, so the figures in our TCO model are assumptions.
2. Lago (getlago.com): Open-core, Go + ClickHouse & AGPL-3.0 limits
Lago has no processor parent after the 2026 deals:
- Rails, Go, ClickHouse and Postgres. Lago's self-hosted stack combines a Rails API, a Go events processor, PostgreSQL, Redis and, at high volume, ClickHouse. Columnar storage compresses event data well, though how well depends on your schema.
- OSS ($0, AGPL-3.0) vs paid plans (Launch, Scale, Enterprise). Lago OSS covers core metering, plans, coupons, basic wallets, and PSP sync. Lago Premium, on Cloud or self-hosted and priced by quote, adds progressive billing, multi-entity setups, the customer portal, dunning, and revenue analytics.
- Self-hosting overhead. If you modify AGPL-3.0 code in a networked SaaS without a commercial license, you owe source disclosure. Running ClickHouse, Postgres, Redis, Rails and Go on Kubernetes also takes about 16 hours a month of SRE work by our estimate.
3. Metronome + Stripe Billing vs Owned PG17 FORCE RLS Metering
- Stripe + Metronome (acquired Jan 2026). Stripe Usage-Based Billing bundles Meters API ingestion inside Stripe Billing's 0.7% pay-as-you-go fee (annual contracts start at $620 a month), and Metronome handles enterprise commits and prepaid credits. On $30M, 0.7% is $210,000 before any card or ACH fees.
- Owned VPC ledger (PG17 FORCE RLS + direct
PaymentIntents). You keepusage_events, integer micro-centcredit_grants, and ASC 606 entries in partitioned PostgreSQL 17, then charge finalized invoices through StripePaymentIntentsor direct ODFI ACH (Plaid vs Stripe). That removes the percentage billing fee, but the build and the compliance work become yours.
Owned credit ledger design: micro-cent metering and deadlock-free AI token burn-down
A micro-cent credit ledger stores every balance as an integer number of 1e-8 dollars, so rating, grants and invoices reconcile exactly.
Across multi-tenant SaaS and transaction management work, custom billing pipelines tend to break on the same three bugs. IEEE 754 floats drift across $0.00015 LLM calls. Parallel streaming workers deadlock when they lock overlapping grants out of order. Retried timeouts charge the customer twice (see RFC 9110 on idempotent methods and Stripe's idempotent requests docs).
PostgreSQL 17 can close all three with BIGINT micro-cents (PostgreSQL numeric types), row-level security, deterministic FOR UPDATE locks and IFRS 15 / ASC 606 revenue columns. These are the decisions that matter:
The burn-down step is the part most teams get wrong. Each streaming completion locks the tenant's active grants in the same order (priority, then expiry, then id), and debits the smaller of each grant's balance and the remaining cost. Two workers billing the same workspace then wait for each other rather than lock in a circle. Whatever cost no grant covers becomes overage on the period's invoice outbox row.
Treating PROMO grants as revenue-free is a modelling choice. The right pattern depends on the credit terms (refundable, expiring, material rights), so check it with your auditors. Card data never touches these tables, and Stripe-hosted fields can keep you within SAQ A scope under PCI DSS v4.0.1 if you meet the SAQ A criteria. Off-session overage charges need a saved payment method on the outbox row (off-session confirm), and none of this volume pays Stripe Billing's 0.7% fee. For the tenant wall itself, see multi-tenant SaaS architecture.
Usage based billing TCO over 36 months: $10M ARR at 150M events/mo
Take a Series B AI or API product over 36 months. It bills $10,000,000 a year in usage ($30,000,000 cumulative) across 1,200 B2B workspaces that stream 150,000,000 metered events a month, and it needs SOC 2 Type II, ASC 606 / IFRS 15 deferred-revenue schedules, and SAML SSO.
Fair warning: Orb Enterprise and Lago's upper tiers are sold by custom quote. The commits and basis points in Options A and B are illustrative assumptions, not published prices, so swap in your own quotes.
Payment rail settlement (direct Stripe PaymentIntents plus ACH capped at $5) is the same across all four options. Routing $30M through standalone Stripe Billing at 0.7% would add $210,000 in software fees. Labor compares Idealogic's $75/hr senior CEE rate with a $165/hr US agency rate (2.2x), set against the 2025 EU whole-economy hourly labour cost benchmark (lc_lci_lev, EUR 34.9 EU, EUR 38.2 euro area) and US DOL / BLS Software Developers (15-1252.00) wage data:
- Option A: Orb Enterprise (assumed $2,800/mo commit + 36 bps on $30M = $5,800/mo):
- Setup (100h @ $75/hr CEE = $7,500; $165/hr US = $16,500): SQL billable metrics, dimensional price groups, commit webhooks, and NetSuite ASC 606 sync.
- 36-mo SaaS ($5,800/mo x 36 = $208,800): $100,800 base ($2,800/mo) + $108,000 volume share (0.36% on $30M, or $3,000/mo) + 6h/mo (216h) ops ($16,200 CEE / $35,640 US) = $232,500 ($260,940 US).
- Option B: Lago Cloud Enterprise (assumed $2,200/mo commit + 27 bps on $30M = $4,450/mo):
- Setup (110h @ $75/hr CEE = $8,250; $165/hr US = $18,150): Event schemas, prepaid wallets, credit notes, customer portal, and PSP webhooks.
- 36-mo SaaS ($4,450/mo x 36 = $160,200): $79,200 base ($2,200/mo) + $81,000 event/volume tier (0.27% on $30M, or $2,250/mo) + 6h/mo (216h) ops ($16,200 CEE / $35,640 US) = $184,650 ($213,990 US).
- Option C: Lago AGPL-3.0 Self-Hosted on AWS EKS (Rails + Go + ClickHouse + PG + Redis + ASC 606 Shims):
- Setup + Missing EE Shims (320h @ $75/hr CEE = $24,000; $165/hr US = $52,800): EKS Helm, HA ClickHouse, Redpanda/Redis, plus custom ASC 606 deferred-revenue exports and shims for the Premium features Lago OSS leaves out.
- 36-mo EKS + Multi-DB ($1,550/mo x 36 = $55,800): HA ClickHouse ($580/mo), RDS Postgres ($340/mo), Redis/Redpanda ($240/mo), and Rails/Go pods ($390/mo) + 16h/mo (576h) SRE ops ($43,200 CEE / $95,040 US) = $123,000 ($203,640 US).
- Option D: Owned PG17 FORCE RLS Metering & Credit Ledger + Direct Stripe PaymentIntents:
- Turnkey build (680h @ $75/hr CEE = $51,000; $165/hr US = $112,200): Partitioned PG17 events, micro-cent
credit_grantsledger, ASC 606 schedules, directPaymentIntents+ ACH outbox, React spend portal, and replay QA. - 36-mo AWS Compute & Storage ($550/mo x 36 = $19,800): Primary PG17 partition delta ($230/mo), Redis quota cache ($130/mo), and Graviton4 pods ($190/mo) + 8h/mo (288h) ledger ops ($21,600 CEE / $47,520 US) = $92,400 ($179,520 US).
- Turnkey build (680h @ $75/hr CEE = $51,000; $165/hr US = $112,200): Partitioned PG17 events, micro-cent
Sensitivity check: Pre-PMF velocity vs Series B payback
- Seed and Series A (under $2M ARR). Rent Orb or Lago Cloud (we budget $2,000 to $3,000 a month) while PMs rework hybrid bundles weekly.
- Series B payback ($10M+ usage ARR). At $75/hr CEE, Option D's $43,500 extra CapEx over Orb ($51,000 - $7,500) divided by $5,100/mo OpEx savings ($6,250/mo vs $1,150/mo) pays back in 8.53 months. Against Lago Cloud it's 11.40 months ($42,750 / $3,750/mo), and against Lago AGPL EKS 16.88 months ($27,000 / $1,600/mo), with no AGPL-3.0 exposure. Even at $165/hr US labor ($179,520), owning still beats Lago AGPL EKS ($203,640), Lago Cloud ($213,990), and Orb ($260,940) in this model.
Usage based billing build costs in 2026: metering and prepaid credit ledgers
Our SaaS development, AI software development, and fintech teams deliver fixed-milestone builds at $75/hr senior CEE rates. A US agency typically charges $165/hr, or 2.2x:
Inside the worked 680-hour ($51,000 CEE vs $112,200 US) owned billing build
- 1. PG17 Events & FORCE RLS (25% / 170h / $12,750 CEE vs $28,050 US): Monthly partitioned
usage_events,(tenant_id, idempotency_key)deduplication, AS RESTRICTIVE walls, and hourly rollups. - 2. Credit Grant Ledger (25% / 170h / $12,750 CEE vs $28,050 US): BIGINT micro-cent promotional, committed, and top-up grants, deterministic FOR UPDATE streaming locks, 80%/100% alerts, and Redis circuit breakers.
- 3. Rating & ASC 606 (20% / 136h / $10,200 CEE vs $22,440 US): Graduated/dimensional rate cards, deferred-revenue journal entries, breakage accounting, and immutable credit memos.
- 4. Direct Stripe PI & ACH (20% / 136h / $10,200 CEE vs $22,440 US): Zero-bps
PaymentIntents+ $5-cap ACH outbox,PaymentElementvaulting aimed at SAQ A scope under PCI DSS v4.0.1, dunning retries, and tax hooks. - 5. Portal & Replay QA (10% / 68h / $5,100 CEE vs $11,220 US): Next.js customer spend & burn-down dashboard, shadow invoice diffing, and 10,000 events/sec load tests.
Stripe buying Metronome and Adyen buying Orb proved that usage metering is now the control plane for payment margin. Once your platform bills ten million dollars a year in AI tokens or API calls, owning a micro-cent PostgreSQL 17 credit ledger over direct PaymentIntents protects both processor neutrality and gross margin.
Shipped Idealogic proof & 5-step CTO decision checklist
We've shipped auditable ledgers and split-payout pipelines to production:
- Creator split payouts (Ugreator): Cross-network usage tracking wired to Stripe Connect split settlements across Instagram, TikTok, and YouTube. See also Finix vs Stripe Connect.
- Mobile banking ledger (C-Bank): Real-time payment confirmations, credit flows, and reporting under PCI DSS v4.0.1 and OWASP MASVS, lifting launch-quarter downloads +30%, MAUs +40%, and cross-service usage +25%.
Five checks settle which usage based billing software fits you in 2026:
- Under $2M ARR and changing rate cards every month? Pick Orb, and remember Adyen owns it now.
- Need a managed product that isn't tied to one PSP? Lago Cloud (Launch or Scale).
- Already all-in on Stripe for enterprise acquiring? Bundle Metronome inside Stripe.
- Self-hosting Lago AGPL-3.0? Budget about 16 hours a month of ClickHouse and Postgres ops (our estimate) and get legal sign-off on AGPL-3.0.
- Past $5M usage ARR, or streaming AI token commits? Model an owned PG17 FORCE RLS ledger: at $10M our worked model puts it at $92,400 over 36 months with no percentage billing fee. Contact our team for a 48-hour billing TCO audit.

CEO and Co-founder at Idealogic. Leading software strategy, systems architecture, and AI-native engineering squads since 2016.
Frequently asked questions
Usage based billing software meters customer events such as API calls or LLM tokens, rates them against a price book, and turns the result into invoices, prepaid credit balances and revenue entries. Orb and Metronome are managed products, now owned by Adyen and Stripe. Lago is open-core, so you can run it in Lago's cloud or host it yourself.
Choose Orb when your finance and RevOps teams need SQL-defined billable metrics, price simulations on historical data, backdated contract changes, and multi-dimensional commit burn-down without running metering clusters, and remember that Adyen has owned Orb since July 2026. Choose Lago when you'd rather stay independent of any one payment processor, want an open-source core you can self-host, or prefer its Cloud Launch, Scale, and Enterprise packages.
Two deals moved independent metering vendors inside payment processors. Stripe completed its acquisition of Metronome in January 2026, which now sits above Stripe Billing's standard Meters API for complex enterprise contracts. Adyen closed its $335 million acquisition of Orb on July 1, 2026. If you route payments through more than one acquirer, check how tightly a billing vendor is tied to its parent before you sign.
Lago's core repository is free to self-host, but two things catch engineering teams off guard. First, Lago uses the GNU AGPLv3 copyleft license, so you must disclose your source if you modify the billing engine and expose it over a network. Second, the self-hosted stack combines a Rails API, a Go events processor, PostgreSQL, Redis and, at high volume, ClickHouse. You run all of that and still don't get Premium features such as progressive billing, multi-entity billing and dunning.
Stripe Billing charges a consolidated 0.7% pay-as-you-go fee on recurring and metered billing volume before credit card interchange or ACH processing fees even begin. Across $10 million in annual usage-billed ARR ($30 million over 36 months), that 0.7% comes to $210,000 for the billing layer alone. AI products feel it more than most, because GPU and LLM inference costs have already eaten into gross margin.
LLM token pricing often bills fractions of a cent, such as $0.00015 per thousand input tokens. Storing fractional rates or wallet balances in IEEE 754 binary floats introduces binary rounding drift that causes customer wallet balances and period-end invoices to diverge by dollars across millions of events. Production ledgers store exact integer micro-cents (one hundred millionth of a dollar) inside 64-bit PostgreSQL BIGINT columns.
An enterprise workspace often holds multiple overlapping credit grants at once, such as an expiring promotional pack, a quarterly committed spend pool, and an annual top-up. If concurrent streaming completions lock grants in arbitrary order, PostgreSQL raises deadlock exceptions under load. Selecting eligible rows using deterministic ORDER BY priority ASC, expires_at ASC, id ASC FOR UPDATE inside a short transaction eliminates circular lock waits.
When an enterprise buyer wires $120,000 upfront for an annual AI credit pool, accounting rules under ASC 606 and IFRS 15 prohibit booking that cash immediately as earned revenue. Your ledger records a contract liability (deferred revenue) first, recognizes revenue as usage events burn down the grant balance, and books breakage separately when unused non-refundable credits expire. The exact pattern depends on the credit terms: whether credits are refundable, when they expire, and whether they carry material rights.
Managed billing wins below about $2 million ARR, when packaging changes every sprint. From roughly $5 million, model an owned ledger. In our worked model at $10 million usage-billed ARR a year ($30 million over 36 months) and 150 million monthly events, a 680-hour owned PostgreSQL 17 FORCE RLS metering and credit ledger at $75 per hour senior CEE rates ($51,000 CapEx, or $112,200 at $165 per hour US rates) brings 36 month TCO to $92,400. That's $30,600 to $140,100 below the Lago and Orb options, whose prices we had to assume because enterprise quotes aren't public.
More from the journal

Paddle vs Lemon Squeezy in 2026: MoR Fees, Stripe & TCO
Paddle vs Lemon Squeezy and Stripe Managed Payments in 2026, compared on fees and 36-month TCO: stacked international and subscription surcharges, merchant of record liability, B2B Net-30 invoicing, PG17 entitlement guards, and the math for a $6M/yr SaaS.

Finix vs Stripe Connect in 2026: PayFac, IC++ & Split TCO
Engineering and 36-month TCO teardown of Finix vs Stripe Connect vs Payrix and Adyen for Platforms in 2026: PayFac-as-a-Service, Interchange++ spreads, PostgreSQL 17 split sub-ledgers, and $108M GMV math.

Anrok vs Avalara in 2026: SaaS Sales Tax, VAT & Stripe Tax
Engineering and 36-month TCO teardown of Anrok vs Avalara vs Stripe Tax in 2026: SaaS and AI token taxability, HRIS physical nexus, EU VIES reverse charge, PostgreSQL tax ledgers, and $18M ARR math.