A
chroma
90.0
29,704 stars · Apache-2.0
Databases
supabase leads by 7.9 · clear
A
90.0
29,704 stars · Apache-2.0
B · leads
97.9
115,156 stars · Apache-2.0
chroma versus supabase is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. chroma is written mainly in Rust; supabase is written mainly in TypeScript. The composite score is 90.0 for chroma and 97.9 for supabase.
supabase has 115,156 GitHub stars to chroma's 29,704, a gap of 85,452 (3.88×). Forks are 2,609 for chroma and 15,166 for supabase. On the log scale used inside this pair, adoption is 88 versus 100, and the fork community is 82 versus 100.
Push history: chroma was last pushed on 13 November 2026 (3 days ago), and supabase was last pushed on 17 November 2026 (0 days ago). Open issues stand at 979 for chroma (0.033 per star) and 1,233 for supabase (0.011 per star). Issue-health scores are 70 and 84; activity scores are 100 and 100.
Both chroma 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 chroma (29,704 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: chroma is open source, supabase is open source.
supabase is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is fork community at 18 points (82 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
supabase finishes ahead at 97.9 against chroma at 90.0, a 7.9 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 | chroma | supabase |
|---|---|---|
| GitHub stars | 29,704 | 115,156 |
| Forks | 2,609 | 15,166 |
| Open issues | 979 | 1,233 |
| Adoption | 88 | 100 |
| Activity | 100 | 100 |
| Community | 82 | 100 |
| Issue health | 70 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 90.0 | 97.9 |
Search infrastructure for AI
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 29,704 for chroma. The gap is 85,452 stars.
supabase was pushed more recently: 17 November 2026 versus 13 November 2026 for chroma. That is 3 days apart.
Yes. This catalog marks both chroma and supabase as self-hostable. Confirm each project's deploy docs before you plan a migration.
chroma 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 chroma scores 90.0. This page calls that a clear lead for supabase.