Why Redis Is Changing Licenses and What It Means for the Database Ecosystem

Redis History: Back to the Beginning

Redis began as a simple in‑memory dictionary server created by Salvatore Sanfilippo for a real‑time log analysis tool, later evolving into a full‑featured NoSQL database adopted by major companies and packaged in major Linux distributions.

Cloud vs Open Source

Redis Ltd. announced that starting with version 7.4 the core will be released under a non‑free, source‑available license (SSPL and RSAL), a move framed as a response to cloud providers monetizing open‑source software without contributing back.

Changing Distribution Model

Redis Labs, like other venture‑backed database companies, has shifted to dual licensing to monetize services, arguing that the BSD license no longer fits the modern cloud‑centric ecosystem.

Proliferating Forks and Alternatives

Numerous alternatives have emerged, including Valkey (a Linux‑Foundation‑backed fork), KeyDB, Redict (LGPLv3), and Microsoft’s Garnet (MIT‑licensed), each offering different licensing and feature trade‑offs.

Considerations for Alternatives

Linux distributions and service providers must evaluate these forks for compatibility, licensing compliance, and feature parity; early adopters report mixed experiences regarding functionality and maintenance support.

The Way Forward

While it is still uncertain which fork will gain the most traction, Valkey appears poised to become a widely‑supported replacement, prompting vendors to reconsider reliance on Redis under its new licensing regime.