A · leads
openreplay
90.0
13,157 stars · license n/a
Analytics
openreplay leads by 1.0 · narrow
A · leads
90.0
13,157 stars · license n/a
B
89.0
9,535 stars · AGPL-3.0
openreplay versus paradedb 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; paradedb is written mainly in Rust. The composite score is 90.0 for openreplay and 89.0 for paradedb.
openreplay has 13,157 GitHub stars to paradedb's 9,535, a gap of 3,622 (1.38×). Forks are 891 for openreplay and 515 for paradedb. On the log scale used inside this pair, adoption is 100 versus 97, and the fork community is 100 versus 92.
Push history: openreplay was last pushed on 17 November 2026 (0 days ago), and paradedb was last pushed on 17 November 2026 (0 days ago). Open issues stand at 193 for openreplay (0.015 per star) and 284 for paradedb (0.030 per star). Issue-health scores are 84 and 70; 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. paradedb 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 paradedb. This is a procurement signal, not legal advice.
In Analytics, both openreplay (13,157 stars) and paradedb (9,535 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, paradedb is open source.
The lead is split. openreplay is furthest ahead on issue health (84 to 70), while paradedb is furthest ahead on license flexibility (52 to 30). Choose the dimension a rollout cannot compromise on.
openreplay finishes ahead at 90.0 against paradedb at 89.0, a 1.0 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 | paradedb |
|---|---|---|
| GitHub stars | 13,157 | 9,535 |
| Forks | 891 | 515 |
| Open issues | 193 | 284 |
| Adoption | 100 | 97 |
| Activity | 100 | 100 |
| Community | 100 | 92 |
| Issue health | 84 | 70 |
| License | 30 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 90.0 | 89.0 |
Session replay, cobrowsing and product analytics you can self-host. Best for reproducing issues and iterating on your product.
One Postgres for your application data, full-text search, vector retrieval, and aggregations. Home of the pg_search extension.
openreplay has more GitHub stars: 13,157 versus 9,535 for paradedb. The gap is 3,622 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both openreplay and paradedb 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. paradedb 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.
openreplay scores 90.0 and paradedb scores 89.0. This page calls that a narrow lead for openreplay.