A
meilisearch
84.3
59,885 stars · license n/a
Databases
quivr leads by 13.6 · clear
A
84.3
59,885 stars · license n/a
B · leads
97.9
39,655 stars · MIT
meilisearch versus quivr is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. meilisearch is written mainly in Rust; quivr is written mainly in Go. The composite score is 84.3 for meilisearch and 97.9 for quivr.
meilisearch has 59,885 GitHub stars to quivr's 39,655, a gap of 20,230 (1.51×). Forks are 2,799 for meilisearch and 3,730 for quivr. On the log scale used inside this pair, adoption is 100 versus 96, and the fork community is 96 versus 100.
Push history: meilisearch 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 318 for meilisearch (0.005 per star) and 16 for quivr (0.000 per star). Issue-health scores are 84 and 96; activity scores are 100 and 100.
meilisearch is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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 30 for meilisearch and 96 for quivr. This is a procurement signal, not legal advice.
Only quivr is marked self-hostable here (39,655 stars, deploy score 100). meilisearch is not (59,885 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: meilisearch is unpriced in this catalog, quivr is open source.
The lead is split. meilisearch is furthest ahead on adoption (100 to 96), while quivr is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
quivr finishes ahead at 97.9 against meilisearch at 84.3, a 13.6 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 | meilisearch | quivr |
|---|---|---|
| GitHub stars | 59,885 | 39,655 |
| Forks | 2,799 | 3,730 |
| Open issues | 318 | 16 |
| Adoption | 100 | 96 |
| Activity | 100 | 100 |
| Community | 96 | 100 |
| Issue health | 84 | 96 |
| License | 30 | 96 |
| Self-hosting | 35 | 100 |
| Composite | 84.3 | 97.9 |
A lightning-fast search engine API bringing AI-powered hybrid search to your sites and applications.
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.
meilisearch has more GitHub stars: 59,885 versus 39,655 for quivr. The gap is 20,230 stars.
meilisearch was pushed more recently: 17 November 2026 versus 16 November 2026 for quivr. That is 1 days apart.
Only quivr is marked self-hostable. meilisearch is not.
meilisearch is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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 97.9 and meilisearch scores 84.3. This page calls that a clear lead for quivr.