A · leads
rxdb
98.1
23,439 stars · Apache-2.0
Databases
rxdb leads by 1.6 · narrow
A · leads
98.1
23,439 stars · Apache-2.0
B
96.5
27,730 stars · BSD-3-Clause
rxdb versus Valkey is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. rxdb is written mainly in TypeScript; Valkey is written mainly in C. The composite score is 98.1 for rxdb and 96.5 for Valkey.
Valkey has 27,730 GitHub stars to rxdb's 23,439, a gap of 4,291 (1.18×). Forks are 1,185 for rxdb and 1,540 for Valkey. On the log scale used inside this pair, adoption is 98 versus 100, and the fork community is 96 versus 100.
Push history: rxdb 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 67 for rxdb (0.003 per star) and 1,045 for Valkey (0.038 per star). Issue-health scores are 96 and 70; activity scores are 100 and 100.
rxdb 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. 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 96 for rxdb and 96 for Valkey. This is a procurement signal, not legal advice.
In Databases, both rxdb (23,439 stars) and Valkey (27,730 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: rxdb is open source, Valkey is open source.
The lead is split. rxdb is furthest ahead on issue health (96 to 70), while Valkey is furthest ahead on fork community (100 to 96). Choose the dimension a rollout cannot compromise on.
rxdb finishes ahead at 98.1 against Valkey at 96.5, a 1.6 point narrow 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 | rxdb | Valkey |
|---|---|---|
| GitHub stars | 23,439 | 27,730 |
| Forks | 1,185 | 1,540 |
| Open issues | 67 | 1,045 |
| Adoption | 98 | 100 |
| Activity | 100 | 100 |
| Community | 96 | 100 |
| Issue health | 96 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 98.1 | 96.5 |
The local-first database that runs on every JS runtime and replicates with your existing backend - no vendor, no lock-in - https://rxdb.info/
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 23,439 for rxdb. The gap is 4,291 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both rxdb and Valkey as self-hostable. Confirm each project's deploy docs before you plan a migration.
rxdb 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. 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.
rxdb scores 98.1 and Valkey scores 96.5. This page calls that a narrow lead for rxdb.