A · level
dbx
92.5
30,615 stars · Apache-2.0
Databases
Too close to call · 92.5 to 92.9
A · level
92.5
30,615 stars · Apache-2.0
B · level
92.9
40,739 stars · Apache-2.0
dbx versus tidb 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; tidb is written mainly in Go. The composite score is 92.5 for dbx and 92.9 for tidb.
tidb has 40,739 GitHub stars to dbx's 30,615, a gap of 10,124 (1.33×). Forks are 2,788 for dbx and 6,297 for tidb. On the log scale used inside this pair, adoption is 97 versus 100, and the fork community is 91 versus 100.
Push history: dbx was last pushed on 17 November 2026 (0 days ago), and tidb was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,733 for dbx (0.057 per star) and 7,730 for tidb (0.190 per star). Issue-health scores are 52 and 34; activity scores are 100 and 100.
Both dbx and tidb are listed as Apache-2.0. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Databases, both dbx (30,615 stars) and tidb (40,739 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, tidb is open source.
The lead is split. dbx is furthest ahead on issue health (52 to 34), while tidb is furthest ahead on fork community (100 to 91). Choose the dimension a rollout cannot compromise on.
Composite score: dbx 92.5, tidb 92.9. 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 | tidb |
|---|---|---|
| GitHub stars | 30,615 | 40,739 |
| Forks | 2,788 | 6,297 |
| Open issues | 1,733 | 7,730 |
| Adoption | 97 | 100 |
| Activity | 100 | 100 |
| Community | 91 | 100 |
| Issue health | 52 | 34 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 92.5 | 92.9 |
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。
TiDB is built for agentic workloads that grow unpredictably, with ACID guarantees and native support for transactions, analytics, and vector search. No data silos. No noisy neighbors. No infrastructure ceiling.
tidb has more GitHub stars: 40,739 versus 30,615 for dbx. The gap is 10,124 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both dbx and tidb 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. tidb 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. 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 92.5 and tidb scores 92.9.