A · leads
dbeaver
94.5
52,455 stars · Apache-2.0
Databases
dbeaver leads by 4.1 · narrow
A · leads
94.5
52,455 stars · Apache-2.0
B
90.4
25,194 stars · AGPL-3.0
dbeaver versus TDengine is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. dbeaver is written mainly in Java; TDengine is written mainly in C. The composite score is 94.5 for dbeaver and 90.4 for TDengine.
dbeaver has 52,455 GitHub stars to TDengine's 25,194, a gap of 27,261 (2.08×). Forks are 4,460 for dbeaver and 5,011 for TDengine. On the log scale used inside this pair, adoption is 100 versus 93, and the fork community is 99 versus 100.
Push history: dbeaver was last pushed on 17 November 2026 (0 days ago), and TDengine was last pushed on 15 November 2026 (2 days ago). Open issues stand at 3,349 for dbeaver (0.064 per star) and 454 for TDengine (0.018 per star). Issue-health scores are 52 and 84; activity scores are 100 and 100.
dbeaver 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 dbeaver and 52 for TDengine. This is a procurement signal, not legal advice.
In Databases, both dbeaver (52,455 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: dbeaver is open source, TDengine is open source.
The lead is split. dbeaver is furthest ahead on license flexibility (96 to 52), while TDengine is furthest ahead on issue health (84 to 52). Choose the dimension a rollout cannot compromise on.
dbeaver finishes ahead at 94.5 against TDengine at 90.4, a 4.1 point narrow 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 | dbeaver | TDengine |
|---|---|---|
| GitHub stars | 52,455 | 25,194 |
| Forks | 4,460 | 5,011 |
| Open issues | 3,349 | 454 |
| Adoption | 100 | 93 |
| Activity | 100 | 100 |
| Community | 99 | 100 |
| Issue health | 52 | 84 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 94.5 | 90.4 |
Free universal database tool and SQL client
High-performance, scalable time-series database designed for Industrial IoT (IIoT) scenarios
dbeaver has more GitHub stars: 52,455 versus 25,194 for TDengine. The gap is 27,261 stars.
dbeaver was pushed more recently: 17 November 2026 versus 15 November 2026 for TDengine. That is 2 days apart.
Yes. This catalog marks both dbeaver and TDengine as self-hostable. Confirm each project's deploy docs before you plan a migration.
dbeaver 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.
dbeaver scores 94.5 and TDengine scores 90.4. This page calls that a narrow lead for dbeaver.