A · leads
starrocks
90.7
12,261 stars · Apache-2.0
Analytics
starrocks leads by 7.3 · clear
A · leads
90.7
12,261 stars · Apache-2.0
B
83.4
23,865 stars · license n/a
starrocks versus timescaledb is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. starrocks is written mainly in Java; timescaledb is written mainly in C. The composite score is 90.7 for starrocks and 83.4 for timescaledb.
timescaledb has 23,865 GitHub stars to starrocks's 12,261, a gap of 11,604 (1.95×). Forks are 2,679 for starrocks and 1,188 for timescaledb. On the log scale used inside this pair, adoption is 93 versus 100, and the fork community is 100 versus 90.
Push history: starrocks 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 1,753 for starrocks (0.143 per star) and 476 for timescaledb (0.020 per star). Issue-health scores are 34 and 84; activity scores are 100 and 100.
starrocks 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. 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 96 for starrocks and 30 for timescaledb. This is a procurement signal, not legal advice.
Only starrocks is marked self-hostable here (12,261 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: starrocks is open source, timescaledb is unpriced in this catalog.
The lead is split. starrocks is furthest ahead on license flexibility (96 to 30), while timescaledb is furthest ahead on issue health (84 to 34). Choose the dimension a rollout cannot compromise on.
starrocks finishes ahead at 90.7 against timescaledb at 83.4, a 7.3 point clear 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 | starrocks | timescaledb |
|---|---|---|
| GitHub stars | 12,261 | 23,865 |
| Forks | 2,679 | 1,188 |
| Open issues | 1,753 | 476 |
| Adoption | 93 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 90 |
| Issue health | 34 | 84 |
| License | 96 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 90.7 | 83.4 |
The world's fastest open query engine for sub-second analytics both on and off the data lakehouse. With the flexibility to support nearly any scenario, StarRocks provides best-in-class performance for multi-dimensional analytics, real-time analytics, and ad-hoc queries. A Linux Foundation project.
A time-series database for high-performance real-time analytics packaged as a Postgres extension
timescaledb has more GitHub stars: 23,865 versus 12,261 for starrocks. The gap is 11,604 stars.
Both were last pushed on 17 November 2026.
Only starrocks is marked self-hostable. timescaledb is not.
starrocks 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. 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.
starrocks scores 90.7 and timescaledb scores 83.4. This page calls that a clear lead for starrocks.