Skip to content
DevUtils Online

Databases

quivr vs TDengine

quivr leads by 7.4 · clear

A · leads

quivr

98.6

39,655 stars · MIT

B

TDengine

91.2

25,194 stars · AGPL-3.0

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

quivr has 39,655 GitHub stars to TDengine's 25,194, a gap of 14,461 (1.57×). Forks are 3,730 for quivr and 5,011 for TDengine. On the log scale used inside this pair, adoption is 100 versus 96, and the fork community is 96 versus 100.

Push history: quivr was last pushed on 16 November 2026 (1 day ago), and TDengine was last pushed on 15 November 2026 (2 days ago). Open issues stand at 16 for quivr (0.000 per star) and 454 for TDengine (0.018 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.

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

In Databases, both quivr (39,655 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: quivr is open source, TDengine is open source.

The lead is split. quivr is furthest ahead on license flexibility (96 to 52), while TDengine is furthest ahead on fork community (100 to 96). Choose the dimension a rollout cannot compromise on.

quivr finishes ahead at 98.6 against TDengine at 91.2, a 7.4 point clear 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.

quivr versus TDengine metrics
Signal quivr TDengine
GitHub stars 39,655 25,194
Forks 3,730 5,011
Open issues 16 454
Adoption 100 96
Activity 100 100
Community 96 100
Issue health 96 84
License 96 52
Self-hosting 100 100
Composite 98.6 91.2

quivr

An open-source engine that turns continuous content streams into search and monitoring. Durable ingestion, hybrid search, alerts, and plugins for formats, models and business rules.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, quivr or TDengine?

quivr has more GitHub stars: 39,655 versus 25,194 for TDengine. The gap is 14,461 stars.

Which was updated more recently, quivr or TDengine?

quivr was pushed more recently: 16 November 2026 versus 15 November 2026 for TDengine. That is 1 days apart.

Can I self-host both quivr and TDengine?

Yes. This catalog marks both quivr 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, quivr or TDengine?

quivr 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 quivr vs TDengine score?

quivr scores 98.6 and TDengine scores 91.2. This page calls that a clear lead for quivr.

Related comparisons