Skip to content
DevUtils Online

Databases

DuckDB vs TDengine

DuckDB leads by 5.3 · narrow

A · leads

DuckDB

96.2

43,126 stars · MIT

B

TDengine

90.9

25,194 stars · AGPL-3.0

DuckDB versus TDengine is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. DuckDB is written mainly in C++; TDengine is written mainly in C. The composite score is 96.2 for DuckDB and 90.9 for TDengine.

DuckDB has 43,126 GitHub stars to TDengine's 25,194, a gap of 17,932 (1.71×). Forks are 4,214 for DuckDB and 5,011 for TDengine. On the log scale used inside this pair, adoption is 100 versus 95, and the fork community is 98 versus 100.

Push history: DuckDB 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 1,261 for DuckDB (0.029 per star) and 454 for TDengine (0.018 per star). Issue-health scores are 70 and 84; activity scores are 100 and 100.

DuckDB is listed as MIT, 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 DuckDB and 52 for TDengine. This is a procurement signal, not legal advice.

In Databases, both DuckDB (43,126 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: DuckDB is open source, TDengine is open source.

The lead is split. DuckDB is furthest ahead on license flexibility (96 to 52), while TDengine is furthest ahead on issue health (84 to 70). Choose the dimension a rollout cannot compromise on.

DuckDB finishes ahead at 96.2 against TDengine at 90.9, a 5.3 point narrow margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

DuckDB versus TDengine metrics
Signal DuckDB TDengine
GitHub stars 43,126 25,194
Forks 4,214 5,011
Open issues 1,261 454
Adoption 100 95
Activity 100 100
Community 98 100
Issue health 70 84
License 96 52
Self-hosting 100 100
Composite 96.2 90.9

DuckDB

DuckDB is an in-process analytical database, often described as SQLite for OLAP. It runs inside the application process and queries local files such as Parquet.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, DuckDB or TDengine?

DuckDB has more GitHub stars: 43,126 versus 25,194 for TDengine. The gap is 17,932 stars.

Which was updated more recently, DuckDB or TDengine?

DuckDB was pushed more recently: 17 November 2026 versus 15 November 2026 for TDengine. That is 2 days apart.

Can I self-host both DuckDB and TDengine?

Yes. This catalog marks both DuckDB and TDengine as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, DuckDB or TDengine?

DuckDB is listed as MIT, 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.

Who wins the DuckDB vs TDengine score?

DuckDB scores 96.2 and TDengine scores 90.9. This page calls that a narrow lead for DuckDB.

Related comparisons