A
lago
88.9
10,891 stars · AGPL-3.0
Analytics
Plausible leads by 4.9 · narrow
A
88.9
10,891 stars · AGPL-3.0
B · leads
93.8
29,871 stars · AGPL-3.0
lago versus Plausible 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; Plausible is written mainly in Elixir. The composite score is 88.9 for lago and 93.8 for Plausible.
Plausible has 29,871 GitHub stars to lago's 10,891, a gap of 18,980 (2.74×). Forks are 798 for lago and 1,940 for Plausible. On the log scale used inside this pair, adoption is 90 versus 100, and the fork community is 88 versus 100.
Push history: lago was last pushed on 17 November 2026 (0 days ago), and Plausible was last pushed on 17 November 2026 (0 days ago). Open issues stand at 17 for lago (0.002 per star) and 58 for Plausible (0.002 per star). Issue-health scores are 96 and 96; activity scores are 100 and 100.
Both lago and Plausible are listed as AGPL-3.0. A network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. The license score is therefore level at 52 versus 52, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Analytics, both lago (10,891 stars) and Plausible (29,871 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, Plausible is freemium.
Plausible is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is fork community at 12 points (88 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
Plausible finishes ahead at 93.8 against lago at 88.9, a 4.9 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 | Plausible |
|---|---|---|
| GitHub stars | 10,891 | 29,871 |
| Forks | 798 | 1,940 |
| Open issues | 17 | 58 |
| Adoption | 90 | 100 |
| Activity | 100 | 100 |
| Community | 88 | 100 |
| Issue health | 96 | 96 |
| License | 52 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 88.9 | 93.8 |
Open Source Metering and Usage Based Billing API ⭐️ Consumption tracking, Subscription management, Pricing iterations, Payment orchestration & Revenue analytics
Plausible is a lightweight, cookie-less web analytics tool. The community edition can be self-hosted; the company also sells a managed service.
Plausible has more GitHub stars: 29,871 versus 10,891 for lago. The gap is 18,980 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both lago and Plausible 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. Plausible 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.
Plausible scores 93.8 and lago scores 88.9. This page calls that a narrow lead for Plausible.