A · leads
dbt
92.9
14,183 stars · Apache-2.0
Analytics
dbt leads by 6.0 · narrow
A · leads
92.9
14,183 stars · Apache-2.0
B
86.9
9,535 stars · AGPL-3.0
dbt versus paradedb 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 Rust. The composite score is 92.9 for dbt and 86.9 for paradedb.
dbt has 14,183 GitHub stars to paradedb's 9,535, a gap of 4,648 (1.49×). Forks are 2,679 for dbt and 515 for paradedb. On the log scale used inside this pair, adoption is 100 versus 96, and the fork community is 100 versus 79.
Push history: dbt 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 1,915 for dbt (0.135 per star) and 284 for paradedb (0.030 per star). Issue-health scores are 34 and 70; 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. 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 96 for dbt and 52 for paradedb. This is a procurement signal, not legal advice.
In Analytics, both dbt (14,183 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: dbt is open source, paradedb is open source.
The lead is split. dbt is furthest ahead on license flexibility (96 to 52), while paradedb is furthest ahead on issue health (70 to 34). Choose the dimension a rollout cannot compromise on.
dbt finishes ahead at 92.9 against paradedb at 86.9, a 6.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 | dbt | paradedb |
|---|---|---|
| GitHub stars | 14,183 | 9,535 |
| Forks | 2,679 | 515 |
| Open issues | 1,915 | 284 |
| Adoption | 100 | 96 |
| Activity | 100 | 100 |
| Community | 100 | 79 |
| Issue health | 34 | 70 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 92.9 | 86.9 |
dbt enables data analysts and engineers to transform their data using the same practices that software engineers use to build applications.
One Postgres for your application data, full-text search, vector retrieval, and aggregations. Home of the pg_search extension.
dbt has more GitHub stars: 14,183 versus 9,535 for paradedb. The gap is 4,648 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both dbt and paradedb 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. 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.
dbt scores 92.9 and paradedb scores 86.9. This page calls that a narrow lead for dbt.