A
redis
83.4
77,588 stars · license n/a
Databases
xerj leads by 6.4 · narrow
A
83.4
77,588 stars · license n/a
B · leads
89.8
19,190 stars · Apache-2.0
redis versus xerj 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; xerj is written mainly in Rust. The composite score is 83.4 for redis and 89.8 for xerj.
redis has 77,588 GitHub stars to xerj's 19,190, a gap of 58,398 (4.04×). Forks are 25,072 for redis and 1,440 for xerj. On the log scale used inside this pair, adoption is 100 versus 88, and the fork community is 100 versus 72.
Push history: redis was last pushed on 17 November 2026 (0 days ago), and xerj was last pushed on 17 November 2026 (0 days ago). Open issues stand at 3,122 for redis (0.040 per star) and 251 for xerj (0.013 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. xerj 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. License scores in this pair are 30 for redis and 96 for xerj. This is a procurement signal, not legal advice.
Only xerj is marked self-hostable here (19,190 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, xerj is open source.
The lead is split. redis is furthest ahead on fork community (100 to 72), while xerj is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
xerj finishes ahead at 89.8 against redis at 83.4, a 6.4 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 | redis | xerj |
|---|---|---|
| GitHub stars | 77,588 | 19,190 |
| Forks | 25,072 | 1,440 |
| Open issues | 3,122 | 251 |
| Adoption | 100 | 88 |
| Activity | 100 | 100 |
| Community | 100 | 72 |
| Issue health | 70 | 84 |
| License | 30 | 96 |
| Self-hosting | 35 | 100 |
| Composite | 83.4 | 89.8 |
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.
AI search engine and MCP server for bots and agents. One Rust binary indexes code, docs, logs, JSONL/CSV and PDFs for BM25 full-text, vector and hybrid search, code search without grep, agent memory and RAG. Elasticsearch-compatible API; Corpus Hub serves hundreds of reference memory corpora.
redis has more GitHub stars: 77,588 versus 19,190 for xerj. The gap is 58,398 stars.
Both were last pushed on 17 November 2026.
Only xerj is marked self-hostable. redis is not.
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. xerj 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
xerj scores 89.8 and redis scores 83.4. This page calls that a narrow lead for xerj.