A
openreplay
85.8
13,157 stars · license n/a
Analytics
Plausible leads by 8.0 · clear
A
85.8
13,157 stars · license n/a
B · leads
93.8
29,871 stars · AGPL-3.0
openreplay versus Plausible is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. openreplay is written mainly in TypeScript; Plausible is written mainly in Elixir. The composite score is 85.8 for openreplay and 93.8 for Plausible.
Plausible has 29,871 GitHub stars to openreplay's 13,157, a gap of 16,714 (2.27×). Forks are 891 for openreplay and 1,940 for Plausible. On the log scale used inside this pair, adoption is 92 versus 100, and the fork community is 90 versus 100.
Push history: openreplay 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 193 for openreplay (0.015 per star) and 58 for Plausible (0.002 per star). Issue-health scores are 84 and 96; activity scores are 100 and 100.
openreplay is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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. License scores in this pair are 30 for openreplay and 52 for Plausible. This is a procurement signal, not legal advice.
In Analytics, both openreplay (13,157 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: openreplay is unpriced in this catalog, Plausible is freemium.
Plausible is ahead on every scored dimension that is not level. Level dimensions: recent activity, self-hosting. The widest gap is license flexibility at 22 points (30 vs 52), and the tightest is self-hosting at 0 points (100 vs 100).
Plausible finishes ahead at 93.8 against openreplay at 85.8, a 8.0 point clear 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 | openreplay | Plausible |
|---|---|---|
| GitHub stars | 13,157 | 29,871 |
| Forks | 891 | 1,940 |
| Open issues | 193 | 58 |
| Adoption | 92 | 100 |
| Activity | 100 | 100 |
| Community | 90 | 100 |
| Issue health | 84 | 96 |
| License | 30 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 85.8 | 93.8 |
Session replay, cobrowsing and product analytics you can self-host. Best for reproducing issues and iterating on your product.
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 13,157 for openreplay. The gap is 16,714 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both openreplay and Plausible as self-hostable. Confirm each project's deploy docs before you plan a migration.
openreplay is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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 openreplay scores 85.8. This page calls that a clear lead for Plausible.