A
lago
93.0
10,891 stars · AGPL-3.0
Analytics
partytown leads by 3.2 · narrow
A
93.0
10,891 stars · AGPL-3.0
B · leads
96.2
13,817 stars · MIT
lago versus partytown 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; partytown is written mainly in TypeScript. The composite score is 93.0 for lago and 96.2 for partytown.
partytown has 13,817 GitHub stars to lago's 10,891, a gap of 2,926 (1.27×). Forks are 798 for lago and 460 for partytown. On the log scale used inside this pair, adoption is 98 versus 100, and the fork community is 100 versus 92.
Push history: lago was last pushed on 17 November 2026 (0 days ago), and partytown was last pushed on 09 November 2026 (7 days ago). Open issues stand at 17 for lago (0.002 per star) and 1 for partytown (0.000 per star). Issue-health scores are 96 and 96; activity scores are 100 and 92.
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. partytown 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 partytown. This is a procurement signal, not legal advice.
In Analytics, both lago (10,891 stars) and partytown (13,817 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, partytown is open source.
The lead is split. lago is furthest ahead on fork community (100 to 92), while partytown is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
partytown finishes ahead at 96.2 against lago at 93.0, a 3.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 | partytown |
|---|---|---|
| GitHub stars | 10,891 | 13,817 |
| Forks | 798 | 460 |
| Open issues | 17 | 1 |
| Adoption | 98 | 100 |
| Activity | 100 | 92 |
| Community | 100 | 92 |
| Issue health | 96 | 96 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 93.0 | 96.2 |
Open Source Metering and Usage Based Billing API ⭐️ Consumption tracking, Subscription management, Pricing iterations, Payment orchestration & Revenue analytics
Relocate resource intensive third-party scripts off of the main thread and into a web worker. 🎉
partytown has more GitHub stars: 13,817 versus 10,891 for lago. The gap is 2,926 stars.
lago was pushed more recently: 17 November 2026 versus 09 November 2026 for partytown. That is 7 days apart.
Yes. This catalog marks both lago and partytown 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. partytown 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.
partytown scores 96.2 and lago scores 93.0. This page calls that a narrow lead for partytown.