A · leads
chroma
96.5
29,704 stars · Apache-2.0
Databases
chroma leads by 3.2 · narrow
A · leads
96.5
29,704 stars · Apache-2.0
B
93.3
25,279 stars · MIT
chroma versus turso is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in Rust. The composite score is 96.5 for chroma and 93.3 for turso.
chroma has 29,704 GitHub stars to turso's 25,279, a gap of 4,425 (1.18×). Forks are 2,609 for chroma and 1,553 for turso. On the log scale used inside this pair, adoption is 100 versus 98, and the fork community is 100 versus 93.
Push history: chroma was last pushed on 13 November 2026 (3 days ago), and turso was last pushed on 17 November 2026 (0 days ago). Open issues stand at 979 for chroma (0.033 per star) and 1,714 for turso (0.068 per star). Issue-health scores are 70 and 52; activity scores are 100 and 100.
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. turso 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. License scores in this pair are 96 for chroma and 96 for turso. This is a procurement signal, not legal advice.
In Databases, both chroma (29,704 stars) and turso (25,279 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, turso is open source.
chroma is ahead on every scored dimension that is not level. Level dimensions: recent activity, license flexibility, self-hosting. The widest gap is issue health at 18 points (70 vs 52), and the tightest is self-hosting at 0 points (100 vs 100).
chroma finishes ahead at 96.5 against turso at 93.3, a 3.2 point narrow 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 | turso |
|---|---|---|
| GitHub stars | 29,704 | 25,279 |
| Forks | 2,609 | 1,553 |
| Open issues | 979 | 1,714 |
| Adoption | 100 | 98 |
| Activity | 100 | 100 |
| Community | 100 | 93 |
| Issue health | 70 | 52 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 96.5 | 93.3 |
Search infrastructure for AI
A SQL database in Rust: SQLite-compatible, now also speaking Postgres (experimental). The LLVM of databases.
chroma has more GitHub stars: 29,704 versus 25,279 for turso. The gap is 4,425 stars.
turso 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 turso 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. turso 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
chroma scores 96.5 and turso scores 93.3. This page calls that a narrow lead for chroma.