A
FerretDB
70.6
11,117 stars · Apache-2.0
Databases
supabase leads by 27.3 · decisive
A
70.6
11,117 stars · Apache-2.0
B · leads
97.9
115,156 stars · Apache-2.0
FerretDB versus supabase is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. FerretDB is written mainly in Go; supabase is written mainly in TypeScript. The composite score is 70.6 for FerretDB and 97.9 for supabase.
supabase has 115,156 GitHub stars to FerretDB's 11,117, a gap of 104,039 (10.36×). Forks are 496 for FerretDB and 15,166 for supabase. On the log scale used inside this pair, adoption is 80 versus 100, and the fork community is 64 versus 100.
Push history: FerretDB was last pushed on 05 June 2026 (165 days ago), and supabase was last pushed on 17 November 2026 (0 days ago). Open issues stand at 452 for FerretDB (0.041 per star) and 1,233 for supabase (0.011 per star). Issue-health scores are 70 and 84; activity scores are 36 and 100.
Both FerretDB and supabase are listed as Apache-2.0. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Databases, both FerretDB (11,117 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: FerretDB 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 recent activity at 64 points (36 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
supabase finishes ahead at 97.9 against FerretDB at 70.6, a 27.3 point decisive 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 | FerretDB | supabase |
|---|---|---|
| GitHub stars | 11,117 | 115,156 |
| Forks | 496 | 15,166 |
| Open issues | 452 | 1,233 |
| Adoption | 80 | 100 |
| Activity | 36 | 100 |
| Community | 64 | 100 |
| Issue health | 70 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 70.6 | 97.9 |
FerretDB is a MongoDB-compatible document database that stores data in PostgreSQL. It is built for teams that want that wire protocol without the SSPL server.
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 11,117 for FerretDB. The gap is 104,039 stars.
supabase was pushed more recently: 17 November 2026 versus 05 June 2026 for FerretDB. That is 165 days apart.
Yes. This catalog marks both FerretDB and supabase as self-hostable. Confirm each project's deploy docs before you plan a migration.
FerretDB 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. 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 FerretDB scores 70.6. This page calls that a decisive lead for supabase.