head to head · open source
Turso vs Bytebase
Turso has 17,215 GitHub stars, 530 forks, 453 open issues and last shipped 2 days ago. Bytebase has 14,491 stars, 983 forks, 167 open issues and last shipped yesterday. Turso leads on adoption by 19% (17,215 vs 14,491 stars). Turso is written in C under MIT; Bytebase is written in Go under a custom or non-standard licence. Turso has attracted 3% as many forks as stars, Bytebase 7%. Bytebase was the more recently maintained of the two, and both are self-hostable with no licence fee.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 8884 open source comparisons
Side by side
| Turso | Bytebase | |
|---|---|---|
| GitHub stars | ★ 17K | ★ 14K |
| License | MIT | Custom / other |
| Written in | C | Go |
| Last push | 2026-09-16 | 2026-09-17 |
| Forks | ⑂ 530 | ⑂ 983 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick Turso if
- You weight community size — 17K stars and counting
- You want the MIT license terms
- Your stack matches C
- You value the larger contributor base for long-term maintenance
pick Bytebase if
- You want the Bytebase feature set and don't need the biggest community
- You prefer the Custom / other license terms
- Your stack matches Go
- You evaluated both and Bytebase fits your workflow better
About Turso
libSQL is an open source, open contribution fork of SQLite created and maintained by Turso. It lives in the SQLite ecosystem and extends the embedded database model with features such as embedded replicas and remote access. The repository also distinguishes libSQL from the separate Turso database, which is a SQLite compatible implementation written from scratch in Rust and currently in beta.
read the full Turso overview →
About Bytebase
Bytebase is an open source database governance platform that acts as a single control plane between human users, AI agents, and databases. It governs change management, access control, and compliance so that every database change and query can be reviewed, controlled, and recorded. The project sits in the Infrastructure and Operations database ecosystem, with topics that include CI/CD, DevOps, DevSecOps, GitOps, data governance, data masking, data security, database access, Flyway, Liquibase, and MongoDB.
read the full Bytebase overview →
More in Infrastructure & Operations
Related comparisons
More Databases projects
Compare either of these against the rest of the Databases field.
Frequently asked questions
Is Turso or Bytebase more popular?
Turso has 17,215 GitHub stars and Bytebase has 14,491. Turso has the larger community by that measure.
Are Turso and Bytebase free?
Both are open source. Turso is licensed under MIT, and Bytebase has no licence declared in this registry. Both are free to self-host.
What is the difference between Turso and Bytebase?
Turso is written in C and Bytebase in Go. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, Turso or Bytebase?
Choose Turso if you want the larger community (17,215 stars) or its MIT licence terms. Choose Bytebase if its feature set, stack or Custom / other licence fits better. Both are self-hostable.