maintenance. Releases since 2025 only backport security fixes (latest 7.3.6, Oct 2025); Valkey is the more active Redis fork.
Overview
Redict was forked from the last BSD-licensed Redis (7.2.4) in March 2024 by Drew DeVault and contributors, with new changes under LGPL-3.0-only and no contributor licence agreement so it can never be relicensed by one company. It aimed to be a stable, conservative Redis rather than a feature-driven one, hosted on Codeberg. In practice Valkey absorbed most of the community momentum, and Redict's recent releases (through 7.3.6 in October 2025) are mainly CVE fixes backported from Valkey. It works as a drop-in Redis 7.2, but there is little reason to choose it for new deployments.
Strengths & trade-offs
Strengths
- +Copyleft license without a CLA protects against future relicensing
- +Drop-in compatible with Redis 7.2 clients and data files
- +Conservative, stability-focused scope
Trade-offs
- −Little feature development since 2024
- −Small contributor base compared with Valkey
- −Few distro packages and no managed offerings
Great for
- +Organisations that require a copyleft-licensed Redis
- +Stable Redis 7.2-compatible deployments
Think twice for
- −New projects wanting active development (use Valkey)
- −Teams that need managed cloud options
Capabilities
Native or official first-party support · 9 of 25 tracked
Scale & consistency
- Comfortable data size
- Medium · ≤ 10 TB
- Horizontal scaling
- Native
- Multi-region
- No
- Transactions
- Limited ACID
- Consistency
- Eventual
- Schema
- Schemaless
- Architecture
- In memory, Single node, Primary replica, Distributed, Client server
- Query languages
- Redis commands (RESP), Lua
Same cluster model as Redis 7.2.
Deployment
Ecosystem
Alternatives to Redict
The Linux Foundation's BSD-licensed fork of Redis, now the default engine on AWS and Google Cloud.
redict vs valkey →The in-memory data structure server that became the default cache, now with search, JSON and vectors built in.
redict vs redis →Snap's multi-threaded Redis fork with active-active replication and FLASH storage, now dormant.
redict vs keydb →A multi-threaded, shared-nothing in-memory store that speaks Redis and Memcached on one big box.
redict vs dragonfly →Serverless, per-request-priced Redis with an HTTP API built for edge and serverless functions.
redict vs upstash →Managed Valkey and serverless cache/pub-sub from ex-DynamoDB engineers, plus self-hosted Valkey tooling.
redict vs momento →Redict FAQ
What is Redict?
Redict is a key-value database by Redict community, first released in 2024. Redict was forked from the last BSD-licensed Redis (7.2.4) in March 2024 by Drew DeVault and contributors, with new changes under LGPL-3.0-only and no contributor licence agreement so it can never be relicensed by one company. It aimed to be a stable, conservative Redis rather than a feature-driven one, hosted on Codeberg. In practice Valkey absorbed most of the community momentum, and Redict's recent releases (through 7.3.6 in October 2025) are mainly CVE fixes backported from Valkey. It works as a drop-in Redis 7.2, but there is little reason to choose it for new deployments.
Is Redict open source?
Yes. Redict is open source. License: LGPL-3.0-only (new code); BSD-3-Clause (inherited).
Does Redict support ACID transactions?
Partly. Redict offers limited ACID guarantees (for example, single-record or single-partition transactions), with eventual consistency.
Does Redict scale horizontally?
Redict scales horizontally out of the box, with built-in sharding or partitioning. It is comfortable at medium scale (≤ 10 TB).
How can I run Redict?
You can self-host it.
What is Redict best for?
Redict is a strong fit for organisations that require a copyleft-licensed Redis and stable Redis 7.2-compatible deployments. Think twice for new projects wanting active development (use Valkey).
What are the best alternatives to Redict?
Common alternatives to Redict include Valkey, Redis, KeyDB, Dragonfly and Upstash. The right choice depends on your workload, scale and hosting; WhichDB's smart match ranks them against your requirements.
Is Redict still maintained?
Redict is in maintenance mode. Releases since 2025 only backport security fixes (latest 7.3.6, Oct 2025); Valkey is the more active Redis fork.
How popular is Redict?
Redict ranks #599 of 844 databases on the WhichDB Score (0.9/100), and #106 among key-value databases. The score combines public adoption signals such as package downloads, GitHub activity, job posts and developer discussion.