A · leads
supabase
97.9
115,156 stars · Apache-2.0
Databases
supabase leads by 8.6 · clear
A · leads
97.9
115,156 stars · Apache-2.0
B
89.3
19,190 stars · Apache-2.0
supabase versus xerj is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. supabase is written mainly in TypeScript; xerj is written mainly in Rust. The composite score is 97.9 for supabase and 89.3 for xerj.
supabase has 115,156 GitHub stars to xerj's 19,190, a gap of 95,966 (6.00×). Forks are 15,166 for supabase and 1,440 for xerj. On the log scale used inside this pair, adoption is 100 versus 85, and the fork community is 100 versus 76.
Push history: supabase was last pushed on 17 November 2026 (0 days ago), and xerj was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,233 for supabase (0.011 per star) and 251 for xerj (0.013 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.
Both supabase and xerj 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 supabase (115,156 stars) and xerj (19,190 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: supabase is open source, xerj is open source.
supabase is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is fork community at 24 points (100 vs 76), and the tightest is self-hosting at 0 points (100 vs 100).
supabase finishes ahead at 97.9 against xerj at 89.3, a 8.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 | supabase | xerj |
|---|---|---|
| GitHub stars | 115,156 | 19,190 |
| Forks | 15,166 | 1,440 |
| Open issues | 1,233 | 251 |
| Adoption | 100 | 85 |
| Activity | 100 | 100 |
| Community | 100 | 76 |
| Issue health | 84 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 97.9 | 89.3 |
The Postgres development platform. Supabase gives you a dedicated Postgres database to build your web, mobile, and AI applications.
AI search engine and MCP server for bots and agents. One Rust binary indexes code, docs, logs, JSONL/CSV and PDFs for BM25 full-text, vector and hybrid search, code search without grep, agent memory and RAG. Elasticsearch-compatible API; Corpus Hub serves hundreds of reference memory corpora.
supabase has more GitHub stars: 115,156 versus 19,190 for xerj. The gap is 95,966 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both supabase and xerj as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. xerj 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 xerj scores 89.3. This page calls that a clear lead for supabase.