A
libsql
84.5
17,335 stars · MIT
Databases
supabase leads by 13.4 · clear
A
84.5
17,335 stars · MIT
B · leads
97.9
115,156 stars · Apache-2.0
libsql versus supabase is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. libsql is written mainly in C; supabase is written mainly in TypeScript. The composite score is 84.5 for libsql and 97.9 for supabase.
supabase has 115,156 GitHub stars to libsql's 17,335, a gap of 97,821 (6.64×). Forks are 564 for libsql and 15,166 for supabase. On the log scale used inside this pair, adoption is 84 versus 100, and the fork community is 66 versus 100.
Push history: libsql was last pushed on 07 November 2026 (10 days ago), and supabase was last pushed on 17 November 2026 (0 days ago). Open issues stand at 490 for libsql (0.028 per star) and 1,233 for supabase (0.011 per star). Issue-health scores are 70 and 84; activity scores are 92 and 100.
libsql 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 libsql and 96 for supabase. This is a procurement signal, not legal advice.
In Databases, both libsql (17,335 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: libsql is open source, supabase is open source.
supabase is ahead on every scored dimension that is not level. Level dimensions: license flexibility, self-hosting. The widest gap is fork community at 34 points (66 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
supabase finishes ahead at 97.9 against libsql at 84.5, a 13.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 | libsql | supabase |
|---|---|---|
| GitHub stars | 17,335 | 115,156 |
| Forks | 564 | 15,166 |
| Open issues | 490 | 1,233 |
| Adoption | 84 | 100 |
| Activity | 92 | 100 |
| Community | 66 | 100 |
| Issue health | 70 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 84.5 | 97.9 |
libSQL is a fork of SQLite that is both Open Source, and Open Contributions.
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,335 for libsql. The gap is 97,821 stars.
supabase was pushed more recently: 17 November 2026 versus 07 November 2026 for libsql. That is 10 days apart.
Yes. This catalog marks both libsql and supabase as self-hostable. Confirm each project's deploy docs before you plan a migration.
libsql 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 libsql scores 84.5. This page calls that a clear lead for supabase.