A
openreplay
89.8
13,157 stars · license n/a
Analytics
partytown leads by 6.2 · narrow
A
89.8
13,157 stars · license n/a
B · leads
96.0
13,817 stars · MIT
openreplay versus partytown is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in TypeScript. The composite score is 89.8 for openreplay and 96.0 for partytown.
partytown has 13,817 GitHub stars to openreplay's 13,157, a gap of 660 (1.05×). Forks are 891 for openreplay and 460 for partytown. On the log scale used inside this pair, adoption is 100 versus 100, and the fork community is 100 versus 90.
Push history: openreplay was last pushed on 17 November 2026 (0 days ago), and partytown was last pushed on 09 November 2026 (7 days ago). Open issues stand at 193 for openreplay (0.015 per star) and 1 for partytown (0.000 per star). Issue-health scores are 84 and 96; activity scores are 100 and 92.
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. partytown 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 30 for openreplay and 96 for partytown. This is a procurement signal, not legal advice.
In Analytics, both openreplay (13,157 stars) and partytown (13,817 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, partytown is open source.
The lead is split. openreplay is furthest ahead on fork community (100 to 90), while partytown is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
partytown finishes ahead at 96.0 against openreplay at 89.8, a 6.2 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 | openreplay | partytown |
|---|---|---|
| GitHub stars | 13,157 | 13,817 |
| Forks | 891 | 460 |
| Open issues | 193 | 1 |
| Adoption | 100 | 100 |
| Activity | 100 | 92 |
| Community | 100 | 90 |
| Issue health | 84 | 96 |
| License | 30 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 89.8 | 96.0 |
Session replay, cobrowsing and product analytics you can self-host. Best for reproducing issues and iterating on your product.
Relocate resource intensive third-party scripts off of the main thread and into a web worker. 🎉
partytown has more GitHub stars: 13,817 versus 13,157 for openreplay. The gap is 660 stars.
openreplay was pushed more recently: 17 November 2026 versus 09 November 2026 for partytown. That is 7 days apart.
Yes. This catalog marks both openreplay and partytown 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. partytown 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.
partytown scores 96.0 and openreplay scores 89.8. This page calls that a narrow lead for partytown.