Valkey-proxy addresses a critical gap that has slowed adoption of the open source Redis fork. The proxy layer, developed by Percona, sits between applications and Valkey Cluster deployments, eliminating the need to rewrite code for distributed architectures.
Redis's shift to proprietary licensing in 2024 triggered a community schism. The Linux Foundation responded by launching Valkey as a permissively licensed alternative. Though Redis later introduced AGPLv3 as an optional license in 2025, Valkey has continued building momentum with its own governance model and feature roadmap.
Valkey has made significant strides since its inception, cutting memory footprint, adding cluster management tools, access controls, and even deploying AI agents for maintenance tasks. Yet one substantial hurdle remained for organizations considering migration: the architectural mismatch between legacy single-instance Redis applications and distributed Valkey Cluster topologies.
The proxy problem
Redis serves as an in-memory data store for caching and performance-critical workloads across countless applications. Many of these systems were designed to treat Redis as a monolithic service, assuming single-node behavior. Transitioning to Valkey Cluster requires applications to handle multiple nodes, manage routing logic, and account for command behavior variations. Commercial Redis offerings and certain cloud providers solve this through proxy intermediaries, but self-hosted Valkey deployments lacked equivalent tooling.
Percona, which provides support for MySQL, PostgreSQL, MongoDB and other open source databases, is now filling this void. The company counts AWS, Google Cloud, and Oracle among the backers of the Valkey project alongside itself.
Kyle Davis, general manager for the Redis/Valkey ecosystem at Percona, outlined the migration challenge during an interview at the Linux Foundation's Open Source Summit Europe in Prague. He characterized the inability to move applications without substantial rewrites as a major adoption blocker.
Right now there's not really any good open source solution for this.
Kyle Davis, Percona
Other proxy solutions exist in the ecosystem. Envoy, for instance, operates as a general-purpose proxy but lacks full comprehension of the Valkey protocol and cannot fully support all Valkey capabilities due to how it manages connections.
This leaves organizations in a difficult position: maintain aging single-instance Redis deployments or undertake costly application rewrites to adopt clustered Valkey. Valkey-proxy bridges that gap.
Now we can address a whole different layer of applications that really didn't have a good option.
Kyle Davis, Percona
Path to open development
Percona built the initial version of Valkey-proxy internally and intends to transition it into the broader Valkey project before opening development to external contributors. Davis expects input from Percona customers, developers elsewhere, and independent maintainers.
Whether hyperscalers will participate remains uncertain. Davis acknowledged the possibility but noted that cloud providers typically maintain proprietary tooling tightly integrated with their platforms, making broad contribution less predictable.
The proxy holds particular value for organizations managing their own infrastructure, whether on premises or in private clouds. Davis identified the potential user base as spanning from resource-constrained startups to major financial institutions with stringent compliance mandates—entities requiring direct control over data infrastructure placement and operation.
Beyond immediate migration support, Valkey-proxy could serve as a foundation for future capabilities. The abstraction layer enables architectural flexibility and opens possibilities for additional components.
It provides a decoupling layer that in the future we can build other components into. Filling that missing gap allows us to have more flexibility, and now we can start doing things in a different way.
Kyle Davis, Percona
Timeline and testing
Percona secured approval in late September for Valkey-proxy to join the Valkey project. The company is now transferring code from private repositories to public infrastructure. Full source code availability is targeted for end of October, with a release candidate planned for December and general availability expected in early 2027.
The months ahead will be critical for identifying edge cases as real-world applications test the proxy. Freshworks is among the first organizations to evaluate Valkey-proxy, collaborating with Percona as an early adopter and design partner to surface issues during development.
That's going to be a great test case for it.
Kyle Davis, Percona