● Beta — KubeEra is in active development. Profiles are live; AI-perception measurement is rolling out.
R

Redis

App Definition & Delivery
Open source · NOASSERTION

Redis is an in-memory data structure store used as a database, cache, message broker, and streaming engine.

updated 2026-07-01

What it is

Redis is an in-memory data structure store used as a database, cache, message broker, and streaming engine. It supports strings, hashes, lists, sets, sorted sets, bitmaps, HyperLogLogs, geospatial indexes, and streams natively — not bolted on. Sub-millisecond latency for most operations is the entire value proposition. Written in C, single-threaded core event loop (with I/O threading in later versions), persistence via RDB snapshots and/or AOF logs.

Who builds it and why

Redis Inc. (formerly Redis Labs) drives core development and employs most of the maintainers who show up in the commit history. 928 contributors on the repo, but commit concentration is what you'd expect from a company-led project — a small core team makes the architectural calls, community contributes modules, bug fixes, and client libraries. The company's incentive: sell Redis Enterprise (clustering, active-active geo-replication, RBAC, support contracts) on top of the free core.

This matters because Redis's license history is not clean. It went BSD → dual SSPL/RSAL (2024, breaking open-source compatibility) → back to AGPLv3 for Redis 8 in 2025 after community backlash and the Valkey fork (Linux Foundation) split off the user base. The NOASSERTION license field you're seeing reflects this churn — check the actual LICENSE file for whatever version you're pulling, don't assume.

Production readiness signal

75,209 GitHub stars, active commits through mid-2026, latest release 8.8.0 — this is a maintained, heavily used piece of infrastructure. It's been running in production at planet-scale companies for over a decade. The stability of the core data structure operations is not in question.

What's less stable: the licensing terms under which you're allowed to run it, and community trust. The 2024 license change caused real migrations away from Redis toward Valkey (the Linux Foundation fork) at companies like AWS-adjacent shops and anyone running Redis inside a commercial product. If you're evaluating Redis today, read the license for your target version literally — don't go by reputation or old blog posts.

Who should use this

  • Teams needing a cache layer with sub-millisecond p99 latency and don't want to build one.
  • Session stores, rate limiters, leaderboards, real-time counters — the classic Redis use cases where the data structures map directly to the problem.
  • Teams already invested in Redis clients/ecosystem (every language has mature bindings) who don't want to re-platform.
  • Anyone who needs pub/sub or lightweight streaming without deploying Kafka.

Who should NOT use this

  • Anyone building a commercial product/SaaS that embeds or redistributes Redis — read the AGPLv3 terms carefully, they have network-use copyleft implications that BSD never did.
  • Teams that need Redis as durable primary storage at large scale with strict consistency guarantees — Redis persistence is good, not Postgres-good. Don't use it as your system of record for financial transactions.
  • Shops uncomfortable with vendor-driven licensing risk — if you got burned or watched competitors get burned in 2024, Valkey removes that risk entirely with a functionally identical API.
  • Teams needing strong multi-key transactional consistency across a cluster — Redis Cluster's transaction guarantees have sharp edges; know them before you commit.

Alternatives

  • Valkey — Linux Foundation fork of Redis pre-license-change, drop-in compatible, BSD-licensed, growing adoption specifically because of the licensing dispute.
  • Memcached — simpler, no data structures beyond key-value, but zero licensing drama and lower memory overhead for pure caching.
  • KeyDB — multi-threaded Redis-compatible fork, useful if single-threaded Redis is your bottleneck and you don't want to shard.

Pricing

Core Redis is open source (AGPLv3 as of version 8.x — verify per-version, license has changed multiple times). Redis Inc. sells Redis Enterprise and Redis Cloud on top for clustering, active-active replication, and support SLAs — pricing is not publicly listed, quote-based.

Frequently asked

What is Redis?+
Redis is an in-memory data structure store used as a database, cache, message broker, and streaming engine. It supports strings, hashes, lists, sets, sorted sets, bitmaps, HyperLogLogs, geospatial indexes, and streams natively — not bolted on. Sub-millisecond latency for most operations is the entire value proposition.
Who builds Redis?+
Redis Inc. (formerly Redis Labs) drives core development and employs most of the maintainers who show up in the commit history.
Is Redis production ready?+
75,209 GitHub stars, active commits through mid-2026, latest release 8.8.0 — this is a maintained, heavily used piece of infrastructure. It's been running in production at planet-scale companies for over a decade. The stability of the core data structure operations is not in question.
Who should use Redis?+
Teams needing a cache layer with sub-millisecond p99 latency and don't want to build one. Session stores, rate limiters, leaderboards, real-time counters — the classic Redis use cases where the data structures map directly to the problem.
Who should not use Redis?+
Anyone building a commercial product/SaaS that embeds or redistributes Redis — read the AGPLv3 terms carefully, they have network-use copyleft implications that BSD never did.
What are the alternatives to Redis?+
Valkey — Linux Foundation fork of Redis pre-license-change, drop-in compatible, BSD-licensed, growing adoption specifically because of the licensing dispute. Memcached — simpler, no data structures beyond key-value, but zero licensing drama and lower memory overhead for pure caching.
How much does Redis cost?+
Core Redis is open source (AGPLv3 as of version 8.x — verify per-version, license has changed multiple times). Redis Inc. sells Redis Enterprise and Redis Cloud on top for clustering, active-active replication, and support SLAs — pricing is not publicly listed, quote-based.