A
FerretDB
74.2
11,117 stars · Apache-2.0
Databases
tidb leads by 18.7 · decisive
A
74.2
11,117 stars · Apache-2.0
B · leads
92.9
40,739 stars · Apache-2.0
FerretDB versus tidb 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 Go. The composite score is 74.2 for FerretDB and 92.9 for tidb.
tidb has 40,739 GitHub stars to FerretDB's 11,117, a gap of 29,622 (3.66×). Forks are 496 for FerretDB and 6,297 for tidb. On the log scale used inside this pair, adoption is 88 versus 100, and the fork community is 71 versus 100.
Push history: FerretDB was last pushed on 05 June 2026 (165 days ago), and tidb was last pushed on 17 November 2026 (0 days ago). Open issues stand at 452 for FerretDB (0.041 per star) and 7,730 for tidb (0.190 per star). Issue-health scores are 70 and 34; activity scores are 36 and 100.
Both FerretDB 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 FerretDB (11,117 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: FerretDB is open source, tidb is open source.
The lead is split. FerretDB is furthest ahead on issue health (70 to 34), while tidb is furthest ahead on recent activity (100 to 36). Choose the dimension a rollout cannot compromise on.
tidb finishes ahead at 92.9 against FerretDB at 74.2, a 18.7 point decisive 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 | FerretDB | tidb |
|---|---|---|
| GitHub stars | 11,117 | 40,739 |
| Forks | 496 | 6,297 |
| Open issues | 452 | 7,730 |
| Adoption | 88 | 100 |
| Activity | 36 | 100 |
| Community | 71 | 100 |
| Issue health | 70 | 34 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 74.2 | 92.9 |
FerretDB is a MongoDB-compatible document database that stores data in PostgreSQL. It is built for teams that want that wire protocol without the SSPL server.
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 11,117 for FerretDB. The gap is 29,622 stars.
tidb was pushed more recently: 17 November 2026 versus 05 June 2026 for FerretDB. That is 165 days apart.
Yes. This catalog marks both FerretDB and tidb as self-hostable. Confirm each project's deploy docs before you plan a migration.
FerretDB 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.
tidb scores 92.9 and FerretDB scores 74.2. This page calls that a decisive lead for tidb.