Skip to content
DevUtils Online

Databases

redis vs tile38

tile38 leads by 3.2 · narrow

A

redis

83.4

77,588 stars · license n/a

B · leads

tile38

86.6

9,761 stars · MIT

redis versus tile38 is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. redis is written mainly in C; tile38 is written mainly in Go. The composite score is 83.4 for redis and 86.6 for tile38.

redis has 77,588 GitHub stars to tile38's 9,761, a gap of 67,827 (7.95×). Forks are 25,072 for redis and 626 for tile38. On the log scale used inside this pair, adoption is 100 versus 82, and the fork community is 100 versus 64.

Push history: redis was last pushed on 17 November 2026 (0 days ago), and tile38 was last pushed on 14 November 2026 (3 days ago). Open issues stand at 3,122 for redis (0.040 per star) and 165 for tile38 (0.017 per star). Issue-health scores are 70 and 84; activity scores are 100 and 100.

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. tile38 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 30 for redis and 96 for tile38. This is a procurement signal, not legal advice.

Only tile38 is marked self-hostable here (9,761 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: redis is unpriced in this catalog, tile38 is open source.

The lead is split. redis is furthest ahead on fork community (100 to 64), while tile38 is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.

tile38 finishes ahead at 86.6 against redis at 83.4, a 3.2 point narrow margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

redis versus tile38 metrics
Signal redis tile38
GitHub stars 77,588 9,761
Forks 25,072 626
Open issues 3,122 165
Adoption 100 82
Activity 100 100
Community 100 64
Issue health 70 84
License 30 96
Self-hosting 35 100
Composite 83.4 86.6

redis

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.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, redis or tile38?

redis has more GitHub stars: 77,588 versus 9,761 for tile38. The gap is 67,827 stars.

Which was updated more recently, redis or tile38?

redis was pushed more recently: 17 November 2026 versus 14 November 2026 for tile38. That is 3 days apart.

Can I self-host both redis and tile38?

Only tile38 is marked self-hostable. redis is not.

Which license is easier to embed in a commercial product, redis or tile38?

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. tile38 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.

Who wins the redis vs tile38 score?

tile38 scores 86.6 and redis scores 83.4. This page calls that a narrow lead for tile38.

Related comparisons