The Real Reason Redis Maintainers Disagree on Direction

Redis is the high-speed engine inside thousands of apps, from AI startups to major banks. But a deep disagreement over its future has split its community, and the 'real reason' has less to do with code than with a fundamental clash of philosophies.

Code, Cash, and Control

At its heart, the disagreement among Redis maintainers is about the soul of a massively successful open-source project. For years, Redis was governed by a permissive BSD license, meaning anyone could use, modify, and build upon it with few restrictions.

This fostered a vibrant community, but it also created a problem: corporate giant Redis Ltd., the primary steward of the project, felt that large cloud providers like AWS were profiting from Redis without contributing back in a meaningful way. The core conflict isn't about specific features; it's a battle between the ideals of a free, community-driven tool and the commercial necessity of funding its development and protecting its business model.

The Licensing Schism

The long-simmering tension erupted in March 2024 when Redis Ltd. announced it was moving away from the open-source BSD license. New versions of Redis would be released under dual source-available licenses (RSALv2 and SSPLv1). In simple terms, these licenses prevent cloud companies from offering Redis as a commercial service without paying Redis Ltd. While the company argued this was a necessary step to ensure the project's sustainability, many in the open-source world saw it as a betrayal. They argued that a project built by a community was being walled off for corporate benefit. This decision was the catalyst that fractured the community and led to direct, public disagreement among its key figures.

The Fork in the Road: Enter Valkey

The response from dissenting maintainers and major tech companies was swift. They created a 'fork'—a new project based on the last truly open-source version of Redis (7.2.4). Named Valkey and housed under the neutral, non-profit Linux Foundation, it promised to continue the original open-source mission of Redis. This move was backed by major players like Amazon Web Services, Google Cloud, and Oracle, the very companies the license change targeted. This effectively created two parallel paths: the official Redis, now controlled more tightly by Redis Ltd. and focused on enterprise features and AI, and Valkey, the community-driven spiritual successor committed to a permissive license.

Two Futures, One Past

Today, the disagreement is encoded in the projects' trajectories. Redis Ltd. has pushed forward, integrating advanced features for AI, JSON, and vector search directly into its core product, arguing the license change has allowed it to innovate faster. In a bid to mend fences, it later added an OSI-approved open-source license, AGPLv3, as a third option, though for many commercial users, its restrictive terms are a non-starter. Meanwhile, Valkey is focused on performance improvements on the core architecture and remaining fully open source, attracting developers and companies who prioritize license freedom above all else. The maintainers who stayed with Redis and those who moved to Valkey aren't just disagreeing on a roadmap; they are executing two fundamentally different visions for what an open-source project should be in the modern cloud era.