ElastiCachetoRedis or Valkey

ElastiCache pricing and alternatives: Redis or Valkey, fully configurable

Redis or Valkey with the configuration your workload needs, run by engineers in our cloud, your cloud account or your data center.

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

  • Operated by AceMQ
  • Redis or Valkey
Amazon ElastiCache → OSStend · at a glance

Amazon ElastiCache pricing is only part of the picture. OSStend runs Redis or Valkey with full configuration, including the persistence, eviction and admin commands that ElastiCache restricts, and the customer picks the engine. ElastiCache remains the better fit for plain caches on AWS where parameter groups are enough.

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
Compare

Amazon ElastiCache and OSStend at a glance

ElastiCache is AWS's managed cache service for Redis OSS and Valkey. It is quick to start and tuned through parameter groups. OSStend suits teams that need direct control, a choice of engine or a place other than AWS.

OSStend
EnginesRedis or Valkey, your choiceRedis OSS, Valkey and Memcached node types and serverless (ElastiCache pricing)
ConfigurationFull Redis or Valkey configuration, changed on request by engineersOn clusters running Redis OSS, commands such as CONFIG, SAVE, BGSAVE, REPLICAOF and DEBUG are unavailable (AWS docs)
Where it runsOur cloud, your cloud account, your data centerAWS
PricingPrice drivers on pricing; sized per designSet by AWS; sample list prices are in the pricing section below (ElastiCache pricing)

Sources: AWS ElastiCache restricted commands and parameter groups, checked 9 Nov 2026, and ElastiCache pricing, checked 1 Nov 2026.

Operated by AceMQCompany figures, as published on acemq.com
160+customers served by AceMQ, which operates OSStend
10+years running open source data and messaging
24/7on-call engineers, not a ticket queue
Built for your workload

Why teams look for an alternative to ElastiCache

The most common reasons are control and place. The documented command restrictions limit tuning and persistence work, the service runs on AWS, and the Redis licence changes of 2024 and 2025 have made some teams reconsider which engine to run.

Area and managed serviceDocumented limitWhat OSStend does insteadSource
Admin commands and tuningAmazon ElastiCache (Redis OSS)On clusters running Redis OSS, AWS lists BGREWRITEAOF, BGSAVE, CONFIG, DEBUG, MIGRATE, REPLICAOF, SAVE, SLAVEOF, SHUTDOWN and SYNC as unavailable.What OSStend does insteadFull Redis or Valkey configuration, run by OSStend engineers.AWS docs, checked 30 Oct 2026 ↗

The second reason is the engine. Redis moved from a BSD licence to source-available licences in 2024 and added AGPLv3 with Redis 8 in 2025, while Valkey continues under BSD. The Redis vs Valkey comparison sets out the history and the choice.

A fair snapshot of Amazon ElastiCache

ElastiCache is the simplest way to put a cache beside an AWS application. If parameter groups give you the control you need and the cache stays on AWS, there is little reason to move.

  • It sits inside your AWS account and networking.
  • It offers both Redis OSS and Valkey nodes, so the engine question can be answered without leaving the service (ElastiCache pricing, checked 1 Nov 2026).
  • It suits caches where eviction and persistence defaults are acceptable.
Compare

Full comparison: OSStend and Amazon ElastiCache

OSStend is listed first. The ElastiCache column states only what the AWS documentation says, with the date checked.

FactorOSStend
Good fitCaches and session stores that need their own persistence, eviction and admin access; estates beyond AWSPlain caches on AWS where parameter groups are enough
Poor fitSmall caches with default settings, free tiers, self-serve sign-upWorkloads that need CONFIG, SAVE or REPLICAOF access (AWS docs), or that run outside AWS
Where it runsOur cloud, your cloud account, your data center, Kubernetes or OpenShiftAWS
TailoringPersistence and eviction settings, topology, engine and version chosen with youEngine settings through parameter groups (AWS docs)
MigrationReplication keeps the new nodes current while ElastiCache stays live; OSStend owns the cutoverYour team plans and runs it
Service levelsWritten SLA per plan (see service levels)AWS publishes its own SLA; compare its current terms with the service level you need
Pricing modelPrice drivers: engine, size, SLA tier, where it runs. See pricingPer node hour or serverless usage (ElastiCache pricing)

Sources: AWS ElastiCache restricted commands and parameter groups, checked 9 Nov 2026, and ElastiCache pricing, checked 1 Nov 2026.

Enterprise only

How OSStend does it

OSStend designs the cache around the workload, then runs it: persistence and eviction settings, replication and failover, and the engine you choose. The first step is a 45-minute workload review with an engineer: the current setup is reviewed, the design is sketched, and a price follows for that design.

Managed Redis or Valkey keeps your clients unchanged. Engineers have direct access to the configuration, so a change that needs CONFIG or a persistence adjustment is a request to an engineer, not a service limitation.

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.

There is no fixed menu here: the settings, node count and upgrade dates your workload needs are written into the design you sign off before anything is built, and that design is what OSStend runs.

Contact us if

  • You need persistence, eviction or replication settings that parameter groups do not expose.
  • You want to choose between Redis and Valkey, or switch later.
  • You run caches in more than one cloud or in a data center.
Talk to an engineer

Not a fit if

  • A plain cache on AWS with default settings: ElastiCache will cost less.
  • You want a free tier or a self-serve console.
Pricing

ElastiCache pricing: list prices and what ours depends on

AWS publishes ElastiCache prices per node hour and for serverless usage; the table shows three node sizes and the Valkey serverless rates. OSStend prices each design, and the drivers are published so the two are easy to compare: the engine, the size and replica count, the service level tier and where it runs.

ElastiCache, on demandValkey
cache.t4g.micro, per node hour$0.0128$0.016
cache.m7g.large, per node hour$0.1264$0.158
cache.r7g.large, per node hour$0.1752$0.219
Serverless, data stored per GB-hour$0.084$0.125
Serverless, per million ECPUs$0.0023$0.0034

US East (N. Virginia), USD. Source: AWS ElastiCache pricing, checked 1 Nov 2026; rates read from the AWS Price List file for ElastiCache published 14 Oct 2026. The pricing page repeats the r7g.large Valkey and the Valkey serverless rates in its worked examples. Backup storage and data transfer are billed separately.

Prices are quoted per design, after the workload review, so the figure is for the cluster you need rather than a plan size. Send the engine, rough size and where it must run, and the engineer prices that design.

When comparing, include replicas, backup storage and cross-zone traffic on the AWS side, and the service level you need on both. Full drivers are on pricing.

Fair notes on other options

Several routes exist besides OSStend. The right one depends on whether the problem is control, cost or the licence.

Illustrative: plan names and shapes stand in for any provider's menu.
Stay on ElastiCache and choose Valkey.
If the only concern is the Redis licence, ElastiCache supports Valkey today.
Redis Cloud or Redis Enterprise,
sold by Redis itself, for teams that want the vendor's own commercial features. See the Redis Enterprise comparison.
Another managed vendor.
Aiven lists Valkey as a service (Aiven pricing, checked 1 Nov 2026). Other managed vendors have their own pages, for example Instaclustr.
Another cloud's cache.
Caches that live in Azure have the Azure Managed Redis comparison, and serverless per-request Redis has the Upstash comparison.

How to choose

Choose by what you must control and where it has to run. Redis and Valkey behave the same for most application code, so the engine matters less than the operating model.

  1. If parameter groups are enough and the cache stays on AWS, keep ElastiCache.
  2. If the concern is the licence, compare the engines in Redis vs Valkey first.
  3. If you need admin commands, persistence control or a place beyond AWS, choose OSStend.
How it works

Moving off ElastiCache

The new nodes are built beside ElastiCache and kept current by replication. Clients switch once the new side is verified, with ElastiCache kept for rollback.

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

    An engineer reviews the current setup: sizes, settings, extensions or plugins, versions, traffic and where it must run.

  2. Design

    The cluster design is written and signed off before anything is built: size, topology, configs, versions and upgrade calendar.

  3. Move

    The new cluster runs beside the old one and stays current while the old service stays live. Traffic switches only when the new side is verified.

  4. Run

    Named engineers operate it 24/7: backups, patching, scaling and incident response, with upgrades on the customer's change calendar.

Talk to an engineer

Review your cache with an engineer

45 minutes: the current setup is reviewed 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.