A · level
dbx
94.7
30,615 stars · Apache-2.0
Databases
Too close to call · 94.7 to 95.1
A · level
94.7
30,615 stars · Apache-2.0
B · level
95.1
27,730 stars · BSD-3-Clause
dbx versus Valkey is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. dbx is written mainly in Rust; Valkey is written mainly in C. The composite score is 94.7 for dbx and 95.1 for Valkey.
dbx has 30,615 GitHub stars to Valkey's 27,730, a gap of 2,885 (1.10×). Forks are 2,788 for dbx and 1,540 for Valkey. On the log scale used inside this pair, adoption is 100 versus 99, and the fork community is 100 versus 92.
Push history: dbx 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 1,733 for dbx (0.057 per star) and 1,045 for Valkey (0.038 per star). Issue-health scores are 52 and 70; activity scores are 100 and 100.
dbx 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 dbx and 96 for Valkey. This is a procurement signal, not legal advice.
In Databases, both dbx (30,615 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: dbx is open source, Valkey is open source.
The lead is split. dbx is furthest ahead on fork community (100 to 92), while Valkey is furthest ahead on issue health (70 to 52). Choose the dimension a rollout cannot compromise on.
Composite score: dbx 94.7, Valkey 95.1. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
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 | dbx | Valkey |
|---|---|---|
| GitHub stars | 30,615 | 27,730 |
| Forks | 2,788 | 1,540 |
| Open issues | 1,733 | 1,045 |
| Adoption | 100 | 99 |
| Activity | 100 | 100 |
| Community | 100 | 92 |
| Issue health | 52 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.7 | 95.1 |
25 MB lightweight cross-platform database client for 100+ databases, including MySQL, PostgreSQL, SQLite, Redis, MongoDB, DuckDB, SQL Server, and Dameng. Built-in AI, MCP Server, CLI, desktop and Docker. | 轻量级跨平台数据库管理工具,支持 MySQL、PostgreSQL、SQLite、Redis、MongoDB、达梦等 100+ 数据库,提供桌面端、Docker、CLI、内置 AI 助手和 MCP。
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.
dbx has more GitHub stars: 30,615 versus 27,730 for Valkey. The gap is 2,885 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both dbx and Valkey as self-hostable. Confirm each project's deploy docs before you plan a migration.
dbx 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.
Neither tool clears a one-point margin. dbx scores 94.7 and Valkey scores 95.1.