Skip to content
DevUtils Online

Analytics

timescaledb vs uPlot

uPlot leads by 8.6 · clear

B · leads

uPlot

93.4

10,650 stars · MIT

timescaledb versus uPlot is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. timescaledb is written mainly in C; uPlot is written mainly in JavaScript. The composite score is 84.8 for timescaledb and 93.4 for uPlot.

timescaledb has 23,865 GitHub stars to uPlot's 10,650, a gap of 13,215 (2.24×). Forks are 1,188 for timescaledb and 472 for uPlot. On the log scale used inside this pair, adoption is 100 versus 92, and the fork community is 100 versus 87.

Push history: timescaledb 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 476 for timescaledb (0.020 per star) and 132 for uPlot (0.012 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.

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

Only uPlot is marked self-hostable here (10,650 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: timescaledb is unpriced in this catalog, uPlot is open source.

The lead is split. timescaledb is furthest ahead on fork community (100 to 87), while uPlot is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.

uPlot finishes ahead at 93.4 against timescaledb at 84.8, a 8.6 point clear 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.

timescaledb versus uPlot metrics
Signal timescaledb uPlot
GitHub stars 23,865 10,650
Forks 1,188 472
Open issues 476 132
Adoption 100 92
Activity 100 100
Community 100 87
Issue health 84 84
License 30 96
Self-hosting 35 100
Composite 84.8 93.4

Questions this page answers

Which has more GitHub stars, timescaledb or uPlot?

timescaledb has more GitHub stars: 23,865 versus 10,650 for uPlot. The gap is 13,215 stars.

Which was updated more recently, timescaledb or uPlot?

Both were last pushed on 17 November 2026.

Can I self-host both timescaledb and uPlot?

Only uPlot is marked self-hostable. timescaledb is not.

Which license is easier to embed in a commercial product, timescaledb or uPlot?

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

Who wins the timescaledb vs uPlot score?

uPlot scores 93.4 and timescaledb scores 84.8. This page calls that a clear lead for uPlot.

Related comparisons