A
neon
84.6
23,335 stars · Apache-2.0
Databases
TDengine leads by 8.0 · clear
A
84.6
23,335 stars · Apache-2.0
B · leads
92.6
25,194 stars · AGPL-3.0
neon versus TDengine 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; TDengine is written mainly in C. The composite score is 84.6 for neon and 92.6 for TDengine.
TDengine has 25,194 GitHub stars to neon's 23,335, a gap of 1,859 (1.08×). Forks are 1,139 for neon and 5,011 for TDengine. On the log scale used inside this pair, adoption is 99 versus 100, and the fork community is 83 versus 100.
Push history: neon was last pushed on 31 August 2026 (78 days ago), and TDengine was last pushed on 15 November 2026 (2 days ago). Open issues stand at 589 for neon (0.025 per star) and 454 for TDengine (0.018 per star). Issue-health scores are 70 and 84; activity scores are 58 and 100.
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. TDengine is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. License scores in this pair are 96 for neon and 52 for TDengine. This is a procurement signal, not legal advice.
In Databases, both neon (23,335 stars) and TDengine (25,194 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, TDengine is open source.
The lead is split. neon is furthest ahead on license flexibility (96 to 52), while TDengine is furthest ahead on recent activity (100 to 58). Choose the dimension a rollout cannot compromise on.
TDengine finishes ahead at 92.6 against neon at 84.6, a 8.0 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 | TDengine |
|---|---|---|
| GitHub stars | 23,335 | 25,194 |
| Forks | 1,139 | 5,011 |
| Open issues | 589 | 454 |
| Adoption | 99 | 100 |
| Activity | 58 | 100 |
| Community | 83 | 100 |
| Issue health | 70 | 84 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 84.6 | 92.6 |
Neon: Serverless Postgres. We separated storage and compute to offer autoscaling, code-like database branching, and scale to zero.
High-performance, scalable time-series database designed for Industrial IoT (IIoT) scenarios
TDengine has more GitHub stars: 25,194 versus 23,335 for neon. The gap is 1,859 stars.
TDengine was pushed more recently: 15 November 2026 versus 31 August 2026 for neon. That is 76 days apart.
Yes. This catalog marks both neon and TDengine 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. TDengine is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
TDengine scores 92.6 and neon scores 84.6. This page calls that a clear lead for TDengine.