SaaS vendor migrates off Redis to Valkey in 60 days.

Situation

The company was a mid sized SaaS analytics vendor serving several thousand business customers from a multi tenant platform. Redis sat at the center of that platform, used for caching, session storage, and a high volume job queue across roughly two dozen services. The team had adopted Redis years earlier under a permissive open source license and had never revisited the terms, because there had never been a reason to.

The exposure that triggered the work

As of March 2024, Redis moved from its permissive open source license to a dual model under the Redis Source Available License and the Server Side Public License. Source available is not open source, and the Server Side Public License is not approved by the Open Source Initiative. For a vendor that resold analytics built on Redis as part of a hosted service, the competitive use language created exposure that the company counsel could not cleanly rule out. A renewal of the commercial support contract was also approaching, and the vendor sales team had begun referencing the new license in conversation. The board asked a simple question the company could not yet answer: how much of our product depends on this, and what does the change cost us.

Approach

We began with the inventory. A software composition analysis pass mapped every service that touched Redis, direct and transitive, and recorded the version and the exact role each instance played. That map turned a vague worry into a bounded list of two dozen touch points, ranked by exposure. Only a handful sat in the competitive use path that concerned counsel; the rest were internal.

With the list in hand, we weighed three paths: negotiate a commercial license, stay put and accept the risk, or migrate to Valkey, the open source fork created after the license change. We sized each on cost, license posture, and timeline. Valkey carried strong protocol compatibility with the Redis version in use, which kept the engineering change small, and it returned the platform to an open license footing, which removed the competitive use question entirely. Migration won on both risk and total cost.

We sequenced the cutover by service rather than all at once. The highest exposure services moved first, behind a compatibility test suite that validated each before promotion. Internal services followed. The team ran Valkey and Redis side by side during transition so any regression could be reverted in minutes rather than rolled back across the platform.

Outcome

The migration completed in 60 days, inside the window before the support renewal. All two dozen services moved to Valkey under an open license, which closed the competitive use exposure that had prompted the work. The company avoided a commercial license quote that had been framed in the low six figures per year, and it declined the renewal without disruption. Equally important, the inventory built for the migration became a standing asset: the platform now carries a current software bill of materials that flags any future license change at the next refresh.

Lessons for buyers

Three lessons carry to other buyers. First, the inventory is the whole game. The migration was fast because the work was scoped precisely, and it was scoped precisely because the inventory was complete. Second, a credible fork changes the math. Valkey gave the company a real alternative, which removed the pressure to accept a commercial quote on the vendor terms. Third, timing is leverage. By acting before the renewal rather than after, the company chose its path on its own schedule rather than under a deadline set by someone else.

A migration like this is the work of our open source remediation advisory service. For the wider context, see our pillar on Redis, Elastic, and database relicensing and our guide to open source license risk.