Redis History & Founding Timeline

The decision to change Redis's license from BSD to RSALv2/SSPL — while commercially motivated and arguably necessary for long-term sustainability — was executed without sufficient advance community engagement, creating the impression of a unilateral decision made without respect for the open-source community that built Redis's success. A more deliberate stakeholder engagement process might have preserved community goodwill while achieving similar commercial objectives, potentially preventing or softening the Valkey fork response.

Redis Ltd. maintained a balanced portfolio of on-premise Enterprise and cloud offerings for longer than optimal, slowing the cloud revenue mix improvement that investors and the competitive landscape demanded. Earlier and more aggressive migration of the installed base toward Redis Cloud — even at the cost of some short-term revenue cannibalization from on-premise maintenance contracts — would have improved the company's competitive positioning against pure-cloud alternatives and accelerated the ARR growth trajectory.

Redis Ltd.'s strategy of building advanced capabilities — search, JSON, graph, time series — as separate loadable modules rather than integrating them into the core Redis codebase created a fragmented developer experience and complicated deployment management. Customers running multiple modules faced version compatibility challenges and increased operational complexity. The later integration of key modules into Redis Stack was a corrective measure that acknowledged this architectural misstep.