A
QuestDB
90.8
17,538 stars · Apache-2.0
Databases
quivr leads by 8.3 · clear
A
90.8
17,538 stars · Apache-2.0
B · leads
99.1
39,655 stars · MIT
QuestDB versus quivr is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. QuestDB is written mainly in Java; quivr is written mainly in Go. The composite score is 90.8 for QuestDB and 99.1 for quivr.
quivr has 39,655 GitHub stars to QuestDB's 17,538, a gap of 22,117 (2.26×). Forks are 1,701 for QuestDB and 3,730 for quivr. On the log scale used inside this pair, adoption is 92 versus 100, and the fork community is 90 versus 100.
Push history: QuestDB was last pushed on 17 November 2026 (0 days ago), and quivr was last pushed on 16 November 2026 (1 day ago). Open issues stand at 1,515 for QuestDB (0.086 per star) and 16 for quivr (0.000 per star). Issue-health scores are 52 and 96; activity scores are 100 and 100.
QuestDB 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. 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. License scores in this pair are 96 for QuestDB and 96 for quivr. This is a procurement signal, not legal advice.
In Databases, both QuestDB (17,538 stars) and quivr (39,655 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: QuestDB is open source, quivr is open source.
quivr is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is issue health at 44 points (52 vs 96), and the tightest is self-hosting at 0 points (100 vs 100).
quivr finishes ahead at 99.1 against QuestDB at 90.8, a 8.3 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 | QuestDB | quivr |
|---|---|---|
| GitHub stars | 17,538 | 39,655 |
| Forks | 1,701 | 3,730 |
| Open issues | 1,515 | 16 |
| Adoption | 92 | 100 |
| Activity | 100 | 100 |
| Community | 90 | 100 |
| Issue health | 52 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 90.8 | 99.1 |
QuestDB is a time-series database with SQL and a focus on ingestion speed. It is used for metrics, market data, and other timestamp-heavy workloads.
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.
quivr has more GitHub stars: 39,655 versus 17,538 for QuestDB. The gap is 22,117 stars.
QuestDB was pushed more recently: 17 November 2026 versus 16 November 2026 for quivr. That is 1 days apart.
Yes. This catalog marks both QuestDB and quivr as self-hostable. Confirm each project's deploy docs before you plan a migration.
QuestDB 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. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
quivr scores 99.1 and QuestDB scores 90.8. This page calls that a clear lead for quivr.