Comparison
NumKong vs redis
Verdict
Pick NumKong when license: NumKong is Apache-2.0, redis is Other; pick redis when license: redis is Other, NumKong is Apache-2.0.
Markdown twin · NumKong alternatives · redis alternatives
GraphCanon updated today
Trust & integrity
| Signal | NumKong | redis |
|---|---|---|
| Maintenance | Very active (1d since push) As of today · github_public_v1 | Very active (0d since push) As of today · github_public_v1 |
| Provenance | Not a fork · Personal account As of today · github_public_v1 | Not a fork · Organization account As of today · github_public_v1 |
| Security (OSV) | No lockfile As of today · none | No lockfile As of today · none |
Tagline
- NumKong
- SIMD-accelerated distances, dot products, matrix ops, geospatial & geometric kernels for 16 numeric types — from 6-bit floats to 64-bit complex — across x86, Arm, RISC-V, and WASM, with bindings for P
- redis
- Redis is a preferred cache, data structure server, and document & vector query engine for real-time applications.
Stars
- NumKong
- 1.8k
- redis
- 75k
Forks
- NumKong
- 124
- redis
- 25k
Open issues
- NumKong
- 30
- redis
- 2.9k
Language
- NumKong
- C
- redis
- C
Adopt for
- NumKong
- -
- redis
- Redis is an in-memory database designed as a versatile cache and data structure store with advanced features such as JSON operations and vector searches, making it suitable for real-time applications.
Persona
- NumKong
- -
- redis
- -
Runtime
- NumKong
- -
- redis
- -
License
- NumKong
- Apache-2.0
- redis
- Other
Last pushed
- NumKong
- Jul 9, 2026
- redis
- Jul 10, 2026
Categories
- NumKong
- Data & Retrieval, Evaluation & Observability, Vector Databases
- redis
- Data & Retrieval, Vector Databases
Trust and health
Days since push
- NumKong
- 1d
- redis
- 0d
Open issues (now)
- NumKong
- 30
- redis
- 2.9k
Owner type
- NumKong
- User
- redis
- Organization
Full report
- NumKong
- Trust report
- redis
- Trust report
Choose NumKong if…
- License: NumKong is Apache-2.0, redis is Other.
- Tags unique to NumKong: arm-neon, assembly, blas, cpp.
- Also covers Evaluation & Observability.
When NOT to use NumKong
- Data & Retrieval: Skip a heavy ingestion framework when your corpus is small and static; a script plus the embedding API is enough.
- Evaluation & Observability: Defer heavyweight eval infra only until you have real traffic - never skip it once users depend on answers.
- Vector Databases: Don't reach for a dedicated vector DB under ~100k vectors; pgvector on your existing Postgres is simpler to operate.
Choose redis if…
- License: redis is Other, NumKong is Apache-2.0.
- Tags unique to redis: cache, caching, database, in-memory.
- You need high-speed access to frequently used data due to Redis's in-memory nature.
When NOT to use redis
- Your project has limited memory resources since Redis relies on in-memory storage, which could lead to high costs or operational challenges with large datasets.
- You prioritize persistence over speed; while Redis offers persistence options, its primary design is for real-time access and not robust disk-based backup solutions like traditional SQL databases.
- Your application workload does not benefit from the fast read/write capabilities and rich data structure support offered by Redis, possibly implying that a less specialized database would suffice.
Explore
Sources
Every stat on this page traces to a dated GitHub sync, license file, enrichment field, or trust scan.
- GitHub stars (ashvardanian/NumKong) · observed Jul 11, 2026
- GitHub forks (ashvardanian/NumKong) · observed Jul 11, 2026
- Last push (ashvardanian/NumKong) · observed Jul 9, 2026
- License file (Apache-2.0) · observed Jul 11, 2026
- Trust scan (lockfile / OSV) · observed Jul 11, 2026
- GitHub stars (redis/redis) · observed Jul 11, 2026
- GitHub forks (redis/redis) · observed Jul 11, 2026
- Last push (redis/redis) · observed Jul 10, 2026
- License file (Other) · observed Jul 11, 2026
- Decision facts (enrichment) · observed Jul 11, 2026
- Trust scan (lockfile / OSV) · observed Jul 11, 2026
GitHub stars on cards: NumKong 1.8k · redis 75k (synced Jul 11, 2026).
Common questions
- What is the difference between NumKong and redis?
- NumKong: SIMD-accelerated distances, dot products, matrix ops, geospatial & geometric kernels for 16 numeric types — from 6-bit floats to 64-bit complex — across x86, Arm, RISC-V, and WASM, with bindings for P. redis: Redis is a preferred cache, data structure server, and document & vector query engine for real-time applications.. See the comparison table for live GitHub stats and shared categories.
- When should I choose NumKong over redis?
- Choose NumKong over redis when License: NumKong is Apache-2.0, redis is Other; Tags unique to NumKong: arm-neon, assembly, blas, cpp; Also covers Evaluation & Observability.
- When should I choose redis over NumKong?
- Choose redis over NumKong when License: redis is Other, NumKong is Apache-2.0; Tags unique to redis: cache, caching, database, in-memory; You need high-speed access to frequently used data due to Redis's in-memory nature.
- When should I avoid NumKong?
- Data & Retrieval: Skip a heavy ingestion framework when your corpus is small and static; a script plus the embedding API is enough. Evaluation & Observability: Defer heavyweight eval infra only until you have real traffic - never skip it once users depend on answers. Vector Databases: Don't reach for a dedicated vector DB under ~100k vectors; pgvector on your existing Postgres is simpler to operate.
- When should I avoid redis?
- Your project has limited memory resources since Redis relies on in-memory storage, which could lead to high costs or operational challenges with large datasets. You prioritize persistence over speed; while Redis offers persistence options, its primary design is for real-time access and not robust disk-based backup solutions like traditional SQL databases. Your application workload does not benefit from the fast read/write capabilities and rich data structure support offered by Redis, possibly implying that a less specialized database would suffice.
- Is NumKong or redis more popular on GitHub?
- redis has more GitHub stars (75,394 vs 1,845). Stars measure visibility, not whether either tool fits your constraints.
- Are NumKong and redis open source?
- Yes - both are open-source projects on GitHub (NumKong: Apache-2.0, redis: Other).
- Where can I find alternatives to NumKong or redis?
- GraphCanon lists graph-backed alternatives at NumKong alternatives and redis alternatives (NumKong markdown twin, redis markdown twin), ranked by typed relationship edges rather than popularity votes.
- Is there a machine-readable version of this comparison?
- Yes. The markdown twin at this comparison mirrors this page for agents and LLM crawlers, with the same stats table and FAQ answers.
- Which is better maintained, NumKong or redis?
- NumKong: Very active. redis: Very active. Compare maintenance labels, days since push, and release cadence in the trust section below - stars alone do not measure maintenance.
- Where are the full trust reports for NumKong and redis?
- GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: NumKong trust report; redis trust report.