Lago pricing

About

Lago is an open-source billing and metering platform for usage-based, subscription, and hybrid pricing models. It gives engineering and finance teams the metering, invoicing, payment orchestration, entitlements, and revenue-analytics primitives needed to bill any metric — tokens, GPUs, API calls, seats, credits — without building a billing system from scratch. The product ships in two forms: a free, self-hosted open-source edition (AGPLv3, deployed via Docker) and a single commercial package called Lago Premium, sold through sales conversations and available with either Cloud Deployment or Self Hosted Deployment.

Founded by CEO Anh-Tho Chuong and CTO/CPO Raffi Sarkissian, Lago is a Y Combinator (S21) company that has raised roughly $22M total — a $7M seed led by SignalFire and a $15M Series A led by FirstMark Capital, announced 2024-03-14 at a reported ~$100M valuation. The company positions itself as the leading open-source billing platform and reports processing around $829M in invoices monthly. Its open-source repository carries roughly 10.2k GitHub stars under AGPLv3, and its customer base skews toward AI, infrastructure, and fintech — Mistral AI, Synthesia, Groq, PayPal, Swan, and Laravel are named references.

Lago competes with closed-source billing infrastructure such as Stripe Billing, Chargebee, and the newer usage-billing wave like Metronome and Orb. Its differentiator is the open-core posture: teams worried about vendor lock-in, data residency, or wanting to inspect and self-host the billing engine can run the full open-source edition for free, then graduate to Lago Premium for the managed platform, premium features, and supported deployment — on Lago Cloud or self-hosted. For broader context, see how peers structure the freemium pricing trade-off and the wider pricing blueprint.

Pricing summary : free self-hosted open source vs quote-only Lago Premium

Lago runs an open-core model with two distinct paths. The free path is the self-hosted open-source edition — AGPLv3, run on your own infrastructure via Docker, with no license fee, reachable only through the “Deploy open source” link to GitHub. The paid path is now a single commercial package, Lago Premium, which is quote-only: the pricing page publishes no dollar amounts and routes the one column (“Available in Lago Premium”) to “Contact us” / book a demo. This is a deliberately gated, sales-led posture on the commercial product, contrasted against a genuinely free open-source on-ramp.

The dimensions that shape a Lago Premium quote (none of them priced publicly):

• Deployment — Lago Premium is available with Cloud Deployment or Self Hosted Deployment; both sit inside the same package rather than being split across tiers.
• Usage volume — Lago meters events and transactions. Its own docs are more specific about what a Premium quote is sized on: the packages incorporate usage-based dimensions including events ingested, invoices generated, and active customers. No rate card is published for any of them.
• Company stage — Lago’s docs state pricing is “structured in packages that are tailored to specific company stages: early, scaling, or more on the enterprise side,” so the same single Premium package is quoted differently by stage.
• Capped inclusions with add-on overage — multiple billing entities are “included up to a capped number of billing entities, available as an add-on beyond that threshold,” and data pipeline integration is “included up to a capped volume per month, available as an add-on beyond that threshold.” Neither cap is published.
• Paid add-ons (“Add-on available on demand”) — premium ingestion sources, progressive billing, tax integrations, automatic dunning, CRM/CPQ/accounting-software integrations, custom branding, 24x7 incident management, and an assigned solution engineer.
• Professional services — Forward Deployed Services are quoted as a “Custom Professional Service (pricing on demand)”.

What makes this different: the entire commercial catalog is a single quote-only package with no price of any kind on the page — yet a fully free, fully featured-enough open-source edition undercuts the need to ever talk to sales for teams willing to self-host.

Pricing by product

Lago has one product with two ways to consume it: the free self-hosted open-source edition, and the single quote-only commercial package, Lago Premium. No dollar amount appears anywhere on the pricing page — the only column, “Available in Lago Premium,” links to “Contact us.”

Lago platform (self-hosted open source)

Lago Premium (the single commercial package)

Capped inclusions (metered inside Lago Premium)

Add-ons — “Add-on available on demand”

Sales motions across products: PLG / self-serve for the free self-hosted open-source edition (download and run yourself); sales-led and quote-only for Lago Premium and every add-on.

Hidden costs : what running Lago really costs beyond the quote

Because Lago publishes no managed-cloud prices, the meaningful “hidden cost” question splits two ways: what you pay if you self-host the free edition, and what sits outside the base quote if you buy the managed cloud. In both cases the sticker is misleading — “Free” is not zero, and “Contact us” is not all-inclusive.

Archetype A — the self-hoster. A team that runs the free open-source edition pays nothing to Lago, but billing is operationally heavy. The real bill is infrastructure plus engineering time.

The lesson: the free edition removes license fees and lock-in, but billing is the kind of system engineers hate to own — and billing increasingly doubles as an analytics platform, where the most valuable premium features are gated out of the open-source edition, so heavy users tend to graduate to a quote anyway.

Archetype B — the Lago Premium buyer. A scaling AI company buys Lago Premium, but several capabilities its finance team expects sit outside the base package as add-ons available on demand.

The lesson: dunning, tax, accounting connectors, and round-the-clock support are exactly the things a revenue team assumes are “in the box,” yet on Lago’s 2026 matrix each is explicitly marked Add-on available on demand — and two of the included capabilities (billing entities, data pipeline volume) convert into add-ons once you cross an unpublished cap. The realistic bill is the base quote plus a stack of separately-priced modules.

Want to estimate your own Lago bill? Use the Lago pricing calculator to model your costs based on event volume, add-ons, and self-host vs managed deployment.

Pricing evolution : Lago pricing history and changes

Lago has never published a managed-cloud dollar figure on its pricing page — from the 2023 “Open Source / Premium” layout through the Business / Enterprise matrix to the single “Available in Lago Premium” column of 2026-07-22, the paid path has always said “Contact us.” What has moved is the packaging and the naming: a 2022 open-source launch, a 2024 funding-driven feature expansion, a late-2025 redesign that renamed the tiers and pushed several capabilities into paid add-ons, and a 2026 consolidation that undid the tier split entirely and moved the differentiation into add-ons and unpublished caps.

Cadence

Tracked range: 2022-01–2026-07 (29 Wayback snapshots plus two direct captures of getlago.com/pricing). Quarters not listed above were verified stable (0 price changes, 0 SKU additions). No public dollar amount has ever appeared for the managed product.

Notable changes

• 2022-06-02 — v0.1 open-source billing platform launches under AGPLv3; pricing page adopts the “Fair pricing for all — no revenue cut, no lock-in” Open Source (Free) + Premium (Contact us) layout.
• 2022-11-26 — The essay “Engineers’ billing nightmares” reaches 204 points / 120 comments on Hacker News, a major top-of-funnel moment that predates the product’s maturity.
• 2024-03-14 — $22M total funding announced ($15M Series A led by FirstMark, $7M seed led by SignalFire; ~$100M valuation). Pricing FAQ shifts to stage-based packages (early / scaling / enterprise).
• ~Dec 2025 — Pricing page redesigned and rebranded: Premium becomes Business and Enterprise; the free open-source edition is removed from the comparison matrix and pushed to GitHub; progressive billing, dunning, tax, CRM/CPQ, and forward-deployed engineers become add-ons in both paid tiers.
• 2026-07-22 — The two-column matrix collapses into a single “Available in Lago Premium” column, still quote-only. Self-hosting stops being a tier gate (Premium is offered with Cloud or Self Hosted Deployment), 24x7 incident management and an Assigned Solution Engineer unbundle into “Add-on available on demand,” and two previously binary rows gain unpublished caps: multiple billing entities and data pipeline integration are included only “up to a capped number / capped volume per month.”

The 2025–2026 repackaging in detail

The most consequential pricing changes in Lago’s history are not numbers — they are the late-2025 repackaging and the 2026-07-22 consolidation that followed it. For roughly three years (2022–2025) the pricing page ran a stable, ideologically clean two-column story: Open Source (Free) beside Premium (Contact us), with a feature matrix that mostly differentiated “core” from “premium” billing capabilities and a manifesto-style FAQ (“we don’t take a cut on revenue… it felt like rent-seeking”).

The Wayback snapshots bracket the change tightly: the 2025-11 snapshot still shows “Open Source / Premium,” while the 2026-01 snapshot already shows the current “Empowering sophisticated pricing models” layout with Business and Enterprise columns. Three things changed at once:

1. The free edition left the matrix. Where the OSS tier used to sit shoulder-to-shoulder with the paid tier as a first-class comparison column, it is now a “Deploy open source” link to GitHub. The headline pricing decision is now which paid tier, not free vs paid.
2. Add-ons appeared. Capabilities that buyers treat as table-stakes — progressive billing, automatic dunning, tax integrations, CRM/CPQ/accounting connectors, forward-deployed engineers — are now explicitly marked Add-on in both Business and Enterprise, unbundling revenue from the base package.
3. The platform expanded upmarket. Lago AI (on-demand AI agents / billing intelligence) and Lago Embedded (white-label billing) joined the nav, and the matrix gained enterprise signals (multi-entities, audit logs, granular RBAC, self-hosted-with-support on Enterprise).

The through-line: Lago kept its “no public price” posture intact while quietly shifting the commercial narrative from “free OSS vs paid cloud” toward “buy a paid package, then add the modules you need.”

Then, on 2026-07-22, the tier split itself disappeared. Business and Enterprise merged into one column — “Available in Lago Premium” — and the logic of the change follows directly from the 2025 move: once add-ons carry the differentiation, a second tier has nothing left to gate. Three consequences matter for buyers:

1. Self-hosting got cheaper to reach, in principle. Self-hosted deployment with vendor support was the Enterprise gate in the 2026-06 capture; it now ships with Premium itself. A compliance-bound buyer no longer has to buy the top tier to keep billing data in their own VPC — though with no published price, “cheaper” is an inference about packaging, not a verified discount.
2. Support went the other way. Business-hours incident management, a support portal, and implementation guidance are in the package, but 24x7 incident management and an Assigned Solution Engineer — both bundled into Enterprise in June — are now separately-quoted add-ons. Any buyer with a round-the-clock revenue-critical billing pipeline pays for that twice over: once in the base quote, once on the add-on line.
3. Two binary rows became metered ones. Multiple billing entities and data pipeline integration are now “included up to a capped number / capped volume per month, available as an add-on beyond that threshold,” with neither cap published. That converts two yes/no features into unbudgetable variables — the same overage dynamic Lago’s own product exists to manage.

Net effect on evaluation: the decision got simpler to describe (one package, one CTA) and harder to cost. Where a buyer used to compare two quote-only tiers and could at least infer scope from the Enterprise feature list, they now face a single quote whose real total depends on which of ten-plus add-ons they need and where two undisclosed caps fall relative to their volume.

What’s unique : open-core billing with a genuinely free on-ramp

A genuinely free, fully-functional open-source core — not a crippled trial. Lago’s Community edition is the real billing engine under AGPLv3, deployable on your own infrastructure with no license fee and no time limit. This is the opposite of a typical “free tier” that throttles you toward a credit card; it is a complete product you can fork, inspect, and self-host forever. That free path is the whole point of the freemium pricing thesis here — it removes the need to ever talk to sales for teams willing to operate billing themselves.

“No revenue cut” as a pricing manifesto. For years Lago’s pricing FAQ argued, almost ideologically, that taking a percentage of customer revenue is “rent-seeking” — fine for payment processors whose risk scales with volume, but wrong for billing software. So Lago prices on software dimensions (a fixed fee plus metered events/usage), never on a slice of GMV. That positioning is the explicit anti-Stripe-Billing, anti-Chargebee wedge.

The entire commercial catalog is one quote-only package. Since 2026-07-22 the matrix has a single column — “Available in Lago Premium,” priced “Contact us” — with no dollar figure anywhere on the page. A billing company that itself refuses to publish prices is a striking choice, and a deliberate one: Lago sells a tailored quote rather than a public rate card, trading self-serve transparency for sales-led customization. Collapsing two quote-only tiers into one removes the last comparative anchor a buyer had; there is no longer even a cheaper-tier feature list to reason from.

Self-host with support, without buying the top tier. Self-hosted deployment with vendor support was Lago’s sharpest differentiator against closed-source billing, and until mid-2026 it was gated behind Enterprise. As of 2026-07-22 the page states Lago Premium is available with Cloud Deployment and Self Hosted Deployment, so a compliance-bound buyer gets the escape hatch inside the base package rather than as an upsell — a combination Stripe Billing or Chargebee structurally cannot offer at any tier.

Unbundling now reaches the support desk. Since the late-2025 redesign, capabilities like progressive billing, dunning, tax, and accounting connectors have been billed as add-ons rather than bundled. The 2026-07-22 change pushed that logic further than most vendors go: 24x7 incident management and an Assigned Solution Engineer — the things Enterprise tiers usually exist to sell — are now “Add-on available on demand,” while business-hours coverage stays included. Support became a line item rather than a tier. Two more rows — multiple billing entities and data pipeline integration — are included only “up to a capped number / capped volume per month,” with the caps unpublished, so even the included column is soft-metered. Two customers on the identical single package can land at very different totals.

Strengths & weaknesses

Billing UX : the metering, invoicing and analytics controls Lago ships

Named controls surfaced on the pricing-page feature matrix (these are the product capabilities Lago bills against, since Lago itself is the billing tool):

• Billable metrics & usage ingestion — define metered dimensions and ingest events; premium ingestion sources are an “Add-on available on demand.”
• Real-time usage alerts and wallet alerts — threshold alerts on usage as it accrues plus alerts on prepaid wallet balances, so customers catch overages before invoicing.
• Entitlements, plan configuration & plan overrides — manage entitlements directly in billing, configure plans with custom pricing units, and override a plan for a given client.
• Customer portal for your clients — a hosted customer-facing portal for self-service billing visibility, plus prepaid credits.
• Invoice generation, management, grace periods & preview endpoint — generate and manage invoices, set grace periods, issue receipts and credit notes, and render an invoice before it is finalized via the preview endpoint.
• Progressive billing — “Add-on available on demand”, not part of the Premium base.
• Cash collection — payments integration is included; automatic dunning is an “Add-on available on demand.”
• Revenue analytics — a built-in analytics dashboard and lifetime usage calculation; the data pipeline integration is “Included up to a capped volume per month, available as an add-on beyond that threshold.”
• Multiple billing entities — “Included up to a capped number of billing entities, available as an add-on beyond that threshold.”
• Lago AI — AI Billing Assistant, AI Finance Assistant, and an MCP server, all listed as available in Lago Premium.
• Security controls — API key permissions, RBAC + custom role, security logs, API and activity logs (audit trail), and SSO via Okta.
• Support controls — business-hours incident management, a customer portal for support access, and implementation guidance and check-in are included; 24x7 incident management and an Assigned Solution Engineer are each an “Add-on available on demand.”
• Deployment & compliance — Lago Premium ships with Cloud Deployment or Self Hosted Deployment; SOC 2 Type II, flexible deployment (on-prem or VPC), SMTP integration included, and custom branding as an “Add-on available on demand.”

Strategic wins : Why Lago’s pricing decisions worked

1. Open source as the top-of-funnel, not a loss leader

Lago made the free, self-hostable AGPLv3 engine the product’s front door. Combined with developer-first content (the 204-point “Engineers’ billing nightmares” HN thread predated product maturity), the open-source on-ramp built distribution and trust before any sales motion existed. For pricing teams, this is the freemium pricing flywheel done deliberately — give away the engine, monetize operation and support. See usage-based pricing fundamentals for the underlying framework.

2. “No revenue cut” turns pricing into positioning

By refusing to take a percentage of customer GMV and pricing only on software dimensions (fixed fee + metered events), Lago converted its rate model into a competitive narrative against Stripe Billing and Chargebee. The message — “billing is software and should be priced as such” — is itself the sales pitch. This is a textbook example of aligning the value metric with how buyers think about fairness, and it resonates with the broader move away from per-user licenses.

3. Self-host-with-support unlocks compliance-bound buyers

Offering a paid self-hosted deployment with an SLA lets Lago sell to fintech, IoT/telco, and regulated buyers who cannot send billing data to a third party — exactly the customers closed-source SaaS billing structurally locks out. It monetizes the lock-in fear instead of triggering it. The 2026-07-22 change made the move sharper: self-hosting is no longer an Enterprise gate but part of Lago Premium itself, so the compliance requirement stops being an upsell trigger and becomes a deployment checkbox — which widens the addressable set of regulated buyers who can say yes without a tier negotiation.

4. Quote-only packaging captures complex, high-value deals

Refusing to publish prices is a real cost (it kills self-serve), but it lets Lago tailor the quote to the messy, high-ACV billing needs of AI and infrastructure companies. For a product whose value is proportional to billing complexity, a sales conversation extracts more than a public rate card would — and the 2026-07-22 consolidation into a single package removes the anchoring problem that two named tiers create, since a buyer can no longer ask to be sized into the cheaper one. Related: how outcome- and usage-based models reward customized, value-aligned packaging.

Areas to improve : Gaps in Lago’s pricing approach

1. Publish at least a starting price or a public range

A billing company that won’t show any price is an ironic friction point, and it forces every evaluator into a sales call before they can budget. The 2026-07-22 consolidation made this worse, not better: with Business and Enterprise gone there is a single “Contact us” and no lower-tier feature list to reason from. A concrete fix: publish a Lago Premium “starting at $X/mo” anchor or a public band by event volume, with bespoke deals still quoted. A single anchor would let buyers self-qualify and reduce the cost-unpredictability and bill-shock anxiety that gated pricing creates.

2. Publish the two caps that now sit inside “included”

As of 2026-07-22, multiple billing entities and data pipeline integration are included only “up to a capped number / capped volume per month, available as an add-on beyond that threshold” — and neither cap appears on the page. That converts two features a buyer would tick as included into unbudgetable variables discovered after signature. The fix is cheap and doesn’t require publishing a rate card: state the numbers (entities included, monthly pipeline volume included), even if the overage price stays on demand.

3. Make the add-on boundaries explicit before the sales call

Marking dunning, tax, CRM connectors — and now 24x7 incident management and an assigned solution engineer — as “Add-on available on demand” without indication of cost means buyers discover the real bill mid-negotiation. Support is the sharpest case: a company running revenue-critical billing will assume round-the-clock coverage is what a premium package buys, and on Lago’s 2026 matrix it explicitly isn’t. A fix: a short, public “what’s in the base package vs add-ons” explainer with at least relative pricing, so finance teams can model total cost the way they can with a transparent usage-based billing vendor — and so Lago practices the pricing transparency it sells.

4. Re-surface the free edition in the comparison

The late-2025 redesign dropped the open-source tier out of the matrix, weakening Lago’s strongest differentiator — that “free” is a real, full product. Now that the paid side is a single column, a two-column comparison (Open source · Lago Premium) would be simpler than the layout Lago has already abandoned, and it would put the genuinely-free path back at the decision point instead of in a “Deploy open source” link at the page footer.

Key takeaways

1. A free open-source core can be a distribution engine, not a discount. Lago gives away the full billing engine under AGPLv3 and monetizes operation, support, and premium features — the open-source product is the top of the funnel, not a watered-down trial.
2. You can make your value metric a moral argument. “No revenue cut, no lock-in” reframes a pricing choice as fairness, turning the rate model itself into the differentiator against Stripe Billing and Chargebee.
3. Repackaging is a pricing change even when no number moves. Lago has never changed a public price, yet the late-2025 rename to Business/Enterprise and the 2026-07-22 collapse of both tiers into one Lago Premium package each materially changed what a buyer gets for their money.
4. If add-ons carry the differentiation, tiers stop earning their keep. Once Lago had moved dunning, tax, connectors and support into “add-on available on demand,” a second named tier had nothing left to gate — so it merged the two. Tiering and modular add-ons are substitutes, not complements; running both means charging twice for the same segmentation.
5. Selling transparency while hiding your own prices is a credibility risk. A billing platform that won’t publish a single dollar figure — and that now caps two “included” features at undisclosed thresholds — invites the exact “black box” criticism it levels at competitors.

UBP implications

1. Software dimensions beat revenue share for infrastructure tools. Pricing on metered events and a fixed fee — rather than a slice of customer GMV — is the credible model for usage-based infrastructure, because it grows with the customer without taxing their success.
2. Open-core is a viable UBP go-to-market when billing is operationally hard. When the product is something engineers hate to build and maintain, “free to self-host, paid to operate and support” converts complexity into a monetization surface.
3. Add-on unbundling is the next lever after the base usage metric — and it eventually eats your tiers. Once a vendor has a usage-priced base, breaking dunning, tax, and integrations into separately-priced modules lets it expand revenue per account without raising the headline rate, at the cost of budget predictability. Lago’s 2026-07-22 collapse of two quote-only tiers into one package shows where that road ends: when modules carry every meaningful gate, named tiers have nothing left to differentiate and get merged away. The same logic then reaches inside the base package — Lago’s “included up to a capped number / capped volume” rows keep a capability in the included column while still metering the heavy users, which monetizes well but turns a yes/no checkbox into an unbudgetable variable for the buyer.

Sources

• Lago pricing page (accessed 2026-07-22)
• Lago book a demo (accessed 2026-07-22)
• Lago docs — FAQ: Pricing (accessed 2026-07-22)
• Lago docs — FAQ: Deployment (accessed 2026-07-22)
• Lago docs — self-hosted overview (accessed 2026-07-22)
• Lago open-source repository (GitHub) (accessed 2026-07-22)
• Lago about page (accessed 2026-07-22)
• Lago documentation (accessed 2026-06-03)

Bottom line

Lago is the rare billing company that gives away its core engine and refuses to publish a managed-cloud price — an open-core, “no revenue cut” stance that turns its pricing philosophy into its marketing. The free AGPLv3 edition is a genuine product, not a trial. On the paid side, the 2026-07-22 consolidation replaced the Business/Enterprise split with one quote-only package, Lago Premium, sold with Cloud or Self Hosted Deployment — which is a genuine win for compliance-bound buyers, since self-hosting with support is no longer a top-tier upsell. But it made the deal easier to describe and harder to cost: the differentiation moved into “add-on available on demand” modules — now including 24x7 incident management and an assigned solution engineer — and into two “included” rows metered against caps the page never states. The model is coherent and credible, but with the last comparative anchor gone, the absence of any public number is the one place Lago doesn’t practice the transparency it preaches.

Want to compare Lago against other billing and monetization infrastructure companies? Browse the pricing blueprint.

Pricing timeline : Major events on a vertical axis

Each milestone below corresponds to a public pricing change, product launch, or material adjustment. Major events use a filled marker; minor adjustments use a faded one.

Business + Enterprise collapse into a single 'Lago Premium' package

Jul 2026

Lago's pricing page drops the two-column Business / Enterprise matrix in favour of one column, 'Available in Lago Premium', still quote-only with no dollar amounts. Self-hosting is no longer an Enterprise gate — Premium is stated as available with Cloud Deployment and Self Hosted Deployment. Support unbundles: business-hours incident management, a support portal and implementation guidance/check-in are included, while 24x7 incident management and an Assigned Solution Engineer become 'Add-on available on demand'. New matrix rows appear for AI Billing Assistant, AI Finance Assistant, MCP server, wallet alerts, prepaid credits, grace period management, issue receipt, security logs, RBAC + custom role and SSO via Okta. Two capabilities gain published caps: multiple billing entities are 'included up to a capped number… available as an add-on beyond that threshold' and data pipeline integration is 'included up to a capped volume per month'.

Two quote-only managed tiers (Business + Enterprise) confirmed

Jun 2026

Lago's pricing page presents two managed cloud plans — Business and Enterprise — both quote-only with no public dollar amounts. Enterprise adds 24/7 support, an assigned solutions engineer, implementation check-ins, multi-entities, and a self-hosted deployment option. The free open-source self-hosted edition remains available off-domain on GitHub (AGPLv3, ~9.8k stars).

Redesign + rebrand: Business / Enterprise tiers, OSS off the matrix, paid add-ons

Dec 2025

Between the Nov 2025 and Jan 2026 snapshots Lago overhauls the pricing page ('Empowering sophisticated pricing models'). The paid path is renamed from Premium into two columns — Business and Enterprise — both quote-only ('Contact us'). The free self-hosted Community/Open-Source edition is dropped from the main matrix and pushed to GitHub. Lago AI and Lago Embedded join the platform; several capabilities become paid add-ons in both tiers: progressive billing, automatic dunning, tax integrations, CRM/CPQ/accounting integrations, and forward-deployed engineers. Verified via Wayback 2025-11 vs 2026-01 snapshots.

Premium feature matrix expands (progressive billing, dunning, SSO, marketplaces)

Feb 2025

Across 2024–2025 the Premium matrix grows: multiple billing entities, dunning & payment retries, progressive billing, custom SQL metrics, Google/Okta SSO, granular API-key management, audit logs, Anrok/Avalara tax, HubSpot/Salesforce CPQ, and AWS/GCP/Azure marketplace listings. Structure unchanged — still Open Source (Free) vs Premium (Contact us). Verified via Wayback 2024-08 and 2025-08 snapshots.

$22M total funding; pricing page adds funding banner and stage-based packages

Mar 2024

Lago announces $22M total funding ($15M Series A led by FirstMark + $7M seed led by SignalFire; ~$100M valuation). The pricing page keeps the Open Source (Free) / Premium (Contact us) two-tier display but adds a funding banner and reframes the FAQ around 'packages tailored to company stages: early, scaling, enterprise.' Source: TechCrunch (2024-03-14) and FirstMark announcement.

Open-source billing v0.1 launches — Open Source (Free) + Premium (quote-only)

Jun 2022

Lago ships v0.1 as an open-source metering and usage-based billing API under AGPLv3 on GitHub. The pricing page settles into a two-column 'Fair pricing for all' layout: Open Source (Free, 'made for small projects') and Premium (Cloud or Self-Hosted, 'On demand / Contact us'). Stated posture: no revenue cut, no lock-in, hybrid fixed-fee + usage quotes, 30-day money-back, 50–75% startup/OSS discounts. (This replaced an unrelated 2021-era data-sync product that had public $50–$1,000/mo tiers.) Verified via Wayback 2023-04 snapshot; launch corroborated by SignalFire investor post and the 204-point HN thread 'Engineers' billing nightmares' (2022-11-26).