HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
getlago
lago
Go2022–2026
getlago / lago

lago

Open Source Metering and Usage Based Billing API ⭐️ Consumption tracking, Subscription management, Pricing iterations, Payment orchestration & Revenue analytics

30Distinct people
121Mentions
0Explicit recommenders
10.8KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Open Source Metering and Usage Based Billing API ⭐️ Consumption tracking, Subscription management, Pricing iterations, Payment orchestration & Revenue analytics

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 1:56:48 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year121 dated mentions

Observed mentions: 2022-06-01 15:54:31 UTC to 2026-08-16 23:47:45 UTC.

02040602022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 54 mentions; 40 submissions, 14 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 28 mentions; 24 submissions, 4 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 31 mentions; 25 submissions, 6 comments20242025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 6 mentions; 6 submissions, 0 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC544014
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC28244
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC31256
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC202
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC660

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
Lago Agentic-first, open-source monetization infrastructure for AI products Meter tokens, compute, API calls, or any product usage. Turn usage into pricing, credits, entitlements, invoices, payments, and revenue. Use Lago Direct for your own product, or Lago Embedded to power monetization for your customers. Build with your AI agent · Run the AI billing demo · Documentation · Talk to us about Lago Cloud “Lago has been able to follow the pace of our releases and has allowed us to focus on what we do best.” Timothée Lacroix, CTO at Mistral AI · Read the customer story Build with your AI agent Give your coding agent Lago's public documentation, then choose the API, CLI, or MCP for your workflow. Paste this prompt to start: Read https://getlago.com/llms.txt and follow the relevant Lago guides for this project. Use https://swagger.getlago.com/openapi.yaml for exact API fields. Help me design and implement a billing integration. Ask before live access. Your task Start here Build billing into your application REST API and SDKs Inspect billing, run diagnostics, or write scripts Lago CLI Give an assistant tools for live billing data and supported operations Lago MCP server Give your agent current billing and API context Documentation index or documentation MCP These interfaces work independently. Application code uses an SDK or the REST API; no Lago plugin is required. Confirm the target organization and environment, keep API keys out of prompts and source control, and review financial changes before execution. Follow the agent setup guide for connection details and validation, or explore the website overview. To see real usage become a charge locally, run the maintained demo below. See Lago price an AI workload Run the maintained demo from this repository: ./examples/agentic-ai-demo/run.sh It starts the Lago version that matches this checkout, creates a disposable local organization, and prices three illustrative AI requests. Each request sends one input-token event and one output-token event: 3 AI requests 5,000 input tokens x $0.000002 = $0.01 1,250 output tokens x $0.000008 = $0.01 Lago usage total = $0.02 Docker Compose starts an isolated Lago service, then a small script seeds and verifies the example through Lago's API. It retrieves current usage, independently reconciles the result, and retries one transaction to confirm that usage does not increase. Everything stays on your machine; the demo does not access Lago Cloud. The bundled credentials and API key are disposable and only intended for this local demo. Log into http://localhost:8080 with agentic-ai-demo@example.local / agentic-ai-demo-local-password, then open Customers → Agentic AI Demo Customer → Agentic AI Demo subscription → Usage. Requirements: Docker, curl, and jq. If ports 8080 or 3001 are occupied, set LAGO_DEMO_UI_PORT and LAGO_DEMO_API_PORT before running. The demo keeps Lago running so you can inspect the customer, metrics, plan, subscription, events, and usage in the UI. Remove its isolated Compose project and data volume when you are done: ./examples/agentic-ai-demo/run.sh --cleanup Use Claude Code, Codex, or Cursor Open this repository in your coding agent and paste: Run Lago's maintained Agentic AI demo by following this README. Keep it local; do not modify source files or unrelated Docker resources. When it passes, give me the UI URL, token usage and charges, idempotency evidence, and cleanup command. Then offer to connect this agent to Lago's local MCP server. What is Lago? Lago is the programmable system between product usage and revenue. Send events from your application, turn them into billable metrics, apply pricing and entitlements, then generate invoices and collect payments. Usage events -> Metering -> Pricing and credits -> Entitlements -> Invoices -> Payments -> Revenue Use Lago to launch and change pricing without rebuilding billing: tokens by model, input, output, cache, reasoning, or tool call GPU, CPU, storage, and other compute consumption API calls, transactions, seats, active users, or custom events prepaid credits with automatic top-ups subscriptions with allowances, minimum commitments, and overages self-serve plans and negotiated enterprise contracts in the same system Lago is headless and API-first. Your application, internal tools, and agents use the same billing primitives through the REST API, SDKs, webhooks, and MCP server. Product, finance, and operations teams can use the Lago UI when a human interface is faster. How Lago fits into your stack Lago keeps metering and pricing independent from payment processing. Connect Stripe, Adyen, GoCardless, or another provider without making its product catalog your source of truth. Lago Direct and Lago Embedded The same Lago engine supports two operating models: Lago Direct Lago Embedded Who monetizes You monetize your own product Your customers monetize through your platform Experience Your application and teams use Lago through APIs, agent interfaces, and Lago UI Your customers use billing capabilities inside your product through APIs and white-label interfaces Brand Lago powers your billing stack Lago stays behind the scenes under your brand Public example Mistral AI PayPal Lago Direct is the standard way to use Lago: send your own product usage, model your pricing, and bill your customers. Lago Embedded uses the same primitives to let platforms, marketplaces, AI builders, fintech products, and developer tools offer metering and billing to their customers. Both models start with Lago's open-source billing engine and can be paired with Premium deployment, customization, security, and support options. With Lago Embedded, you control the customer experience and which capabilities your users can access. Agentic-first by design Agentic-first means Lago's billing model is available a
Read the full README on GitHub

What Hacker News says

54 sources
AnhTho_FR·Dec 15, 2022Submission

Ask HN: What makes you push through when “no one cares”?

I've been on the founder journey for nearly 2 years now, and I think I was widely unprepared to being the "underdog". I've progressively built muscle around that, with a few mental frameworks and I was wondering what you did? Mine here: https://github.com/getlago/lago/wiki/About-pushing-through-when-%C2%AB-no-one-care… I guess it's different for each person. We keep sharing "tactics" but I think at an early stage, "managing one's emotions" is 80% of the game.
8 points · Open discussion
Hi Sam, OP here. I appreciate the inputs, we're big fans of Stripe at Lago. We operate in the billing space, and are alternatives to home-grown billing systems, Chargebee, Recurly, etc. and Stripe Billing. 1/ Some users use Lago as a complement of Stripe Billing, or don't even consider Stripe Billing, and we built a native integration with Stripe payments. Out of transparency, the first lines we wrote in this post stated that: "Disclaimer: This analysis is based on Stripe’s public pricing as of July 21, 2022. Some merchants may be able to negotiate fees or benefit from grandfathered plans. Lago partners with 'Stripe Payments' and can be used as a complement or replacement of 'Stripe Billing'." 2/ > 'write deliberately-provocative posts to go viral' Thanks for quoting my tweet. I actually shared 2 old articles I wrote in 2021 this week, t
Read the rest
hat made the front page of HN, unrelated to Fintech: - One on my personal blog sharing what I learnt about press relations, main message being 'don't waste money on an agency if you're early stage' because I've seen this happen too often, and too many founders asked me the same questions about this topic [1] I was actually surprised it was read, as HN is known for being more 'engineering oriented' than 'marketing oriented'. - Another one about 'scouts' not being necessarily a good thing for founders, with Sifted (TC for EU) which is a position I stand for as a founder and as an investor, and I think Europe should mature towards this topic [2] The TLDR is: I've been writing about a wide range of topics for a long time, things I like to share, things I stand for and want to have an impact on and was grateful it resonated within my community. Btw I think the HN ring vote is pretty strong, and HN community very 'fierce' (at times), so I don't think we could have got attention by just 'clickbaiting' and attempting to go viral. Like any startup, we're excited to share our vision of the world, and this is why we're writing. Lastly, here are two other examples of content that were intended to spark a discussion in our community (and it did) and don't bring much to Lago as a business: a/ What not to say to someone who has just been laid off [3] I wrote it after my partner was laid off and too many people around him just did not know what to say, which amplified the 'grief'. It reminded me of my personal history of grief, and wrote the post. I received dozens of messages of people who have been laid off recently, or whose friend/closed ones had been fired. Founders reached out to say they would share it with their team (it's not an easy topic to discuss). b/ I recently shared my thought process about moving to the US after YC, as it's a recurring question we have as YC founders based in Europe. This sparked a lot of discussions and helped me iterate on how I approach the question, in a scalable way. I believe other founders learned things by the discussion it sparked, some founders reached out to help me with the US visa etc. Feel free to read it here [4]. Took me some time to write it, but the main ROI was how I've been able to connect with other founders, at the same stage, or 5 steps ahead, and learn from them. And, based on the comments/discussions, I believe other founders in the same situation benefited from this too. My point is: not all content is written in an attempt to go viral, but I just write about what I believe brings value, and it happens to go viral (whatever you mean by that) when it does have an impact. Regarding my tweet, I think a lot of people wonder how to approach HN, and make a lot of rookie mistakes, and I could also write about what I've learned. This would (if I write it successfully) in fine help having better content on HN. YC says 'build something people want', I also happen to (occasionally) write things people want. And there's no better gift for a writer. [1] https://anhtho.substack.com/p/pr-for-startups-is-it-only-for... [2] https://sifted.eu/articles/vc-scout-programme-problems/ [3] https://sifted.eu/articles/what-not-to-say-layoff/ [4] https://github.com/getlago/lago/wiki/Moving-to-the-US-after-...
In Stripe’s real pricing: a primer
AnhTho_FR·Dec 8, 2022Submission

Show HN: AWS – an Open Source framework to build an 'EC2 on-demand' pricing

Hi HN, We've put together a framework showing how to build an on-demand billing system similar to AWS', with charges calculated according to the region and type of instance selected by the customer. It is suitable for companies for which a billable metric can have multiple prices based on its properties, such as cloud computing platforms (see below) and identity verification platforms (e.g. $2 for a bank verification and 3$ for a document verification). It uses Lago's API and UI, which is open-sourced (AGPLv3) https://github.com/getlago/lago
2 points · Open discussion

Showing the 15 most recent of 54 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.