A
Claude-Code-Usage-Monitor
83.1
8,807 stars · MIT
Analytics
lago leads by 10.7 · clear
A
83.1
8,807 stars · MIT
B · leads
93.8
10,891 stars · AGPL-3.0
Claude-Code-Usage-Monitor versus lago is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Claude-Code-Usage-Monitor is written mainly in Python; lago is written mainly in Go. The composite score is 83.1 for Claude-Code-Usage-Monitor and 93.8 for lago.
lago has 10,891 GitHub stars to Claude-Code-Usage-Monitor's 8,807, a gap of 2,084 (1.24×). Forks are 460 for Claude-Code-Usage-Monitor and 798 for lago. On the log scale used inside this pair, adoption is 98 versus 100, and the fork community is 92 versus 100.
Push history: Claude-Code-Usage-Monitor was last pushed on 05 July 2026 (135 days ago), and lago was last pushed on 17 November 2026 (0 days ago). Open issues stand at 40 for Claude-Code-Usage-Monitor (0.005 per star) and 17 for lago (0.002 per star). Issue-health scores are 96 and 96; activity scores are 36 and 100.
Claude-Code-Usage-Monitor is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. 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. License scores in this pair are 96 for Claude-Code-Usage-Monitor and 52 for lago. This is a procurement signal, not legal advice.
In Analytics, both Claude-Code-Usage-Monitor (8,807 stars) and lago (10,891 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: Claude-Code-Usage-Monitor is open source, lago is open source.
The lead is split. Claude-Code-Usage-Monitor is furthest ahead on license flexibility (96 to 52), while lago is furthest ahead on recent activity (100 to 36). Choose the dimension a rollout cannot compromise on.
lago finishes ahead at 93.8 against Claude-Code-Usage-Monitor at 83.1, a 10.7 point clear 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 | Claude-Code-Usage-Monitor | lago |
|---|---|---|
| GitHub stars | 8,807 | 10,891 |
| Forks | 460 | 798 |
| Open issues | 40 | 17 |
| Adoption | 98 | 100 |
| Activity | 36 | 100 |
| Community | 92 | 100 |
| Issue health | 96 | 96 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 83.1 | 93.8 |
Real-time Claude Code usage monitor with predictions and warnings
Open Source Metering and Usage Based Billing API ⭐️ Consumption tracking, Subscription management, Pricing iterations, Payment orchestration & Revenue analytics
lago has more GitHub stars: 10,891 versus 8,807 for Claude-Code-Usage-Monitor. The gap is 2,084 stars.
lago was pushed more recently: 17 November 2026 versus 05 July 2026 for Claude-Code-Usage-Monitor. That is 135 days apart.
Yes. This catalog marks both Claude-Code-Usage-Monitor and lago as self-hostable. Confirm each project's deploy docs before you plan a migration.
Claude-Code-Usage-Monitor is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
lago scores 93.8 and Claude-Code-Usage-Monitor scores 83.1. This page calls that a clear lead for lago.