A
influxdb
94.0
31,816 stars · Apache-2.0
Databases
quivr leads by 5.1 · narrow
A
94.0
31,816 stars · Apache-2.0
B · leads
99.1
39,655 stars · MIT
influxdb versus quivr is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. influxdb is written mainly in Rust; quivr is written mainly in Go. The composite score is 94.0 for influxdb and 99.1 for quivr.
quivr has 39,655 GitHub stars to influxdb's 31,816, a gap of 7,839 (1.25×). Forks are 3,826 for influxdb and 3,730 for quivr. On the log scale used inside this pair, adoption is 98 versus 100, and the fork community is 100 versus 100.
Push history: influxdb 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 2,175 for influxdb (0.068 per star) and 16 for quivr (0.000 per star). Issue-health scores are 52 and 96; activity scores are 100 and 100.
influxdb 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 influxdb and 96 for quivr. This is a procurement signal, not legal advice.
In Databases, both influxdb (31,816 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: influxdb is open source, quivr is open source.
The lead is split. influxdb is furthest ahead on fork community (100 to 100), while quivr is furthest ahead on issue health (96 to 52). Choose the dimension a rollout cannot compromise on.
quivr finishes ahead at 99.1 against influxdb at 94.0, a 5.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 | influxdb | quivr |
|---|---|---|
| GitHub stars | 31,816 | 39,655 |
| Forks | 3,826 | 3,730 |
| Open issues | 2,175 | 16 |
| Adoption | 98 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 100 |
| Issue health | 52 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.0 | 99.1 |
Scalable datastore for metrics, events, and real-time analytics
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 31,816 for influxdb. The gap is 7,839 stars.
influxdb was pushed more recently: 17 November 2026 versus 16 November 2026 for quivr. That is 1 days apart.
Yes. This catalog marks both influxdb and quivr as self-hostable. Confirm each project's deploy docs before you plan a migration.
influxdb 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 influxdb scores 94.0. This page calls that a narrow lead for quivr.