shouldiuse.io

Report

Should I Use Valkey?

valkey.io·Analyzed 2 hours ago·Based on 10 sources

Depends

Depends

Buy it if you need a fast cache or Redis replacement and can self-host or use a managed cloud plan.

Free, BSD-licensed Redis fork backed by AWS and Google. Great cache if you run ops; not a supported product.

Confidence: Medium

Free / BSD

Price

Open source, no license fees

2024

Forked from Redis

Branched from Redis 7.3

Linux Foundation

Governance

Backed by AWS, Google, Oracle

AWS, GCP, DigitalOcean

Managed on

Also Elestio and Yandex Cloud

Value for money5

Free BSD core; managed plans undercut Redis

Ease of use3

Managed deploys in minutes; self-hosting needs ops

Feature depth4

Near-Redis parity; 9.x adds modules, RDMA, dashboards

Support quality2

Community plus cloud vendors; no commercial SLA

Security posture3

Fast patching, but repeated use-after-free CVEs

Pros

  • Free, BSD-licensed; no vendor license changes to fear
  • Linux Foundation project with AWS, Google, Oracle backing²
  • Compatible with Redis OSS clients and ElastiCache workflows
  • Fully managed deployment available in minutes via Elestio
  • Active release cadence with regular security fixes

Cons

  • No single commercial vendor behind it; no support contract²
  • Fork divergence from Redis adds migration and ecosystem risk
  • Repeated use-after-free CVEs, including RCE-class bugs
  • Some Redis-community skeptics claim adoption stalled

Gotchas

  • highExposed ports are a common attack path; lock down config before launch
  • mediumManaged serverless pricing confuses users; unit prices hide hourly floors
  • mediumRedis and Valkey now add different features — budget migration testing
  • mediumCVE history includes use-after-free and RCE flaws; stay on latest release

Best for

  • High-traffic caching and session stores
  • Teams already on AWS or GCP managed cache
  • Redis OSS users avoiding license-change risk
  • Self-hosters wanting permissive BSD licensing

Not for

  • Tiny projects — a simple managed cache is less work
  • Anyone needing a vendor SLA and support contract
  • Teams relying on Redis-8+ exclusive features; the forks have diverged
  • Buyers wanting a polished, no-ops dashboard product

Companies that use it

  • MaiCoin10
  • Braze

Pricing

Self-hosted

Free

  • Full feature set
  • BSD license
  • You own operations and patching

Managed (AWS, GCP, DigitalOcean, Elestio, Yandex)

Usage-based

  • Pay per node or serverless
  • Cheapest AWS node class: cache.t4g.micro
  • Serverless billed per request units

Security

Actively patched open-source project, but a track record of use-after-free CVEs including RCE — secure your deployment and patch fast.

  • CVE-2026-56684 — use-after-freeUse-after-free vulnerability in Valkey
  • CVE-2026-63639 — RCE via use-after-freeRed Hat advisory: remote code execution via use-after-free flaw
  • CVE-2026-82631 — use-after-freeUse-after-free flaw in valkey-io valkey

What users say

Developer sentiment is mixed: strong respect for the engineering team and momentum, alongside skeptics calling adoption slow.

It never really took off.
Reddit, r/redis
Kinda took it a long time, actually.
Reddit, r/linux
Valkey is run by incredibly talented de…
Reddit, r/devops

Alternatives

Compare Valkey with each alternative.

DragonflyDB

Redis-compatible, multi-threaded; different performance tradeoffs at scale

KeyDB

Redis-compatible fork with multithreading; simpler feature surface

Memcached

Dead-simple pure caching if you don't need data structures

Full analysis

Based on ~40 public sources including official docs, Reddit threads, CVE databases, and cloud vendor pages

Sources

  1. official
  2. news
  3. official
  4. review
  5. review
  6. security
  7. security
  8. review
  9. review
  10. news

Rate this review

Anonymous. You can change your vote.

Loading votes…

Ask a follow-up

Ask if a use case fits. Answers stay inside this report and its sources.