A · leads
lago
93.1
10,891 stars · AGPL-3.0
Analytics
lago leads by 2.2 · narrow
A · leads
93.1
10,891 stars · AGPL-3.0
B
90.9
13,328 stars · AGPL-3.0
lago versus rybbit is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. lago is written mainly in Go; rybbit is written mainly in TypeScript. The composite score is 93.1 for lago and 90.9 for rybbit.
rybbit has 13,328 GitHub stars to lago's 10,891, a gap of 2,437 (1.22×). Forks are 798 for lago and 791 for rybbit. On the log scale used inside this pair, adoption is 98 versus 100, and the fork community is 100 versus 100.
Push history: lago was last pushed on 17 November 2026 (0 days ago), and rybbit was last pushed on 13 November 2026 (4 days ago). Open issues stand at 17 for lago (0.002 per star) and 212 for rybbit (0.016 per star). Issue-health scores are 96 and 84; activity scores are 100 and 92.
Both lago and rybbit are listed as AGPL-3.0. A network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. The license score is therefore level at 52 versus 52, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Analytics, both lago (10,891 stars) and rybbit (13,328 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: lago is open source, rybbit is open source.
The lead is split. lago is furthest ahead on issue health (96 to 84), while rybbit is furthest ahead on adoption (100 to 98). Choose the dimension a rollout cannot compromise on.
lago finishes ahead at 93.1 against rybbit at 90.9, a 2.2 point narrow margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | lago | rybbit |
|---|---|---|
| GitHub stars | 10,891 | 13,328 |
| Forks | 798 | 791 |
| Open issues | 17 | 212 |
| Adoption | 98 | 100 |
| Activity | 100 | 92 |
| Community | 100 | 100 |
| Issue health | 96 | 84 |
| License | 52 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 93.1 | 90.9 |
Open Source Metering and Usage Based Billing API ⭐️ Consumption tracking, Subscription management, Pricing iterations, Payment orchestration & Revenue analytics
🐸 Rybbit - open-source and privacy-friendly alternative to Google Analytics that is 10x more intuitive.
rybbit has more GitHub stars: 13,328 versus 10,891 for lago. The gap is 2,437 stars.
lago was pushed more recently: 17 November 2026 versus 13 November 2026 for rybbit. That is 4 days apart.
Yes. This catalog marks both lago and rybbit as self-hostable. Confirm each project's deploy docs before you plan a migration.
lago is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. rybbit is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
lago scores 93.1 and rybbit scores 90.9. This page calls that a narrow lead for lago.