A
SpacetimeDB
82.5
25,561 stars · license n/a
Databases
Valkey leads by 14.0 · clear
A
82.5
25,561 stars · license n/a
B · leads
96.5
27,730 stars · BSD-3-Clause
SpacetimeDB versus Valkey 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; Valkey is written mainly in C. The composite score is 82.5 for SpacetimeDB and 96.5 for Valkey.
Valkey has 27,730 GitHub stars to SpacetimeDB's 25,561, a gap of 2,169 (1.08×). Forks are 1,121 for SpacetimeDB and 1,540 for Valkey. On the log scale used inside this pair, adoption is 99 versus 100, and the fork community is 96 versus 100.
Push history: SpacetimeDB was last pushed on 17 November 2026 (0 days ago), and Valkey was last pushed on 17 November 2026 (0 days ago). Open issues stand at 984 for SpacetimeDB (0.038 per star) and 1,045 for Valkey (0.038 per star). Issue-health scores are 70 and 70; 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. Valkey is listed as BSD-3-Clause, 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 SpacetimeDB and 96 for Valkey. This is a procurement signal, not legal advice.
Only Valkey is marked self-hostable here (27,730 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, Valkey is open source.
Valkey is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health. The widest gap is license flexibility at 66 points (30 vs 96), and the tightest is issue health at 0 points (70 vs 70).
Valkey finishes ahead at 96.5 against SpacetimeDB at 82.5, a 14.0 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 | Valkey |
|---|---|---|
| GitHub stars | 25,561 | 27,730 |
| Forks | 1,121 | 1,540 |
| Open issues | 984 | 1,045 |
| Adoption | 99 | 100 |
| Activity | 100 | 100 |
| Community | 96 | 100 |
| Issue health | 70 | 70 |
| License | 30 | 96 |
| Self-hosting | 35 | 100 |
| Composite | 82.5 | 96.5 |
Development at the speed of light
Valkey is a Linux Foundation key-value store forked from Redis. It is used as a cache, queue, and ephemeral data store under a permissive license.
Valkey has more GitHub stars: 27,730 versus 25,561 for SpacetimeDB. The gap is 2,169 stars.
Both were last pushed on 17 November 2026.
Only Valkey 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. Valkey is listed as BSD-3-Clause, 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.
Valkey scores 96.5 and SpacetimeDB scores 82.5. This page calls that a clear lead for Valkey.