A · leads
paradedb
86.5
9,535 stars · AGPL-3.0
Analytics
paradedb leads by 1.7 · narrow
A · leads
86.5
9,535 stars · AGPL-3.0
B
84.8
23,865 stars · license n/a
paradedb versus timescaledb is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. paradedb is written mainly in Rust; timescaledb is written mainly in C. The composite score is 86.5 for paradedb and 84.8 for timescaledb.
timescaledb has 23,865 GitHub stars to paradedb's 9,535, a gap of 14,330 (2.50×). Forks are 515 for paradedb and 1,188 for timescaledb. On the log scale used inside this pair, adoption is 91 versus 100, and the fork community is 88 versus 100.
Push history: paradedb was last pushed on 17 November 2026 (0 days ago), and timescaledb was last pushed on 17 November 2026 (0 days ago). Open issues stand at 284 for paradedb (0.030 per star) and 476 for timescaledb (0.020 per star). Issue-health scores are 70 and 84; activity scores are 100 and 100.
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. timescaledb 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 52 for paradedb and 30 for timescaledb. This is a procurement signal, not legal advice.
Only paradedb is marked self-hostable here (9,535 stars, deploy score 100). timescaledb is not (23,865 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: paradedb is open source, timescaledb is unpriced in this catalog.
The lead is split. paradedb is furthest ahead on self-hosting (100 to 35), while timescaledb is furthest ahead on issue health (84 to 70). Choose the dimension a rollout cannot compromise on.
paradedb finishes ahead at 86.5 against timescaledb at 84.8, a 1.7 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 | paradedb | timescaledb |
|---|---|---|
| GitHub stars | 9,535 | 23,865 |
| Forks | 515 | 1,188 |
| Open issues | 284 | 476 |
| Adoption | 91 | 100 |
| Activity | 100 | 100 |
| Community | 88 | 100 |
| Issue health | 70 | 84 |
| License | 52 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 86.5 | 84.8 |
One Postgres for your application data, full-text search, vector retrieval, and aggregations. Home of the pg_search extension.
A time-series database for high-performance real-time analytics packaged as a Postgres extension
timescaledb has more GitHub stars: 23,865 versus 9,535 for paradedb. The gap is 14,330 stars.
Both were last pushed on 17 November 2026.
Only paradedb is marked self-hostable. timescaledb is not.
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. timescaledb 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.
paradedb scores 86.5 and timescaledb scores 84.8. This page calls that a narrow lead for paradedb.