shouldiuse.io

Categories

VERDICT

Valkey Review

Depends

Should I use Valkey?

Not disclosed - valkey.io

· 1 month ago

Buy it if you need a fast cache or Redis replacement and can self-host or use a managed cloud plan. Skip it if you want a vendor support SLA or a no-ops experience.

Confidence

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

Ratings

  • Value for money
  • Ease of use
  • Feature depth
  • Support quality
  • Security posture

Pricing

Free

Self-hosted

ModelNot disclosed
Monthly feesNot disclosed
HardwareNot disclosed
Free tierYes
Managed (AWS, GCP, DigitalOcean, Elestio, Yandex)Usage-based

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

Gotchas - check before you buy

high

Exposed ports are a common attack path; lock down config before launch

medium

Managed serverless pricing confuses users; unit prices hide hourly floors

medium

Redis and Valkey now add different features — budget migration testing

medium

CVE history includes use-after-free and RCE flaws; stay on latest release

Pros and cons

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

Sources & method

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

official x2review x4security x2news x2
  • CVE-2026-56684 — use-after-free, Use-after-free vulnerability in Valkey
  • CVE-2026-63639 — RCE via use-after-free, Red Hat advisory: remote code execution via use-after-free flaw
  • CVE-2026-82631 — use-after-free, Use-after-free flaw in valkey-io valkey

Key stats

  • Value for money: 5/5

    Rating

  • Free

    Starting price

  • 10

    Sources

  • Analyzed

  • Value for money: 5/5. Free BSD core; managed plans undercut Redis
  • Ease of use: 3/5. Managed deploys in minutes; self-hosting needs ops
  • Feature depth: 4/5. Near-Redis parity; 9.x adds modules, RDMA, dashboards
  • Support quality: 2/5. Community plus cloud vendors; no commercial SLA
  • Security posture: 3/5. Fast patching, but repeated use-after-free CVEs
  • 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

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.

  • Redis

    The original; vendor-backed, faster-moving features, but license restrictions

    Valkey vs Redis
  • 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

Companies that use it

  • MaiCoin10
  • Braze
Full analysis

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

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

Methodology

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

Read how a report is made.

Sources

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

Add this review to your site

This check for Valkey says Depends.

Put the badge on your site.

Visitors see the independent review.

The link points here, and search engines follow it.

This is the badge visitors see on your site.

Paste one snippet. Keep the link as it is. A nofollow tag stops search engines from following it.

Rate this review

Anonymous. You can change your vote.

Loading votes…

Comments

One queue. No nested comments. Give a display name first. Limit: 200 words per comment and 7 comments per day. You can edit or delete yours.

Save a name to write a comment.

0 / 200 words

No comments yet.