Valkey Turns Redis Caching Commodity

This shifts core caching from a premium software category into a lowest cost infrastructure choice. Once Valkey gave cloud providers a neutral, BSD licensed fork with Linux Foundation governance, AWS and Google could sell Redis compatible caching as a standard managed service inside their own clouds. That weakens Redis's leverage on simple cache, session store, and queue workloads, because customers can keep the same API while buying from the provider that already runs their compute and billing.

• Valkey started in March 2024 as a Redis 7.2.4 fork under the Linux Foundation, with support from AWS, Google, Oracle, Ericsson, and Snap. That matters because enterprises read Linux Foundation governance as a signal that no single vendor can tighten licensing or control the roadmap alone.
  1 linuxfoundation 5 linuxfoundation
• AWS turned that governance shift into a direct pricing weapon. ElastiCache documents say Valkey is priced 20% below Redis OSS for node based deployments, and AWS has promoted up to 33% lower serverless costs plus in place migration from Redis OSS, which makes switching mostly an engine choice, not an app rewrite.
  3 amazon 4 amazon 6 amazon
• Google is following the same playbook. Memorystore for Valkey lets teams create a managed Valkey cluster from the Google Cloud console with the same networking, monitoring, scaling, and billing surface used for Redis. That makes Redis compatibility feel like a cloud feature, not a company specific product moat.
  2 sacra 7 google 8 google

The next battleground is above the cache layer. Basic key value storage will keep getting cheaper and more interchangeable, so Redis's path is to win on higher level data structures, search, vector workloads, and enterprise features that are harder for hyperscalers to flatten into a default cloud utility.