Skip to content

An open-source, in-memory key/value datastore for caching, queues and primary-database use, forked from Redis and backed by the Linux Foundation.

Open-source alternative to:

BSD-3-ClauseSelf-hostedNot yet assessed
Screenshot of the Valkey website
Homepage of valkey.io

What the free edition leaves out

Scroll sideways to view all columns →

We have not been able to confirm enough from official sources to give a verdict. “Not confirmed” means the official pages we read did not say, so we do not guess.

Open-core feature checklist for Valkey
FeatureFree editionDetailsSource
SSO / SAMLNot confirmedSingle sign-on is not described on the pages read. The docs describe ACL users that authenticate with a password or a TLS certificate.Source ↗
Role-based access controlFreeThe ACL documentation describes limiting connections by command and key access per user.Source ↗
Audit logsNot confirmedAudit logs are not described on the pages read.Source ↗
Multi-user / teamsFreeThe ACL documentation describes multiple user accounts, each with its own password or certificate-based login and limits.Source ↗
Backups and restoreFreeThe persistence documentation describes RDB snapshots and the append-only file, and recommends RDB files for backups.Source ↗
API accessNot confirmedClients talk to Valkey through its network protocol and commands; an HTTP or REST API is not described on the pages read.Source ↗
Support SLANot confirmedNo paid support or SLA is described on the project's pages read.Source ↗

Best for

Teams that run Redis-style caching, queues or session storage and want it under a permissive open-source license with neutral governance.

Why choose it over Redis

The code is BSD-3-Clause, and the project's homepage says it is backed by the Linux Foundation and will stay open source. Valkey's history page says Redis Ltd. moved Redis in 2024 from the BSD license to dual source-available licenses (RSALv2 and SSPLv1), which the page says are not open source licenses, and that Valkey continues from the BSD-licensed code. It supports standalone and cluster modes, replication, Lua scripting and loadable modules.

Where it falls short

The project's pages describe the software and its community only; no official managed service or paid support is described, so you run replication, persistence and upgrades yourself. As a fork it is a separate codebase from Redis, so check client and module compatibility for the versions you use.

Open-source alternative to

  • Redis — Valkey's repository README and history page say it was forked from Redis just before Redis moved to source-available licenses, so it can replace Redis for people who want to stay on the BSD-licensed code.

Category

Backend & Databases

Topics

Tech stack

Languages as reported by GitHub for the repository.

Share: