Skip to content
TrustList
News

Redict is deprecated: 7.3.6 is the final release and the author advises Valkey

Editorial

By TrustList Editorial

The copyleft Redis fork announced on 17 November 2026 that it will get no further releases; its author recommends moving to Valkey and says to avoid returning to Redis.

About Redict is deprecated: 7.3.6 is the final release and the author advises Valkey

Redict is deprecated: 7.3.6 is the final release and the author advises Valkey

17 November 2026: Redict, a copyleft fork of Redis, has been declared deprecated by its author, Drew DeVault, in a post on the project's website. Version 7.3.6 is the final release. Anyone who runs Redict should plan a move to another key-value server.

Not yet independently verified. This is a post on the project's own website, written by its author; we have not checked its claims about licences or about Redis. The post does not say whether security fixes will be issued for 7.3.6 or when packages will leave distributions. The advice to switch is the author's, and the migration steps given are only for package and container installs. We will update this when it can be confirmed, and remove this note.

Why the project is stopping

The post says Redict was started to rally the people who left Redis behind around a copyleft licence, as protection against a future licence change by the vendor. It says that, with the success of the Valkey project and Redis returning to a copyleft licence, Redict was not able to build a sustainable community. The author thanks contributors and users and signs off by saying the project had a good run.

The recommended destination

The author recommends that Redict users switch to Valkey. It notes that Valkey uses a permissive licence, which the author argues gives it better long-term prospects. It advises against going back to Redis, even though Redis is open source and copyleft again, because Redis uses a contributor licence agreement, which the author says would make another licence change easier. That is the author's opinion, and a team choosing a replacement should weigh licence, support and hosting options for itself.

How to switch, as described by the author

According to the post, switching is straightforward. For installs from a package manager, install the Valkey package and move the configuration file from /etc/redict.conf to /etc/valkey.conf. For containers, pull the Valkey container instead of the Redict one and make sure it runs with the appropriate configuration file.

The post does not describe moving data, replication or clusters, so those need their own plan. Before changing anything in production, take a backup of your data files, read the Valkey documentation on compatibility with the Redis version your Redict build tracks, and rehearse the change on a copy.

What teams should do

Start with an inventory of where Redict runs: servers, container images, Helm charts, compose files and infrastructure code. Search for the redict package name and the redict image reference in your repositories, because it is easy to forget a cache that has run quietly for years.

Next, decide the date. A project with no further releases is unlikely to receive fixes for new vulnerabilities from its maintainers, so the safer course is to schedule the move rather than wait for a problem. If you depend on a distribution package, check how long your distribution plans to keep shipping it, since that is not covered in the post.

Test your clients against the replacement, including any modules, scripts and configuration directives you use, and check monitoring dashboards and alerts that refer to the old service name. Then migrate a non-critical instance first, keep the old one available for rollback, and retire it once the new one has run cleanly under real load.

Our database software category lists database products to compare.

Who needs to act

This mainly matters to teams that run their own Redict servers. Applications that use Redis-compatible clients usually connect the same way to Valkey, but each team should confirm that on its own workload.

Sources

Categories & features

TrustList Weekly

The week in software and IT, in one email

The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.

We will email you to confirm. Unsubscribe with one click in any issue. Privacy policy

You may be interested in