Drew DeVault, author of the Sway user environment, the Hare programming language, the Aerc email client and the SourceHut collaborative development platform, announced the transfer of the Redict DBMS to the category outdated. The release Redict 7.3.6, created a year ago, will remain the last; no more updates are planned to be published. Redict was aimed at conservative maintenance of the code base without increasing functionality, since, according to the developers, Redis had reached maturity and contained all the necessary capabilities. Redict is also notable for its move to use the LGPLv3 license for patches (the old code remained under the BSD license).
The project became meaningless after Redis switched to the free AGPLv3 license, and Valkey, which continued to develop the code base under the BSD license, demonstrated the ability to maintain the code in the long term. Drew DeVault recommended that users switch to using Valkey despite the permissive license, since although the Redis code is available under the AGPL license, transferring changes to it requires signing an agreement to transfer ownership of the property rights to the code, which does not exclude another transition to a proprietary license in the future. To migrate from Redict to Valkey, just install the package with
Valkey and rename the configuration file from /etc/redict.conf to /etc/valkey.conf.
Redis was initially shipped under a permissive BSD license, which allowed you not to open your changes, after which in 2024 it switched to proprietary licenses RSALv2 (Redis Source Available License v2) and SSPLv1 (Server Side Public License v1). In 2025, Redis became available under the AGPLv3 license, a feature of which is the presence of restrictions for applications that provide the functioning of network services. When using AGPL components in the operation of network services, the developer is obliged to provide the user with the source code of all changes made to these components, even if the software underlying the service is not distributed and is used exclusively in the internal infrastructure to organize the operation of the service.