A
quivr
94.0
39,655 stars · MIT
Databases
supabase leads by 3.9 · narrow
A
94.0
39,655 stars · MIT
B · leads
97.9
115,156 stars · Apache-2.0
quivr versus supabase 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; supabase is written mainly in TypeScript. The composite score is 94.0 for quivr and 97.9 for supabase.
supabase has 115,156 GitHub stars to quivr's 39,655, a gap of 75,501 (2.90×). Forks are 3,730 for quivr and 15,166 for supabase. On the log scale used inside this pair, adoption is 91 versus 100, and the fork community is 85 versus 100.
Push history: quivr was last pushed on 16 November 2026 (1 day ago), and supabase was last pushed on 17 November 2026 (0 days ago). Open issues stand at 16 for quivr (0.000 per star) and 1,233 for supabase (0.011 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. supabase 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. License scores in this pair are 96 for quivr and 96 for supabase. This is a procurement signal, not legal advice.
In Databases, both quivr (39,655 stars) and supabase (115,156 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, supabase is open source.
The lead is split. quivr is furthest ahead on issue health (96 to 84), while supabase is furthest ahead on fork community (100 to 85). Choose the dimension a rollout cannot compromise on.
supabase finishes ahead at 97.9 against quivr at 94.0, a 3.9 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 | quivr | supabase |
|---|---|---|
| GitHub stars | 39,655 | 115,156 |
| Forks | 3,730 | 15,166 |
| Open issues | 16 | 1,233 |
| Adoption | 91 | 100 |
| Activity | 100 | 100 |
| Community | 85 | 100 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.0 | 97.9 |
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.
The Postgres development platform. Supabase gives you a dedicated Postgres database to build your web, mobile, and AI applications.
supabase has more GitHub stars: 115,156 versus 39,655 for quivr. The gap is 75,501 stars.
supabase was pushed more recently: 17 November 2026 versus 16 November 2026 for quivr. That is 1 days apart.
Yes. This catalog marks both quivr and supabase as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. supabase 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
supabase scores 97.9 and quivr scores 94.0. This page calls that a narrow lead for supabase.