Comparison

Valkey vs Redis: which to run after the licence change

Redis changed its licence twice in 2024 and 2025. Valkey, a fork of Redis 7.2, stayed under BSD. Here is how to choose, and how a switch works.

45 minutes with an engineer: we review your workload and sketch the design.

  • Operated by AceMQ
  • Redis or Valkey
  • Checked 15 Nov 2026
redis-vs-valkey

Valkey vs Redis: Valkey 9.1.3 is BSD-licensed and the right default for new deployments that want a BSD engine. Redis 8.10.3 is a good choice if its AGPLv3 option suits your policies or you need Redis itself. Both were current on 15 Nov 2026. Stay on Redis 7.2 or earlier if it works, and test before moving.

160+AceMQ customers
10+Years running these systems
24/7Engineers on call
3Places it runs: our cloud, yours, your data center
Engines we run, on the platforms you already use
  • PostgreSQL
  • MySQL
  • MongoDB
  • Redis
  • Valkey
  • OpenSearch
  • Kafka
  • RabbitMQ
  • AWS
  • Google Cloud
  • Azure
  • Kubernetes
  • OpenShift
  • Prometheus
  • Grafana
  • Datadog
  • Dynatrace
  • Splunk

Redis vs Valkey side by side

Valkey and Redis share a history up to Redis 7.2. They differ in licence, governance and which features sit beyond that point. The table gives the facts that matter for a hosting or procurement decision.

Valkey
LicenceBSD7.2 and earlier: BSD. 7.4 up to Redis 8: source-available licences (RSAL and SSPL). Redis 8 and later: your choice of RSALv2, SSPLv1 or AGPLv3
Latest release, 15 Nov 2026Valkey 9.1.3, 26 Oct 2026; 9.2.0 release candidate 2 on 4 Nov (GitHub releases)Redis 8.10.3, 26 Oct 2026; 8.12 release candidate 3 on 12 Nov (GitHub releases)
OriginA Linux Foundation fork of Redis 7.2The original project
Run by cloud providersUsed by AWS, Google and AivenSold as Redis Cloud and Redis Enterprise by Redis itself
Run by OSStendYes; the customer chooses the engineYes; the customer chooses the engine
Best forNew deployments that want a BSD engineTeams that need Redis itself, or can accept AGPLv3

Sources: InfoQ on Redis 8 and AGPL, May 2025; OSStend GTM brief v8.2 for the 7.2 BSD line, the Valkey fork and its hosts. Licences and releases re-read on 15 Nov 2026 from redis.io licences, the Valkey site and the two GitHub release pages. Licence notes are a summary, not legal advice.

Current releases and support lines

On 15 Nov 2026 the latest stable releases were Valkey 9.1.3 and Redis 8.10.3, both published on 26 Oct 2026 (Valkey, Redis, checked 15 Nov 2026). Valkey ships a major version about every six months; Redis 8.0 was released on 2 May 2025.

Valkey
Major versions since the licence change8.0 (15 Sep 2024), 8.1 (31 Mar 2025), 9.0 (21 Oct 2025), 9.1 (19 May 2026)8.0 (2 May 2025), 8.2 (4 Aug 2025), 8.4 (18 Nov 2025), 8.6 (10 Feb 2026), 8.8 (25 May 2026), 8.10 (29 Jul 2026)
Patched lines on 26-27 Oct 20267.2.15, 8.0.12, 8.1.11, 9.0.7, 9.1.37.2.17, 7.4.12, 8.2.11, 8.4.8, 8.6.8, 8.8.4, 8.10.3
Next release in testing9.2.0 release candidate 2, 4 Nov 20268.12 release candidate 3, 12 Nov 2026

Dates are release dates on each project's GitHub release page; the Valkey site lists 9.1.3 as the latest release and 9.0.7, 8.1.11, 8.0.12 and 7.2.15 as the latest of past releases (valkey.io). Checked 15 Nov 2026. A patch line on this table is not a support commitment: confirm support terms with the project or vendor.

Both projects patch older lines at the same time as new ones, so staying on a release line for a while is practical. The licence still follows the version: a Redis line at 7.4 or later is source-available or AGPLv3 depending on the version and the option you take, while every Valkey line is BSD.

How the two were compared

The comparison uses public licence announcements, project documentation and the experience of AceMQ engineers who run Redis and Valkey for customers. No benchmark numbers are quoted, because none were sourced for this page.

Each factor below was checked against the sources named in the table note on 15 Nov 2026. Where a factor depends on your workload, the page says so and recommends a test on your own data.

Licence history

Redis was BSD licensed until version 7.2. In March 2024 it moved to source-available licences, and in May 2025 Redis 8 added AGPLv3, an OSI-approved open source licence (InfoQ). Redis now says a user may pick RSALv2, SSPLv1 or AGPLv3 for Redis 8 and later (redis.io, checked 15 Nov 2026). Valkey was forked from Redis 7.2 and stays BSD (valkey.io, checked 15 Nov 2026).

  • Redis 7.2 and earlier: BSD.
  • Redis 7.4 up to Redis 8: RSAL and SSPL, which do not allow offering Redis as a hosted service on the same terms as BSD.
  • Redis 8 and later: your choice of RSALv2, SSPLv1 or AGPLv3. Redis says RSALv2 bars offering it as a managed service and calls SSPLv1 source-available, not open source; AGPLv3 is open source and requires source for modifications on distribution.
  • Valkey: BSD, a Linux Foundation fork of Redis 7.2 that keeps compatibility with Redis OSS 7.2 and earlier (Valkey migration guide, checked 15 Nov 2026).

Some enterprises have policies against AGPL software, and AWS and Google run Valkey. Check your own policy before choosing.

Compatibility with your applications

Valkey started as a fork of Redis 7.2, so applications written against that line are the easiest to move. Features added to Redis after the fork need to be checked one by one.

In practice most clients and commands behave the same. The risk sits in modules, newer data structures and commands added in later Redis versions. A review of the commands and modules your applications use settles it before any cutover.

Performance

No sourced benchmark is quoted on this page. Performance depends on the workload, the data size and the settings, so the dependable method is to test both engines on a copy of your own data.

OSStend can run both engines for the same workload during the design review, so the choice rests on your numbers rather than a vendor chart.

When to stay on Redis

Stay on Redis when it works and the licence fits. A move needs a reason, not just a licence headline.

  • You run Redis 7.2 or earlier under BSD and have no need to upgrade.
  • Your policy accepts AGPLv3 and you want Redis 8 features.
  • You use Redis Enterprise features from Redis itself.
  • Your applications depend on modules or commands that Valkey does not have.
How it works

How a switch from Redis to Valkey works

A switch runs the new engine beside the old one, keeps it current by replication, verifies it and then moves clients across, with the old engine kept for rollback. The Redis to Valkey migration guide has the detail.

Illustrative: each phase is planned and rehearsed with your team before traffic moves.
  1. Inventory

    List the commands, modules, persistence and eviction settings in use.

  2. Build

    Stand up Valkey to the signed-off design, beside the existing Redis.

  3. Replicate and test

    Keep the new engine current and run the application's tests against it.

  4. Cut over

    Move clients in stages, and keep Redis available for rollback.

Enterprise only

Where OSStend fits

OSStend runs both engines, and the customer chooses. Managed Redis or Valkey is designed around the workload and run 24/7 by AceMQ engineers, in our cloud, your cloud account or your data center. Leaving ElastiCache? See the ElastiCache comparison. Weighing Redis's own commercial offering? The Redis Enterprise comparison covers its plans and price floor.

Redis 7.2 and earlier are BSD-licensed. From Redis 7.4 Redis is dual-licensed under RSALv2 and SSPLv1 (Redis, 20 Mar 2024), and Redis 8 adds AGPLv3 as a further option (Redis, 1 May 2025), both checked 31 Oct 2026. Valkey stays BSD-licensed. Which engine and version a cluster runs, and the licence that comes with it, is settled in the design review.

Contact us if

  • You want either engine run for you, with direct access to configuration.
  • You need the choice reviewed against your own workload.
Talk to an engineer

Not a fit if

  • You only need a small cache with default settings on AWS: ElastiCache will cost less.
  • You want a free tier or self-serve sign-up.
FAQ

Valkey and Redis questions

Talk to an engineer →

What is Valkey?

Valkey is a BSD-licensed fork of Redis 7.2, maintained under the Linux Foundation. Its latest release on 15 Nov 2026 was Valkey 9.1.3. Several cloud providers, including AWS and Google, use it.

Is Valkey a drop-in replacement for Redis?

For applications written against Redis 7.2 and earlier, usually yes. Modules and features added to Redis later need checking before a move.

Is Redis open source again?

Redis 8 and later can be used under AGPLv3, an OSI-approved open source licence, or under RSALv2 or SSPLv1, which are source-available (redis.io, checked 15 Nov 2026). Versions from 7.4 up to Redis 8 used source-available licences only.

Does Amazon ElastiCache run Valkey?

Yes. ElastiCache supports both Redis OSS and Valkey, though it restricts some admin commands and runs on AWS only.

Which one should a new project use?

Valkey is the simplest default for a BSD engine. Choose Redis 8 if AGPLv3 suits your policies or you need Redis itself, and test your workload on both.

Talk to an engineer

Choose the engine with an engineer

45 minutes: your commands and modules are checked and the Redis or Valkey design is sketched.

  • A design sketch for your workload, not a plan menu
  • A zero-downtime cutover path for what you run today
  • A price for that design, after the review
See pricing →

Your request goes to the OSStend team. No newsletter sign-up.

Get a quoteTalk to an engineer
2Engines
3Where should it run?
4What do you need?

Your request goes to the OSStend team. No newsletter sign-up.