A
rqlite
89.5
17,956 stars · MIT
Databases
supabase leads by 8.4 · clear
A
89.5
17,956 stars · MIT
B · leads
97.9
115,156 stars · Apache-2.0
rqlite versus supabase is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. rqlite is written mainly in Go; supabase is written mainly in TypeScript. The composite score is 89.5 for rqlite and 97.9 for supabase.
supabase has 115,156 GitHub stars to rqlite's 17,956, a gap of 97,200 (6.41×). Forks are 827 for rqlite and 15,166 for supabase. On the log scale used inside this pair, adoption is 84 versus 100, and the fork community is 70 versus 100.
Push history: rqlite was last pushed on 17 November 2026 (0 days ago), and supabase was last pushed on 17 November 2026 (0 days ago). Open issues stand at 69 for rqlite (0.004 per star) and 1,233 for supabase (0.011 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.
rqlite 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 rqlite and 96 for supabase. This is a procurement signal, not legal advice.
In Databases, both rqlite (17,956 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: rqlite is open source, supabase is open source.
The lead is split. rqlite is furthest ahead on issue health (96 to 84), while supabase is furthest ahead on fork community (100 to 70). Choose the dimension a rollout cannot compromise on.
supabase finishes ahead at 97.9 against rqlite at 89.5, a 8.4 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 | rqlite | supabase |
|---|---|---|
| GitHub stars | 17,956 | 115,156 |
| Forks | 827 | 15,166 |
| Open issues | 69 | 1,233 |
| Adoption | 84 | 100 |
| Activity | 100 | 100 |
| Community | 70 | 100 |
| Issue health | 96 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 89.5 | 97.9 |
The lightweight, fault-tolerant database built on SQLite. Designed to keep your data highly available with minimal effort.
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 17,956 for rqlite. The gap is 97,200 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both rqlite and supabase as self-hostable. Confirm each project's deploy docs before you plan a migration.
rqlite 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 rqlite scores 89.5. This page calls that a clear lead for supabase.