A · leads
dbt
92.9
14,183 stars · Apache-2.0
Analytics
dbt leads by 5.1 · narrow
A · leads
92.9
14,183 stars · Apache-2.0
B
87.8
13,157 stars · license n/a
dbt versus openreplay is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. dbt is written mainly in Rust; openreplay is written mainly in TypeScript. The composite score is 92.9 for dbt and 87.8 for openreplay.
dbt has 14,183 GitHub stars to openreplay's 13,157, a gap of 1,026 (1.08×). Forks are 2,679 for dbt and 891 for openreplay. On the log scale used inside this pair, adoption is 100 versus 99, and the fork community is 100 versus 86.
Push history: dbt 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,915 for dbt (0.135 per star) and 193 for openreplay (0.015 per star). Issue-health scores are 34 and 84; activity scores are 100 and 100.
dbt 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 dbt and 30 for openreplay. This is a procurement signal, not legal advice.
In Analytics, both dbt (14,183 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: dbt is open source, openreplay is unpriced in this catalog.
The lead is split. dbt is furthest ahead on license flexibility (96 to 30), while openreplay is furthest ahead on issue health (84 to 34). Choose the dimension a rollout cannot compromise on.
dbt finishes ahead at 92.9 against openreplay at 87.8, 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 | dbt | openreplay |
|---|---|---|
| GitHub stars | 14,183 | 13,157 |
| Forks | 2,679 | 891 |
| Open issues | 1,915 | 193 |
| Adoption | 100 | 99 |
| Activity | 100 | 100 |
| Community | 100 | 86 |
| Issue health | 34 | 84 |
| License | 96 | 30 |
| Self-hosting | 100 | 100 |
| Composite | 92.9 | 87.8 |
dbt enables data analysts and engineers to transform their data using the same practices that software engineers use to build applications.
Session replay, cobrowsing and product analytics you can self-host. Best for reproducing issues and iterating on your product.
dbt has more GitHub stars: 14,183 versus 13,157 for openreplay. The gap is 1,026 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both dbt and openreplay as self-hostable. Confirm each project's deploy docs before you plan a migration.
dbt 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.
dbt scores 92.9 and openreplay scores 87.8. This page calls that a narrow lead for dbt.