A
paradedb
90.8
9,535 stars · AGPL-3.0
Analytics
uPlot leads by 6.9 · narrow
A
90.8
9,535 stars · AGPL-3.0
B · leads
97.7
10,650 stars · MIT
paradedb versus uPlot 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; uPlot is written mainly in JavaScript. The composite score is 90.8 for paradedb and 97.7 for uPlot.
uPlot has 10,650 GitHub stars to paradedb's 9,535, a gap of 1,115 (1.12×). Forks are 515 for paradedb and 472 for uPlot. On the log scale used inside this pair, adoption is 99 versus 100, and the fork community is 100 versus 99.
Push history: paradedb was last pushed on 17 November 2026 (0 days ago), and uPlot was last pushed on 17 November 2026 (0 days ago). Open issues stand at 284 for paradedb (0.030 per star) and 132 for uPlot (0.012 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. uPlot is listed as MIT, 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. License scores in this pair are 52 for paradedb and 96 for uPlot. This is a procurement signal, not legal advice.
In Analytics, both paradedb (9,535 stars) and uPlot (10,650 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: paradedb is open source, uPlot is open source.
The lead is split. paradedb is furthest ahead on fork community (100 to 99), while uPlot is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
uPlot finishes ahead at 97.7 against paradedb at 90.8, a 6.9 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 | uPlot |
|---|---|---|
| GitHub stars | 9,535 | 10,650 |
| Forks | 515 | 472 |
| Open issues | 284 | 132 |
| Adoption | 99 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 99 |
| Issue health | 70 | 84 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 90.8 | 97.7 |
One Postgres for your application data, full-text search, vector retrieval, and aggregations. Home of the pg_search extension.
📈 A small, fast chart for time series, lines, areas, ohlc & bars
uPlot has more GitHub stars: 10,650 versus 9,535 for paradedb. The gap is 1,115 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both paradedb and uPlot as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. uPlot is listed as MIT, 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
uPlot scores 97.7 and paradedb scores 90.8. This page calls that a narrow lead for uPlot.