A · leads
influxdb
94.7
31,816 stars · Apache-2.0
Databases
influxdb leads by 14.1 · clear
A · leads
94.7
31,816 stars · Apache-2.0
B
80.6
25,561 stars · license n/a
influxdb versus SpacetimeDB is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in Rust. The composite score is 94.7 for influxdb and 80.6 for SpacetimeDB.
influxdb has 31,816 GitHub stars to SpacetimeDB's 25,561, a gap of 6,255 (1.24×). Forks are 3,826 for influxdb and 1,121 for SpacetimeDB. On the log scale used inside this pair, adoption is 100 versus 98, and the fork community is 100 versus 85.
Push history: influxdb was last pushed on 17 November 2026 (0 days ago), and SpacetimeDB was last pushed on 17 November 2026 (0 days ago). Open issues stand at 2,175 for influxdb (0.068 per star) and 984 for SpacetimeDB (0.038 per star). Issue-health scores are 52 and 70; activity scores are 100 and 100.
influxdb 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. 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. License scores in this pair are 96 for influxdb and 30 for SpacetimeDB. This is a procurement signal, not legal advice.
Only influxdb is marked self-hostable here (31,816 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: influxdb is open source, SpacetimeDB is unpriced in this catalog.
The lead is split. influxdb is furthest ahead on license flexibility (96 to 30), while SpacetimeDB is furthest ahead on issue health (70 to 52). Choose the dimension a rollout cannot compromise on.
influxdb finishes ahead at 94.7 against SpacetimeDB at 80.6, a 14.1 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 | influxdb | SpacetimeDB |
|---|---|---|
| GitHub stars | 31,816 | 25,561 |
| Forks | 3,826 | 1,121 |
| Open issues | 2,175 | 984 |
| Adoption | 100 | 98 |
| Activity | 100 | 100 |
| Community | 100 | 85 |
| Issue health | 52 | 70 |
| License | 96 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 94.7 | 80.6 |
Scalable datastore for metrics, events, and real-time analytics
Development at the speed of light
influxdb has more GitHub stars: 31,816 versus 25,561 for SpacetimeDB. The gap is 6,255 stars.
Both were last pushed on 17 November 2026.
Only influxdb is marked self-hostable. SpacetimeDB is not.
influxdb 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
influxdb scores 94.7 and SpacetimeDB scores 80.6. This page calls that a clear lead for influxdb.