Skip to content
DevUtils Online

Analytics

cube vs openreplay

openreplay leads by 5.1 · narrow

A

cube

81.6

21,239 stars · license n/a

B · leads

openreplay

86.7

13,157 stars · license n/a

cube versus openreplay is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. cube is written mainly in Rust; openreplay is written mainly in TypeScript. The composite score is 81.6 for cube and 86.7 for openreplay.

cube has 21,239 GitHub stars to openreplay's 13,157, a gap of 8,082 (1.61×). Forks are 2,197 for cube and 891 for openreplay. On the log scale used inside this pair, adoption is 100 versus 95, and the fork community is 100 versus 88.

Push history: cube 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,189 for cube (0.056 per star) and 193 for openreplay (0.015 per star). Issue-health scores are 52 and 84; activity scores are 100 and 100.

cube 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. 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 30 for cube and 30 for openreplay. This is a procurement signal, not legal advice.

Only openreplay is marked self-hostable here (13,157 stars, deploy score 100). cube is not (21,239 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: cube is unpriced in this catalog, openreplay is unpriced in this catalog.

The lead is split. cube is furthest ahead on fork community (100 to 88), while openreplay is furthest ahead on self-hosting (100 to 35). Choose the dimension a rollout cannot compromise on.

openreplay finishes ahead at 86.7 against cube at 81.6, a 5.1 point narrow margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

cube versus openreplay metrics
Signal cube openreplay
GitHub stars 21,239 13,157
Forks 2,197 891
Open issues 1,189 193
Adoption 100 95
Activity 100 100
Community 100 88
Issue health 52 84
License 30 30
Self-hosting 35 100
Composite 81.6 86.7

openreplay

Session replay, cobrowsing and product analytics you can self-host. Best for reproducing issues and iterating on your product.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, cube or openreplay?

cube has more GitHub stars: 21,239 versus 13,157 for openreplay. The gap is 8,082 stars.

Which was updated more recently, cube or openreplay?

Both were last pushed on 17 November 2026.

Can I self-host both cube and openreplay?

Only openreplay is marked self-hostable. cube is not.

Which license is easier to embed in a commercial product, cube or openreplay?

cube 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. 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.

Who wins the cube vs openreplay score?

openreplay scores 86.7 and cube scores 81.6. This page calls that a narrow lead for openreplay.

Related comparisons