A · leads
Plausible
93.8
29,871 stars · AGPL-3.0
Analytics
Plausible leads by 1.9 · narrow
A · leads
93.8
29,871 stars · AGPL-3.0
B
91.9
10,650 stars · MIT
Plausible versus uPlot is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Plausible is written mainly in Elixir; uPlot is written mainly in JavaScript. The composite score is 93.8 for Plausible and 91.9 for uPlot.
Plausible has 29,871 GitHub stars to uPlot's 10,650, a gap of 19,221 (2.80×). Forks are 1,940 for Plausible and 472 for uPlot. On the log scale used inside this pair, adoption is 100 versus 90, and the fork community is 100 versus 81.
Push history: Plausible was last pushed on 17 November 2026 (0 days ago), and uPlot was last pushed on 17 November 2026 (0 days ago). Open issues stand at 58 for Plausible (0.002 per star) and 132 for uPlot (0.012 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.
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. uPlot 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 Plausible and 96 for uPlot. This is a procurement signal, not legal advice.
In Analytics, both Plausible (29,871 stars) and uPlot (10,650 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: Plausible is freemium, uPlot is open source.
The lead is split. Plausible is furthest ahead on fork community (100 to 81), while uPlot is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
Plausible finishes ahead at 93.8 against uPlot at 91.9, a 1.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 | Plausible | uPlot |
|---|---|---|
| GitHub stars | 29,871 | 10,650 |
| Forks | 1,940 | 472 |
| Open issues | 58 | 132 |
| Adoption | 100 | 90 |
| Activity | 100 | 100 |
| Community | 100 | 81 |
| Issue health | 96 | 84 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 93.8 | 91.9 |
Plausible is a lightweight, cookie-less web analytics tool. The community edition can be self-hosted; the company also sells a managed service.
📈 A small, fast chart for time series, lines, areas, ohlc & bars
Plausible has more GitHub stars: 29,871 versus 10,650 for uPlot. The gap is 19,221 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Plausible and uPlot as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. uPlot 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.
Plausible scores 93.8 and uPlot scores 91.9. This page calls that a narrow lead for Plausible.