Redis Cloud Problems & Issues
SaasThe real-time data platform for modern apps
Redis Cloud delivers industry-leading performance for in-memory data with 99.999% SLA available. Main concerns: 2024 license change damaged community trust, memory-based pricing expensive at scale, Valkey fork fragmented ecosystem. Best for caching and real-time features where sub-ms latency justifies cost.
Should you use Redis Cloud?
TryRedis Cloud is worth trying for most users (score 70/100). Most reported issues: 2024 license change sparked community outrage and fork; Memory-based pricing gets expensive at scale; Key-value model limits complex data relationships. Not a good fit for: Teams with large datasets requiring persistence; Applications needing complex data relationships. Users most often switch to Valkey, AWS ElastiCache, Dragonfly.
Top problems
- 2024 license change sparked community outrage and fork
- Memory-based pricing gets expensive at scale
- Key-value model limits complex data relationships
Good for
- Applications needing sub-millisecond latency
- Budget-conscious startups needing caching
- Global applications needing local latency
Avoid if you are
- Teams with large datasets requiring persistence
- Applications needing complex data relationships
Common alternatives: Valkey, AWS ElastiCache, Dragonfly
Overview
Redis Cloud is the fully managed cloud service for Redis, the popular in-memory data store used for caching, session storage, real-time analytics, and more. Controversial license change in 2024 (BSD to SSPL) sparked Valkey fork. Redis 8 added AGPLv3 option in 2025. Plans start at $5/month (Essentials) or $0.881/hour (Pro).
Signals & Issues
Patterns extracted from real user feedback — not raw reviews.
In March 2024, Redis abandoned BSD license for SSPL/RSALv2, neither OSI-approved. This 'forced AWS and GCP to create their own fork' (Valkey). Core contributors migrated to forks. Redis 8 (2025) added AGPLv3 option but damage to trust was done.
Redis stores data in-memory, and 'having all data in memory can be very expensive.' Large datasets requiring low latency face steep costs. Users report 'difficulty scaling Redis without it becoming prohibitively expensive.' Memory costs compound quickly.
Redis Cloud Pro starts at $0.881/hour rather than fixed monthly. 'Real-time data workloads spike with launches, shrink when retired, and swing with usage patterns.' Costs can be unpredictable for variable workloads.
Redis uses key-value pairs to store data, making it 'unable to build complex data relationships.' Applications requiring joins, references, or relational queries need different solutions. Not a general-purpose database replacement.
Redis 'prioritizes performance over durability.' While persistence options exist (RDB, AOF), in-memory nature means data loss risk on failures without proper configuration. Not suitable as primary database for critical data.
March 2026 AWS me-central-1 zone issue affected Redis Cloud services. 'Timeline for full restoration remains unclear.' Cloud provider outages can impact Redis Cloud availability despite 99.999% SLA target.
Users report 'Redis private offering is not transparent' and 'one-way agreement where customers cannot disengage.' Reports of 'Redis continuing to invoice for unused services' and India support team 'not being collaborative.'
AWS ElastiCache 'remains limited to Redis 7.2, preventing access to future features.' The license change means cloud providers won't offer newer Redis versions. Users on AWS must choose between old Redis or Valkey fork.
Valkey (the AWS-backed fork) 'doesn't support newer Redis versions' and 'lags behind Redis 8 innovations' like hash field expiration, vector search, vector sets. Teams choosing Valkey for licensing miss newer features.
Redis 'requires significant RAM' to operate effectively. Datasets must fit in memory. As data grows, memory costs scale linearly. Disk-based alternatives may be more cost-effective for larger, less latency-sensitive data.
What Users Love
Sub-millisecond latency for real-time applications
Redis delivers sub-millisecond response times by keeping data in memory. Ideal for caching, session storage, real-time analytics, and leaderboards. When latency matters, Redis is hard to beat.
Rich data structures beyond key-value
Redis supports strings, hashes, lists, sets, sorted sets, streams, and more. Redis 8 adds vector sets for AI. More flexible than simple key-value stores while maintaining speed.
Essentials plan affordable at $5/month
Redis Cloud Essentials starts at just $5/month (250MB), making entry accessible. Includes high availability and backups. Good for smaller projects and development before scaling to Pro.
99.999% availability SLA on Pro plan
Redis Cloud Pro offers 99.999% availability ('five nines') with round-the-clock support. Active-active geo-replication enables global deployments with local latency. Enterprise-grade reliability.
Redis Query Engine for advanced queries
Redis Query Engine enables SQL-like queries, full-text search, and vector similarity search. Reduces need for separate search services. Redis Cloud-exclusive feature not in Valkey.
AGPLv3 option restored open-source path (Redis 8)
Redis 8 (2025) added AGPLv3 as a license option alongside SSPL/RSALv2. OSI-approved open-source option restored, addressing some community concerns. Self-hosting with open-source is possible again.
Pricing Plans
Users: N/A
Storage: 30MB
Limitations: No HA, no backups, no support, expires after trial period
Users: N/A
Storage: 250MB+
Limitations: No 99.999% SLA, limited data structures, single region
Users: N/A
Storage: Custom
Limitations: Usage-based can be unpredictable, requires cost monitoring
Users: N/A
Storage: Custom
Limitations: Requires sales engagement, minimum commitment likely
Features
Database
- In-Memory Data Store
Sub-ms latency
- Rich Data Structures
Strings, hashes, sets, etc.
- Complex Relationships
Key-value model
Search
- Redis Query Engine
Cloud exclusive
AI
- Vector Search
Redis 8+
Infrastructure
- Active-Active Geo-Rep
Pro plan
Reliability
- 99.999% SLA
Pro plan
Licensing
- OSI Open Source
AGPLv3 option (Redis 8)
Storage
- Disk-Based Storage
Memory only
Compatibility
- AWS ElastiCache Redis 8
License blocked
Who Should Use This?
Good Fit
Applications needing sub-millisecond latency
Redis excels at ultra-low latency use cases: caching, session storage, real-time leaderboards, pub/sub. When every millisecond matters and data fits in memory, Redis is the standard choice.
Budget-conscious startups needing caching
Essentials at $5/month is accessible for caching needs. Upstash offers serverless Redis alternative with free tier. For basic caching, either works without breaking the budget.
Global applications needing local latency
Redis Cloud Pro's active-active geo-replication provides local latency globally with automatic conflict resolution. 99.999% SLA for enterprise requirements. Expensive but capable.
AI applications needing vector similarity
Redis 8 adds vector search and vector sets for AI/ML workloads. Enables semantic search and RAG without separate vector database. Redis Query Engine provides unified search capabilities.
Neutral
AWS users needing latest Redis features
AWS ElastiCache is 'limited to Redis 7.2' due to license change. For Redis 8 features (vector sets, hash expiration), use Redis Cloud directly. Or accept Valkey, which lacks newer features.
Open-source advocates
Redis 8 added AGPLv3 option, restoring OSI-approved open-source path. However, the 2024 SSPL change damaged trust. Valkey (Linux Foundation, BSD) is the pure open-source alternative backed by AWS/GCP.
Avoid
Teams with large datasets requiring persistence
Redis 'prioritizes performance over durability' and 'having all data in memory can be very expensive.' For large datasets where millisecond latency isn't critical, consider PostgreSQL, DynamoDB, or disk-based alternatives.
Applications needing complex data relationships
Redis uses key-value pairs, 'unable to build complex data relationships.' For joins, references, and relational queries, use PostgreSQL or MongoDB. Redis is a cache/real-time store, not a primary database.
Regret Patterns
Common buyer's remorse scenarios reported by users.
Teams chose Redis for speed but found 'having all data in memory can be very expensive.' As datasets grew, costs scaled linearly with memory. Should have evaluated whether all data needed sub-ms latency or if disk-based alternatives sufficed for some workloads.
Organizations using AWS/GCP ElastiCache found Redis versions frozen at 7.2 after license change. New features required either Redis Cloud directly (different billing) or accepting Valkey (missing features). Strategic planning disrupted.
Teams treated Redis as primary storage, then experienced data concerns when realizing it 'prioritizes performance over durability.' In-memory nature means risk without proper persistence configuration. Should have used traditional database for critical data.
Started with Pro for dedicated infrastructure, but $0.881/hour (~$640/month minimum) plus memory scaling exceeded budget. 'Real-time workloads spike unpredictably' making cost forecasting difficult. Essentials or Upstash would have been more predictable.
Application needed relational data, but Redis is 'unable to build complex data relationships.' Attempted workarounds with multiple keys and manual references became unmaintainable. PostgreSQL or MongoDB would have been correct choice.
When It Breaks Down
Scenarios where this product tends to fail users.
Application data grows beyond what memory-based pricing allows. Costs become prohibitive. Team must implement tiered storage strategy, move cold data elsewhere, or migrate to disk-based alternative for some workloads.
ElastiCache stuck at Redis 7.2, but application needs Redis 8 features (vector search, hash expiration). Must migrate to Redis Cloud directly, losing AWS billing consolidation and native integration.
Team didn't configure RDB/AOF persistence correctly. Instance restart or failure loses data. Redis 'prioritizes performance over durability' - proper configuration was required but not understood.
Requirements evolve to need joins, complex aggregations, and relational integrity. Redis key-value model can't support these. Must implement separate database for relational data, adding complexity.
Organization policy requires OSI-approved licenses only. Redis 7.4 SSPL doesn't qualify. Must migrate to Valkey (BSD) or wait for Redis 8 AGPLv3. License evaluation should have happened upfront.
Alternatives Users Switch To
Valkey
9x mentionedLinux Foundation fork after Redis license change. Gain: BSD open source, AWS/GCP backing, ElastiCache support. Trade-off: stuck at Redis 7.2 compatibility, no Redis 8 features.
AWS ElastiCache
7x mentionedAWS managed caching. Gain: Valkey or Redis 7.2, AWS integration, reserved pricing. Trade-off: no Redis 8+, Valkey lacks some features, VPC-only networking.
Upstash
7x mentionedServerless Redis alternative with free tier. Gain: pay-per-request pricing, scales to zero, global replication. Trade-off: different billing model, REST API adds latency vs direct connection.
Dragonfly
5x mentionedRedis-compatible with better memory efficiency. Gain: claims 25x throughput, lower memory use, drop-in Redis replacement. Trade-off: newer project, smaller ecosystem.
KeyDB
4x mentionedMulti-threaded Redis fork. Gain: better multi-core performance, active-active replication, BSD license. Trade-off: less commercial support, smaller community.
Frequently Asked Questions
See how Redis Cloud compares in our Best Database Software rankings, or calculate costs with our Budget Calculator.
Work at Redis Cloud or spotted something outdated? Suggest a correction — we verify every change against public sources. See our methodology.