A
neon
82.8
23,335 stars · Apache-2.0
Databases
tidb leads by 10.1 · clear
A
82.8
23,335 stars · Apache-2.0
B · leads
92.9
40,739 stars · Apache-2.0
neon versus tidb is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. neon is written mainly in Rust; tidb is written mainly in Go. The composite score is 82.8 for neon and 92.9 for tidb.
tidb has 40,739 GitHub stars to neon's 23,335, a gap of 17,404 (1.75×). Forks are 1,139 for neon and 6,297 for tidb. On the log scale used inside this pair, adoption is 95 versus 100, and the fork community is 80 versus 100.
Push history: neon was last pushed on 31 August 2026 (78 days ago), and tidb was last pushed on 17 November 2026 (0 days ago). Open issues stand at 589 for neon (0.025 per star) and 7,730 for tidb (0.190 per star). Issue-health scores are 70 and 34; activity scores are 58 and 100.
Both neon 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 neon (23,335 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: neon is open source, tidb is open source.
The lead is split. neon is furthest ahead on issue health (70 to 34), while tidb is furthest ahead on recent activity (100 to 58). Choose the dimension a rollout cannot compromise on.
tidb finishes ahead at 92.9 against neon at 82.8, a 10.1 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 | neon | tidb |
|---|---|---|
| GitHub stars | 23,335 | 40,739 |
| Forks | 1,139 | 6,297 |
| Open issues | 589 | 7,730 |
| Adoption | 95 | 100 |
| Activity | 58 | 100 |
| Community | 80 | 100 |
| Issue health | 70 | 34 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 82.8 | 92.9 |
Neon: Serverless Postgres. We separated storage and compute to offer autoscaling, code-like database branching, and scale to zero.
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 23,335 for neon. The gap is 17,404 stars.
tidb was pushed more recently: 17 November 2026 versus 31 August 2026 for neon. That is 78 days apart.
Yes. This catalog marks both neon and tidb as self-hostable. Confirm each project's deploy docs before you plan a migration.
neon 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 neon scores 82.8. This page calls that a clear lead for tidb.