A · level
GrowthBook
93.9
8,603 stars · MIT
Analytics
Too close to call · 93.9 to 93.6
A · level
93.9
8,603 stars · MIT
B · level
93.6
10,891 stars · AGPL-3.0
GrowthBook versus lago is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. GrowthBook is written mainly in TypeScript; lago is written mainly in Go. The composite score is 93.9 for GrowthBook and 93.6 for lago.
lago has 10,891 GitHub stars to GrowthBook's 8,603, a gap of 2,288 (1.27×). Forks are 906 for GrowthBook and 798 for lago. On the log scale used inside this pair, adoption is 98 versus 100, and the fork community is 100 versus 98.
Push history: GrowthBook 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 918 for GrowthBook (0.107 per star) and 17 for lago (0.002 per star). Issue-health scores are 52 and 96; activity scores are 100 and 100.
GrowthBook 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 GrowthBook and 52 for lago. This is a procurement signal, not legal advice.
In Analytics, both GrowthBook (8,603 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: GrowthBook is freemium, lago is open source.
The lead is split. GrowthBook 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.
Composite score: GrowthBook 93.9, lago 93.6. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
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 | GrowthBook | lago |
|---|---|---|
| GitHub stars | 8,603 | 10,891 |
| Forks | 906 | 798 |
| Open issues | 918 | 17 |
| Adoption | 98 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 98 |
| Issue health | 52 | 96 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 93.9 | 93.6 |
GrowthBook is a feature-flag and experimentation tool. It is aimed at product teams that want A/B tests and flags without sending every decision to a closed vendor.
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,603 for GrowthBook. The gap is 2,288 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both GrowthBook and lago as self-hostable. Confirm each project's deploy docs before you plan a migration.
GrowthBook 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.
Neither tool clears a one-point margin. GrowthBook scores 93.9 and lago scores 93.6.