A · leads
kysely
87.3
14,360 stars · MIT
Databases
kysely leads by 3.9 · narrow
A · leads
87.3
14,360 stars · MIT
B
83.4
77,588 stars · license n/a
kysely versus redis is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. kysely is written mainly in TypeScript; redis is written mainly in C. The composite score is 87.3 for kysely and 83.4 for redis.
redis has 77,588 GitHub stars to kysely's 14,360, a gap of 63,228 (5.40×). Forks are 459 for kysely and 25,072 for redis. On the log scale used inside this pair, adoption is 85 versus 100, and the fork community is 60 versus 100.
Push history: kysely was last pushed on 17 November 2026 (0 days ago), and redis was last pushed on 17 November 2026 (0 days ago). Open issues stand at 213 for kysely (0.015 per star) and 3,122 for redis (0.040 per star). Issue-health scores are 84 and 70; activity scores are 100 and 100.
kysely 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. redis is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. License scores in this pair are 96 for kysely and 30 for redis. This is a procurement signal, not legal advice.
Only kysely is marked self-hostable here (14,360 stars, deploy score 100). redis is not (77,588 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: kysely is open source, redis is unpriced in this catalog.
The lead is split. kysely is furthest ahead on license flexibility (96 to 30), while redis is furthest ahead on fork community (100 to 60). Choose the dimension a rollout cannot compromise on.
kysely finishes ahead at 87.3 against redis at 83.4, a 3.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 | kysely | redis |
|---|---|---|
| GitHub stars | 14,360 | 77,588 |
| Forks | 459 | 25,072 |
| Open issues | 213 | 3,122 |
| Adoption | 85 | 100 |
| Activity | 100 | 100 |
| Community | 60 | 100 |
| Issue health | 84 | 70 |
| License | 96 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 87.3 | 83.4 |
A type-safe TypeScript SQL query builder
For developers, who are building real-time data-driven applications, Redis is the preferred, fastest, and most feature-rich cache, data structure server, and document and vector query engine.
redis has more GitHub stars: 77,588 versus 14,360 for kysely. The gap is 63,228 stars.
Both were last pushed on 17 November 2026.
Only kysely is marked self-hostable. redis is not.
kysely 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. redis is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
kysely scores 87.3 and redis scores 83.4. This page calls that a narrow lead for kysely.