A · leads
delta
93.4
9,083 stars · Apache-2.0
Analytics
delta leads by 5.1 · narrow
A · leads
93.4
9,083 stars · Apache-2.0
B
88.3
13,157 stars · license n/a
delta versus openreplay is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. delta is written mainly in Scala; openreplay is written mainly in TypeScript. The composite score is 93.4 for delta and 88.3 for openreplay.
openreplay has 13,157 GitHub stars to delta's 9,083, a gap of 4,074 (1.45×). Forks are 2,224 for delta and 891 for openreplay. On the log scale used inside this pair, adoption is 96 versus 100, and the fork community is 100 versus 88.
Push history: delta 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 1,061 for delta (0.117 per star) and 193 for openreplay (0.015 per star). Issue-health scores are 52 and 84; activity scores are 100 and 100.
delta is listed as Apache-2.0, 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. 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 96 for delta and 30 for openreplay. This is a procurement signal, not legal advice.
In Analytics, both delta (9,083 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: delta is open source, openreplay is unpriced in this catalog.
The lead is split. delta is furthest ahead on license flexibility (96 to 30), while openreplay is furthest ahead on issue health (84 to 52). Choose the dimension a rollout cannot compromise on.
delta finishes ahead at 93.4 against openreplay at 88.3, a 5.1 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 | delta | openreplay |
|---|---|---|
| GitHub stars | 9,083 | 13,157 |
| Forks | 2,224 | 891 |
| Open issues | 1,061 | 193 |
| Adoption | 96 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 88 |
| Issue health | 52 | 84 |
| License | 96 | 30 |
| Self-hosting | 100 | 100 |
| Composite | 93.4 | 88.3 |
An open-source storage framework that enables building a Lakehouse architecture with compute engines including Spark, PrestoDB, Flink, Trino, and Hive and APIs
Session replay, cobrowsing and product analytics you can self-host. Best for reproducing issues and iterating on your product.
openreplay has more GitHub stars: 13,157 versus 9,083 for delta. The gap is 4,074 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both delta and openreplay as self-hostable. Confirm each project's deploy docs before you plan a migration.
delta is listed as Apache-2.0, 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. 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.
delta scores 93.4 and openreplay scores 88.3. This page calls that a narrow lead for delta.