A
SpacetimeDB
80.9
25,561 stars · license n/a
Databases
TDengine leads by 11.7 · clear
A
80.9
25,561 stars · license n/a
B · leads
92.6
25,194 stars · AGPL-3.0
SpacetimeDB versus TDengine is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. SpacetimeDB is written mainly in Rust; TDengine is written mainly in C. The composite score is 80.9 for SpacetimeDB and 92.6 for TDengine.
SpacetimeDB has 25,561 GitHub stars to TDengine's 25,194, a gap of 367 (1.01×). Forks are 1,121 for SpacetimeDB and 5,011 for TDengine. On the log scale used inside this pair, adoption is 100 versus 100, and the fork community is 82 versus 100.
Push history: SpacetimeDB was last pushed on 17 November 2026 (0 days ago), and TDengine was last pushed on 15 November 2026 (2 days ago). Open issues stand at 984 for SpacetimeDB (0.038 per star) and 454 for TDengine (0.018 per star). Issue-health scores are 70 and 84; activity scores are 100 and 100.
SpacetimeDB 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. TDengine 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 30 for SpacetimeDB and 52 for TDengine. This is a procurement signal, not legal advice.
Only TDengine is marked self-hostable here (25,194 stars, deploy score 100). SpacetimeDB is not (25,561 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: SpacetimeDB is unpriced in this catalog, TDengine is open source.
The lead is split. SpacetimeDB is furthest ahead on adoption (100 to 100), while TDengine is furthest ahead on self-hosting (100 to 35). Choose the dimension a rollout cannot compromise on.
TDengine finishes ahead at 92.6 against SpacetimeDB at 80.9, a 11.7 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 | SpacetimeDB | TDengine |
|---|---|---|
| GitHub stars | 25,561 | 25,194 |
| Forks | 1,121 | 5,011 |
| Open issues | 984 | 454 |
| Adoption | 100 | 100 |
| Activity | 100 | 100 |
| Community | 82 | 100 |
| Issue health | 70 | 84 |
| License | 30 | 52 |
| Self-hosting | 35 | 100 |
| Composite | 80.9 | 92.6 |
Development at the speed of light
High-performance, scalable time-series database designed for Industrial IoT (IIoT) scenarios
SpacetimeDB has more GitHub stars: 25,561 versus 25,194 for TDengine. The gap is 367 stars.
SpacetimeDB was pushed more recently: 17 November 2026 versus 15 November 2026 for TDengine. That is 2 days apart.
Only TDengine is marked self-hostable. SpacetimeDB is not.
SpacetimeDB 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. TDengine 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.
TDengine scores 92.6 and SpacetimeDB scores 80.9. This page calls that a clear lead for TDengine.