A · leads
orm
94.7
47,675 stars · Apache-2.0
Databases
orm leads by 2.9 · narrow
A · leads
94.7
47,675 stars · Apache-2.0
B
91.8
25,279 stars · MIT
orm versus turso is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. orm is written mainly in TypeScript; turso is written mainly in Rust. The composite score is 94.7 for orm and 91.8 for turso.
orm has 47,675 GitHub stars to turso's 25,279, a gap of 22,396 (1.89×). Forks are 2,635 for orm and 1,553 for turso. On the log scale used inside this pair, adoption is 100 versus 94, and the fork community is 100 versus 93.
Push history: orm was last pushed on 17 November 2026 (0 days ago), and turso was last pushed on 17 November 2026 (0 days ago). Open issues stand at 2,817 for orm (0.059 per star) and 1,714 for turso (0.068 per star). Issue-health scores are 52 and 52; activity scores are 100 and 100.
orm 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 orm and 96 for turso. This is a procurement signal, not legal advice.
In Databases, both orm (47,675 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: orm is open source, turso is open source.
orm 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 7 points (100 vs 93), and the tightest is self-hosting at 0 points (100 vs 100).
orm finishes ahead at 94.7 against turso at 91.8, a 2.9 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 | orm | turso |
|---|---|---|
| GitHub stars | 47,675 | 25,279 |
| Forks | 2,635 | 1,553 |
| Open issues | 2,817 | 1,714 |
| Adoption | 100 | 94 |
| Activity | 100 | 100 |
| Community | 100 | 93 |
| Issue health | 52 | 52 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.7 | 91.8 |
The Prisma ORM: write your application in TypeScript with human-readable queries instead of SQL. Host your database on Prisma Postgres and your app on Prisma Compute.
A SQL database in Rust: SQLite-compatible, now also speaking Postgres (experimental). The LLVM of databases.
orm has more GitHub stars: 47,675 versus 25,279 for turso. The gap is 22,396 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both orm and turso as self-hostable. Confirm each project's deploy docs before you plan a migration.
orm 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.
orm scores 94.7 and turso scores 91.8. This page calls that a narrow lead for orm.