A · level
orm
94.7
47,675 stars · Apache-2.0
Databases
Too close to call · 94.7 to 93.9
A · level
94.7
47,675 stars · Apache-2.0
B · level
93.9
27,730 stars · BSD-3-Clause
orm versus Valkey 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; Valkey is written mainly in C. The composite score is 94.7 for orm and 93.9 for Valkey.
orm has 47,675 GitHub stars to Valkey's 27,730, a gap of 19,945 (1.72×). Forks are 2,635 for orm and 1,540 for Valkey. On the log scale used inside this pair, adoption is 100 versus 95, and the fork community is 100 versus 93.
Push history: orm was last pushed on 17 November 2026 (0 days ago), and Valkey was last pushed on 17 November 2026 (0 days ago). Open issues stand at 2,817 for orm (0.059 per star) and 1,045 for Valkey (0.038 per star). Issue-health scores are 52 and 70; 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. Valkey is listed as BSD-3-Clause, 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 Valkey. This is a procurement signal, not legal advice.
In Databases, both orm (47,675 stars) and Valkey (27,730 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, Valkey is open source.
The lead is split. orm is furthest ahead on fork community (100 to 93), while Valkey is furthest ahead on issue health (70 to 52). Choose the dimension a rollout cannot compromise on.
Composite score: orm 94.7, Valkey 93.9. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
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 | Valkey |
|---|---|---|
| GitHub stars | 47,675 | 27,730 |
| Forks | 2,635 | 1,540 |
| Open issues | 2,817 | 1,045 |
| Adoption | 100 | 95 |
| Activity | 100 | 100 |
| Community | 100 | 93 |
| Issue health | 52 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.7 | 93.9 |
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.
Valkey is a Linux Foundation key-value store forked from Redis. It is used as a cache, queue, and ephemeral data store under a permissive license.
orm has more GitHub stars: 47,675 versus 27,730 for Valkey. The gap is 19,945 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both orm and Valkey 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. Valkey is listed as BSD-3-Clause, 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.
Neither tool clears a one-point margin. orm scores 94.7 and Valkey scores 93.9.