A · leads
lago
90.4
10,891 stars · AGPL-3.0
Analytics
lago leads by 5.6 · narrow
A · leads
90.4
10,891 stars · AGPL-3.0
B
84.8
23,865 stars · license n/a
lago versus timescaledb 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; timescaledb is written mainly in C. The composite score is 90.4 for lago and 84.8 for timescaledb.
timescaledb has 23,865 GitHub stars to lago's 10,891, a gap of 12,974 (2.19×). Forks are 798 for lago and 1,188 for timescaledb. On the log scale used inside this pair, adoption is 92 versus 100, and the fork community is 94 versus 100.
Push history: lago was last pushed on 17 November 2026 (0 days ago), and timescaledb was last pushed on 17 November 2026 (0 days ago). Open issues stand at 17 for lago (0.002 per star) and 476 for timescaledb (0.020 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. timescaledb is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. License scores in this pair are 52 for lago and 30 for timescaledb. This is a procurement signal, not legal advice.
Only lago is marked self-hostable here (10,891 stars, deploy score 100). timescaledb is not (23,865 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: lago is open source, timescaledb is unpriced in this catalog.
The lead is split. lago is furthest ahead on self-hosting (100 to 35), while timescaledb is furthest ahead on adoption (100 to 92). Choose the dimension a rollout cannot compromise on.
lago finishes ahead at 90.4 against timescaledb at 84.8, a 5.6 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 | timescaledb |
|---|---|---|
| GitHub stars | 10,891 | 23,865 |
| Forks | 798 | 1,188 |
| Open issues | 17 | 476 |
| Adoption | 92 | 100 |
| Activity | 100 | 100 |
| Community | 94 | 100 |
| Issue health | 96 | 84 |
| License | 52 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 90.4 | 84.8 |
Open Source Metering and Usage Based Billing API ⭐️ Consumption tracking, Subscription management, Pricing iterations, Payment orchestration & Revenue analytics
A time-series database for high-performance real-time analytics packaged as a Postgres extension
timescaledb has more GitHub stars: 23,865 versus 10,891 for lago. The gap is 12,974 stars.
Both were last pushed on 17 November 2026.
Only lago is marked self-hostable. timescaledb is not.
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. timescaledb is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
lago scores 90.4 and timescaledb scores 84.8. This page calls that a narrow lead for lago.