A
lago
93.8
10,891 stars · AGPL-3.0
Analytics
uPlot leads by 3.0 · narrow
A
93.8
10,891 stars · AGPL-3.0
B · leads
96.8
10,650 stars · MIT
lago versus uPlot 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; uPlot is written mainly in JavaScript. The composite score is 93.8 for lago and 96.8 for uPlot.
lago has 10,891 GitHub stars to uPlot's 10,650, a gap of 241 (1.02×). Forks are 798 for lago and 472 for uPlot. On the log scale used inside this pair, adoption is 100 versus 100, and the fork community is 100 versus 92.
Push history: lago was last pushed on 17 November 2026 (0 days ago), and uPlot was last pushed on 17 November 2026 (0 days ago). Open issues stand at 17 for lago (0.002 per star) and 132 for uPlot (0.012 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.
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. uPlot 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. License scores in this pair are 52 for lago and 96 for uPlot. This is a procurement signal, not legal advice.
In Analytics, both lago (10,891 stars) and uPlot (10,650 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, uPlot is open source.
The lead is split. lago is furthest ahead on issue health (96 to 84), while uPlot is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
uPlot finishes ahead at 96.8 against lago at 93.8, a 3.0 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 | uPlot |
|---|---|---|
| GitHub stars | 10,891 | 10,650 |
| Forks | 798 | 472 |
| Open issues | 17 | 132 |
| Adoption | 100 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 92 |
| Issue health | 96 | 84 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 93.8 | 96.8 |
Open Source Metering and Usage Based Billing API ⭐️ Consumption tracking, Subscription management, Pricing iterations, Payment orchestration & Revenue analytics
📈 A small, fast chart for time series, lines, areas, ohlc & bars
lago has more GitHub stars: 10,891 versus 10,650 for uPlot. The gap is 241 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both lago and uPlot 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. uPlot 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
uPlot scores 96.8 and lago scores 93.8. This page calls that a narrow lead for uPlot.