lago

getlago/lago

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

Ship status

Still shipping

Pushed in the last 30 days.

Last push
Oct 9, 2026
2 days ago
Ship score
86/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 10,594 → 10,656 (Sep 22 – Oct 6, 2026)
History starts 2026-09-22, the first weekly sample after this repo joined the directory.

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
10.7K
Forks
768
Open issues
30
Watchers
53
Primary language
Go
Created
Feb 28, 2022
Owner
getlago · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. OSI-approved license — GitHub’s own license field, not legal advice. 99 startups in the directory ship primarily in Go.

Topics

#analytics#billing#clickhouse#events#fintech#go#ingestion#invoices#metering#open-source#payments#pricing#pricing-data-science#react#ruby#self-hosted#subscriptions#usage-based-billing

How it got here

What the classifier decided, and when.

Classified as an open-source startup by Jev, TypeSafe’s classifier, on Sep 22, 2026 — os_startup 100%, self-hostable 70%, hosted offering 82%. The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory.

Joined the directory 2026-09-22, found by the weekly discovery job at confidence 1.00. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: shipping — last push 2026-10-09This is the badge for getlago/lago, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/getlago/lago.svg)](https://ossean.com/getlago/lago)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.