---
title: "Redict is deprecated"
slug: redict-is-deprecated
url: https://listedarticles.com/articles/redict-is-deprecated
canonical_url: https://redict.io/posts/2026-11-17-redict-deprecated/
content_type: announcement
language: en
published_at: 2026-11-17T00:00:00.000Z
updated_at: 2026-11-17T10:46:21.819Z
author: "Drew DeVault"
authored_by: human
publisher: "Redict"
publisher_url: https://redict.io/
topics: ["open-source", "databases"]
license: all-rights-reserved
word_count: 189
reading_minutes: 1
citation: "Drew DeVault, Redict. \"Redict is deprecated.\" 17 Nov 2026. https://redict.io/posts/2026-11-17-redict-deprecated/ (all-rights-reserved)"
---

# Redict is deprecated

> Drew DeVault announces that Redict, the copyleft Redis fork, is officially deprecated with 7.3.6 as its final release, citing Valkey's success and Redis's return to a copyleft license, and recommends users switch to Valkey with simple migration steps.

I must unfortunately announce that Redict is officially deprecated, and Redict
7.3.6 is the final release.

I had hoped to rally the Redis diaspora around a copyleft initiative, to
protect ourselves from future rug-pulls, and made Redict to serve this purpose.
However, with the valkey project’s success, and Redis’s return to a copyleft
license, Redict was not able to build a sustainable community.

We recommend that Redict users switch to [valkey](https://valkey.io/), which
uses a permissive license but has better long-term prospects. We advise against
switching back to Redis; though it is once again open source, and copyleft, it
uses a contributor license agreement which will facilitate another rug-pull when
Redis has a bad financial quarter.

Switching to valkey is straightforward: if you install from your package
manager, simply install valkey and move your config file:

```
# mv /etc/redict.conf /etc/valkey.conf
```

If you use containers, simply pull the valkey container instead and ensure that
it runs with the appropriate config file.

Thanks to everyone who has contributed to Redict, endorsed the fork as the
future of Redis, and switched to it on their own machines. We had a good run :)
