A · leads
Matomo
90.9
22,032 stars · GPL-3.0
Analytics
Matomo leads by 4.8 · narrow
A · leads
90.9
22,032 stars · GPL-3.0
B
86.1
13,157 stars · license n/a
Matomo versus openreplay is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Matomo is written mainly in PHP; openreplay is written mainly in TypeScript. The composite score is 90.9 for Matomo and 86.1 for openreplay.
Matomo has 22,032 GitHub stars to openreplay's 13,157, a gap of 8,875 (1.67×). Forks are 2,938 for Matomo and 891 for openreplay. On the log scale used inside this pair, adoption is 100 versus 95, and the fork community is 100 versus 85.
Push history: Matomo was last pushed on 17 November 2026 (0 days ago), and openreplay was last pushed on 17 November 2026 (0 days ago). Open issues stand at 2,563 for Matomo (0.116 per star) and 193 for openreplay (0.015 per star). Issue-health scores are 52 and 84; activity scores are 100 and 100.
Matomo is listed as GPL-3.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. 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. License scores in this pair are 64 for Matomo and 30 for openreplay. This is a procurement signal, not legal advice.
In Analytics, both Matomo (22,032 stars) and openreplay (13,157 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: Matomo is open source, openreplay is unpriced in this catalog.
The lead is split. Matomo is furthest ahead on license flexibility (64 to 30), while openreplay is furthest ahead on issue health (84 to 52). Choose the dimension a rollout cannot compromise on.
Matomo finishes ahead at 90.9 against openreplay at 86.1, a 4.8 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 | Matomo | openreplay |
|---|---|---|
| GitHub stars | 22,032 | 13,157 |
| Forks | 2,938 | 891 |
| Open issues | 2,563 | 193 |
| Adoption | 100 | 95 |
| Activity | 100 | 100 |
| Community | 100 | 85 |
| Issue health | 52 | 84 |
| License | 64 | 30 |
| Self-hosting | 100 | 100 |
| Composite | 90.9 | 86.1 |
Matomo is a web analytics platform built as a privacy-oriented alternative to Google Analytics. It has a long plugin history and is designed to run on your own server.
Session replay, cobrowsing and product analytics you can self-host. Best for reproducing issues and iterating on your product.
Matomo has more GitHub stars: 22,032 versus 13,157 for openreplay. The gap is 8,875 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both Matomo and openreplay as self-hostable. Confirm each project's deploy docs before you plan a migration.
Matomo is listed as GPL-3.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Matomo scores 90.9 and openreplay scores 86.1. This page calls that a narrow lead for Matomo.