Redict deprecated as developer points users to Valkey
Drew DeVault has ended Redict, the Redis fork he started after the 2024 licence change, and recommends Valkey instead. LWN.net reports that the two projects are compatible, so a switch should be a small piece of work.

Key takeaways
- Drew DeVault has deprecated Redict, the Redis fork he created after the 2024 licence change, and recommends Valkey instead.
- LWN.net reports that Redict and Valkey are mutually compatible, so switching means installing a different package and renaming the configuration file.
- DeVault says Valkey's success and Redis's return to a copyleft licence left Redict without a sustainable community.
- He advises against returning to Redis, arguing its contributor licence agreement could allow another change of terms later.
In this article
What was announced
Redict, a community fork of the Redis data project, has been retired. Drew DeVault, who created it, announced the decision on 17 November 2026, according to LWN.net.
His advice for anyone still running Redict is short: move to Valkey, the Redis fork backed by the Linux Foundation and released under a permissive licence. A permissive licence is one that puts few conditions on anyone who reuses or shares the code.
Why Redict existed
Redict was set up after Redis changed its licence in 2024. DeVault wanted a version of the software that its maintainers could not take closed again at a later date.
In the announcement, he said he had hoped to "rally the Redis diaspora around a copyleft initiative". Copyleft is a licence condition that requires anyone who shares a modified version to pass on the same freedoms to others.
Redict was therefore built as a safeguard rather than as a product with its own roadmap. That framing matters for understanding what happened next.
Why the project is ending
Two changes removed the reason for Redict to carry on, according to the announcement. Valkey grew into a successful project in its own right, and Redis itself moved back to a copyleft licence.
With both of those in place, Redict no longer had a clear role. DeVault said the fork was not able to build a community large enough to keep going.
The result is a deprecation rather than a technical failure. Redict still exists, but its maintainer is no longer asking people to build on it.
How the switch to Valkey works
LWN.net describes the move as simple, because Redict and Valkey work with each other's setups. In practice, that means installing the Valkey package instead of the Redict one and giving the configuration file a new name.
The report does not mention any conversion step for data already held by a running Redict server. Teams that need certainty on that point should check Valkey's own documentation before making the change on a live system.
LWN.net's report also does not give a firm date for when Redict packages will stop being available. For now, the guidance is about where new work should go, not about an urgent deadline.
Why DeVault warns against Redis

DeVault also advises against simply going back to Redis. He accepts that the project is open source and copyleft once more, but he points to its contributor licence agreement as a risk.
A contributor licence agreement, usually shortened to CLA, is a document that people sign before their code is accepted. It often gives the project owner wide rights over that work, which can make a later change of terms easier.
His argument is that this arrangement would allow another shift in licensing after a weak financial period for the company behind Redis. He considers Valkey's permissive licence the better long-term option, even though it gives users fewer guarantees than a copyleft licence.
For Redict users, the practical takeaway is that the recommended destination is Valkey, and that the change is mainly a packaging exercise rather than a rewrite.
Sources
Spotted a mistake? See our corrections policy. Read how News by OnDevice works in our editorial policy.



