A · leads
delta
94.0
9,083 stars · Apache-2.0
Analytics
delta leads by 2.0 · narrow
A · leads
94.0
9,083 stars · Apache-2.0
B
92.0
10,891 stars · AGPL-3.0
delta versus lago is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. delta is written mainly in Scala; lago is written mainly in Go. The composite score is 94.0 for delta and 92.0 for lago.
lago has 10,891 GitHub stars to delta's 9,083, a gap of 1,808 (1.20×). Forks are 2,224 for delta and 798 for lago. On the log scale used inside this pair, adoption is 98 versus 100, and the fork community is 100 versus 87.
Push history: delta was last pushed on 17 November 2026 (0 days ago), and lago was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,061 for delta (0.117 per star) and 17 for lago (0.002 per star). Issue-health scores are 52 and 96; activity scores are 100 and 100.
delta is listed as Apache-2.0, 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 delta and 52 for lago. This is a procurement signal, not legal advice.
In Analytics, both delta (9,083 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: delta is open source, lago is open source.
The lead is split. delta is furthest ahead on license flexibility (96 to 52), while lago is furthest ahead on issue health (96 to 52). Choose the dimension a rollout cannot compromise on.
delta finishes ahead at 94.0 against lago at 92.0, a 2.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 | delta | lago |
|---|---|---|
| GitHub stars | 9,083 | 10,891 |
| Forks | 2,224 | 798 |
| Open issues | 1,061 | 17 |
| Adoption | 98 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 87 |
| Issue health | 52 | 96 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 94.0 | 92.0 |
An open-source storage framework that enables building a Lakehouse architecture with compute engines including Spark, PrestoDB, Flink, Trino, and Hive and APIs
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 9,083 for delta. The gap is 1,808 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both delta and lago as self-hostable. Confirm each project's deploy docs before you plan a migration.
delta is listed as Apache-2.0, 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.
delta scores 94.0 and lago scores 92.0. This page calls that a narrow lead for delta.