Your Software Roadmap Is Now a Free Spec. Redis Proved It in One Week.
Synergised Consulting Ltd
Last Updated: 16 October 2026
A software vendor's product roadmap no longer belongs to the vendor. When Redis changed its licence in March 2024, a working open-source replacement called Valkey existed within roughly a week, backed by AWS, Google Cloud, Oracle, Ericsson and Snap. What a company announces in public now works as a specification anyone can implement, and the durable value has moved to running the thing well, not owning the code. That shift matters to a small business owner because it changes which parts of your tooling you can safely build on, and which parts you should treat as replaceable from day one.
What Happened at Redis
Redis was, for years, the definition of settled infrastructure. According to the Linux Foundation's launch announcement [1], developers ranked Redis the sixth most-used database in the 2023 Stack Overflow developer survey, and it sat under caching layers, session stores and message queues across a huge share of the web. On 20 March 2024, according to TechCrunch's reporting [3], Redis Ltd moved the product from the permissive BSD licence to source-available licences. According to LWN's coverage of the change [2], all future versions of Redis would ship under the SSPL and RSAL starting with version 7.4, and Redis's own chief executive described the licence move as necessary because maintaining the BSD licence was "at odds with our ability to drive Redis successfully into the future".
The response did not take months. According to TechCrunch's reporting on the fork [3], longtime Redis maintainer Madelyn Olson, a principal engineer at AWS, had already started a fork in her own GitHub account, and most of the existing Redis maintainers joined within days of the announcement. On 28 March 2024, eight days after the licence change, the Linux Foundation announced it would host the fork under the name Valkey, continuing development from Redis 7.2.4 under the BSD 3-clause licence, with AWS, Google Cloud, Oracle, Ericsson and Snap named as backers [1].
Why the fork moved this fast
The speed had a structural cause, not a heroic one. The maintainers did not need to decide what to build, because Redis itself was the specification, and Redis 7.2.4 was the starting point [1]. Nothing about the fork required anyone's permission, because the BSD licence already allowed it. According to TechCrunch [3], the timing helped too: the announcement landed in the middle of KubeCon in Paris, where Linux Foundation staff and AWS engineers were already in the same rooms. As LWN put it at the time [2], the possibility of a swift fork with widespread community backing "should give pause to vendors who expect a smooth path after abandoning open source".
The Same Pattern in Terraform, and What the Numbers Say Now
Redis was not an exception. According to LWN [2], when HashiCorp adopted its Business Source Licence for its products in 2023, a fork of its Terraform infrastructure tool appeared within days and was taken under the Linux Foundation's wing as OpenTofu. Two forks, two different companies, the same shape: a licensing or roadmap decision announced in public, and a functioning alternative assembled faster than the vendor's own release cycle.
The alternatives did not stay small. Live GitHub data retrieved on 16 October 2026 [5] shows OpenTofu at 30,513 stars and Valkey at 27,442 stars, both carrying permissive licences and both under active foundation governance. These are not protest artefacts that faded after the news cycle. They are infrastructure that other projects now build on, which is exactly the outcome a vendor cannot revoke once it exists. The mechanism in both cases was the same: the original product, its documentation and its public roadmap were a complete specification, so the only scarce inputs were maintainers willing to do the work and a governance home the community trusted.
Where the Value Actually Moved
Here is the part that gets missed when the story is told as "open source beat the vendor". The value did not move from Redis Ltd to the Valkey repository. It moved, in both directions, to the layer above the code: running it, hosting it, keeping it current and answering for it. According to AWS's own account of its decision [4], the company added Valkey support to its ElastiCache and MemoryDB managed database services and committed its engineers to contributing to the project. AWS does not own Valkey, cannot licence it and cannot switch it off. What AWS sells is a fully managed version of it with an SLA attached, and that business survives any licence the project ever chooses.
What the vendor still controls | What it no longer controls | |
|---|---|---|
The code and its licence | The fork took both, permanently | |
The specification | Everyone; it is public | The vendor alone |
Running it at scale, with support | Whoever operates best | Nobody by default |
The customer relationship | Whoever owns the hosted experience | The code's author |
A hosted service built on an open core is not a weaker position than owning the code. In the Redis episode it proved to be the stronger one, because it survives every outcome: if the project thrives, the hosted business thrives with it, and if the vendor had kept the code closed, the customers who cared would still have needed someone to run it. The asset that mattered was never the source tree. It was the operating capability and the trust that comes with answering for it.
What This Means for a Small Business
For a business owner, the lesson is not about Redis. It is about which of your tools are foundations and which are fittings. In discovery workshops, owners rarely arrive with a list of systems they are exposed to; the list gets built in conversation, walking through a normal week task by task, and the same pattern shows up each time: the tools that would hurt most to lose are often the ones the owner assumed were simply part of the furniture, provided and priced at their IT provider's discretion. That is the sharp end of the MSP-locked pattern, an owner ready to act whose provider's service scope simply stops short of it.
The practical response is a small piece of homework, not a re-platforming project.
The Homework: A One-Page System Inventory
For each tool the business genuinely depends on, record three things: who provides it, whether a credible open-source or self-hostable alternative exists, and roughly what a move would cost in days of effort. That one-page system inventory does two jobs. On an ordinary Tuesday it tells you where a licence change or a price rise would actually hurt, before it happens. And if the business is ever sold, it answers a question a buyer's diligence always asks: what here depends on a single vendor's continued goodwill?
The Redis episode is the evidence that this question is not hypothetical. Eight days was all it took for the market to rebuild around a decision one company made about one licence, and the businesses that had already written down what they depended on were the ones that could move. The ones that had not found out from an outage.
Sources
- [1] Linux Foundation, "Linux Foundation Launches Open Source Valkey Community", press release, 28 March 2024:
- [2] LWN.net, "The race to replace Redis", 28 March 2024:
- [3] TechCrunch, "Why AWS, Google and Oracle are backing the Valkey Redis fork", 31 March 2024:
- [4] AWS Open Source Blog, "Why AWS Supports Valkey", 4 April 2024:
- [5] GitHub repository data for valkey-io/valkey and opentofu/opentofu, retrieved via the GitHub API on 16 October 2026:
