Published October 7, 2026 · Added October 7, 2026

Percona's Valkey-proxy promises an easier route from standalone Redis to Valkey clusters

Percona announced Valkey-proxy, a new open source project now accepted as an official Valkey project, aimed at making it easier for enterprises to move from Redis to the Linux Foundation-backed fork. The code is due to be released later in October and the project is targeting general availability in 2027 under the BSD-3-Clause licence, sitting between an application and a Valkey deployment so software written for a single standalone instance keeps working while gaining the scalability of cluster mode, and pooling backend connections so connection counts stay bounded. Percona's Redis/Valkey general manager Kyle Davis told The Stack at Open Source Summit Europe in Prague that without a standard open source proxy many enterprises cannot migrate, leaving them on commercial Redis, which is expensive to license and run, or on a cloud provider's proprietary, platform-tied proxy, and described the work as addressing an 'original sin' inherited from Redis that made it hard to scale on top of the data store.

Percona announced Valkey-proxy, a new open source project now accepted as an official Valkey project, aimed at making it easier for enterprises to move from Redis to the Linux Foundation-backed fork. The code is due to be released later in October and the project is targeting general availability in 2027 under the BSD-3-Clause licence, sitting between an application and a Valkey deployment so software written for a single standalone instance keeps working while gaining the scalability of cluster mode, and pooling backend connections so connection counts stay bounded. Percona’s Redis/Valkey general manager Kyle Davis told The Stack at Open Source Summit Europe in Prague that without a standard open source proxy many enterprises cannot migrate, leaving them on commercial Redis, which is expensive to license and run, or on a cloud provider’s proprietary, platform-tied proxy, and described the work as addressing an ‘original sin’ inherited from Redis that made it hard to scale on top of the data store.

Read the original story.

Source: Thestack