HotKV Cloud vs Amazon ElastiCache

An ElastiCache alternative with a different engine

An ElastiCache alternative usually means the same engine somewhere else. HotKV Cloud is a different engine. ElastiCache runs Valkey, Redis OSS or Memcached on AWS. HotKV runs a multi-threaded engine that speaks the same Redis protocol, on a dedicated machine per instance. Your clients stay the same.

Get early access See the measurements
more throughput

ElastiCache

1 shard, plus replicas

node

node

node

node

node

node

node

node

HotKV Cloud

1 machine, 4 of 16 cores busy

one isolated machine

An illustration, not a measurement. ElastiCache's Valkey and Redis OSS engines execute commands on one thread per node, so more throughput means more shards and replicas to size. One HotKV instance uses more of its own cores.

This ElastiCache alternative, run as a single instance on one 160-vCPU machine, led 12 of 12 commands against Valkey 9.1.2, at 8.6x to 56.6x the throughput. HotKV was built from source for that CPU. Valkey 9.1.2 ran as its stock build. The gap is smaller on small machines.

Drop-in

What stays the same with this ElastiCache alternative

HotKV implements the Redis wire protocol. Moving from Amazon ElastiCache is usually a change of host and credentials. Check the command reference for anything outside the core set.

Same protocol

Redis-compatible. RESP2 and RESP3 with HELLO negotiation, and HotKV reports Redis version 8.4.0 to clients, so libraries pick their features by it. Connection strings, pipelines, pub/sub and transactions work as they do today.

Same clients and tools

Redis and Valkey client libraries, redis-cli, redis-cli --cluster and GUI tools connect to HotKV without code changes for the core commands.

Same core commands

300 core commands, Lua scripting and function libraries, plus HotKV's own command families when you want them.

the client you already use
$ redis-cli -h <your-hotkv-host> -p 6379 --tls --user app --askpass
> HELLO 3
1# "server" => "hotkv"
2# "version" => "8.4.0"
3# "proto" => (integer) 3
   ... (four more fields)
> SET session:4821 "same protocol, every core"
OK
> GET session:4821
"same protocol, every core"
> TAG.SET session:4821 tenant:acme   # a HotKV command, when you want it
(integer) 1

The case for an ElastiCache alternative

Why teams look for an ElastiCache alternative

Documented properties of Amazon ElastiCache that send teams looking for an ElastiCache alternative, checked on October 21, 2026.

01

The engines execute commands on one thread

Valkey and Redis OSS execute commands on a single main thread per node. Throughput beyond one node comes from sharding across more nodes, which you size, pay for and rebalance. An ElastiCache alternative with a multi-threaded engine scales inside one machine first.

02

Pricing per node-hour or per use

Node-based caches are billed hourly per node by node type. ElastiCache Serverless is billed on data stored in GB-hours and on ECPUs consumed, so it moves with traffic. Data transfer follows the AWS price list.

03

An AWS service

ElastiCache is an AWS service and runs in AWS Regions and on AWS Outposts. This ElastiCache alternative runs on Google Cloud in 42 regions as HotKV Cloud. As HotKV On-Premise it runs in any cloud account or data centre under a licence.

04

AI workloads need more services

A prompt cache, semantic cache, agent memory and LLM cost tracking are not commands of Valkey or Redis OSS. On HotKV they are command families of the same server, on the Performance plan and above.

Measured, not claimed

This ElastiCache alternative, measured. HotKV vs Valkey 9.1.2 and Redis 8.10.2 on one machine

HotKV Ltd measured Valkey 9.1.2 and Redis 8.10.2, the open-source engine families behind ElastiCache. Both ran as self-hosted single instances on the same machine as HotKV. Amazon ElastiCache itself was not measured. It offers Valkey 9.1 and Redis OSS 7.x builds of its own, so the exact builds differ from the ones measured. The figures show the engines behind the service, the fair baseline for an ElastiCache alternative.

12 of 12
commands where HotKV measured the highest throughput against Valkey
8.6x to 56.6x
HotKV's throughput as a multiple of Valkey's, across the 12 commands it led (MGET to SADD)
None
commands where Valkey measured higher

HotKV Ltd built HotKV from source for this CPU. Valkey ran as its stock release build. Both ran as single instances. Thread counts followed each product's documented all-core setting and were not tuned per product. The gap is smaller on machines with few cores.

SET17.5x
HotKV
50.5M*
Valkey
2.9M
GET22.5x
HotKV
36.6M*
Valkey
1.6M
MGET8.6x
HotKV
4.6M*
Valkey
537K
SETNX29.7x
HotKV
55.3M*
Valkey
1.9M
APPEND19.4x
HotKV
25.1M
Valkey
1.3M
INCR47.3x
HotKV
90.8M
Valkey
1.9M
LPUSH37.5x
HotKV
31.6M
Valkey
842K
RPUSH49.8x
HotKV
43.8M
Valkey
878K
SADD56.6x
HotKV
50.6M*
Valkey
894K
HSET37.1x
HotKV
29.0M*
Valkey
782K
MSET24.3x
HotKV
11.3M
Valkey
465K
PING36.0x
HotKV
125.2M†
Valkey
3.5M

Operations per second, median of 3 runs of 10 seconds. Each pair of bars scales to the faster server on that command.

* Network-limited: the instance's network set this result, so the server's own limit is higher.

† Load-generator-limited: the load-generator machines ran above 85% CPU, so this is their ceiling, not the server's.

Azure D160alds_v7 (AMD EPYC 9V45 (Turin), 160 vCPUs), measured October 9, 2026. 256-byte values, pipeline depth 30, 5,000,000 prefilled keys read uniformly at random. Three dedicated load-generator machines. Every server ran alone as a single instance with persistence off. Each got all cores (Redis 128 I/O threads, its maximum). HotKV Ltd built HotKV from source for this CPU and ran Valkey as its stock release build. Full method and results · Harness and raw data

Side by side

This ElastiCache alternative and Amazon ElastiCache, feature by feature

FeatureHotKVAmazon ElastiCache
EngineHotKV, multi-threaded, C++20Valkey, Redis OSS or Memcached
Command executionMulti-threaded. Every core reads, parses and executes commands on one shared storeSingle main thread per node (Valkey, Redis OSS)
ProtocolRedis-compatible: RESP2 and RESP3 with HELLO negotiation. Reports Redis version 8.4.0 to clientsRESP2 and RESP3 (Valkey, Redis OSS); Memcached protocol
Instance modelEvery HotKV Cloud instance is its own isolated machine with dedicated vCores, RAM and diskNode-based clusters you design, or Serverless
BillingPer instance, billed monthly or yearly in advance and priced per region. Outbound traffic is bundled, with top-up packs. When a bundle is used up, outbound traffic pauses. HotKV Cloud does not bill overage on outbound trafficHourly per node by node type, or GB-hours and ECPUs on Serverless. Data transfer per the AWS price list
Availability SLANone on Starter, 99.9% on Performance, 99.95% on ScalePer the AWS service level agreement
LLM prompt and semantic cacheBuilt in (PCACHE.*, SCACHE.*), Performance plan and above on HotKV CloudNot an engine feature
AI agent memoryBuilt in (AMEM.*), Performance plan and above on HotKV CloudNot an engine feature
LLM token and cost trackingBuilt in (LLMBUDGET.*, LLMSTATS.*), Performance plan and above on HotKV CloudNot an engine feature
MetricsBuilt in. The server serves /metrics itself once metrics-port is set (on-premise)CloudWatch metrics
Key taggingYes (TAG.*)No
Nanosecond TTLYes (NEXPIRE, NTTL)No. Millisecond TTLs
ClientsRedis and Valkey client libraries, redis-cli, redis-cli --cluster and GUI tools connect without code changes for the core commandsValkey, Redis OSS and Memcached clients

In fairness

Where Amazon ElastiCache is ahead of this ElastiCache alternative, or simply different

This ElastiCache alternative page is only useful when it says this part too.

  • ElastiCache integrates with the rest of AWS, with IAM, VPC networking, CloudWatch and reserved-node pricing. If your stack is AWS end to end, that integration has real value.
  • ElastiCache Serverless removes capacity planning entirely and scales with use. HotKV Cloud instances have a fixed size that you upgrade in place.
  • ElastiCache also offers Memcached. HotKV speaks the Redis protocol only.
  • This ElastiCache alternative is in early access and runs on Google Cloud. For workloads that must stay inside AWS, HotKV On-Premise runs in your own AWS account.

Moving over

From Amazon ElastiCache to this ElastiCache alternative in four steps

What switching to an ElastiCache alternative involves in practice.

  1. 1

    Create an instance

    Pick a region and a plan in the HotKV Cloud console. The instance is a machine of its own, provisioned, patched and monitored for you.

  2. 2

    Point your clients at it

    Keep the client library you already use. Change the host, port and credentials from ElastiCache to the HotKV instance. TLS and password authentication are on from the start, with ACL users available. An ElastiCache alternative that speaks the same protocol needs no client changes for the core commands.

  3. 3

    Move the data

    Use the tools you already know. DUMP and RESTORE, MIGRATE, or a replay of your writes all work, because HotKV implements these commands.

  4. 4

    Turn on what was missing

    Vector search and key tagging are core commands on every plan. Prompt and semantic caches, agent memory and LLM cost tracking are commands of the same server on the Performance plan and above. No module, sidecar or second service. That is what an ElastiCache alternative should add.

Questions

Questions about this ElastiCache alternative

Will my ElastiCache clients work with this ElastiCache alternative?

Yes, for the Valkey and Redis OSS engines. They use RESP2 and RESP3, which HotKV implements. The same client libraries connect to a HotKV instance after a change of host and credentials. Memcached clients use a different protocol and do not.

Did you benchmark ElastiCache?

No. HotKV Ltd measured Valkey 9.1.2 and Redis 8.10.2, the open-source engines behind ElastiCache. Both ran as self-hosted single instances on the same 160-vCPU machine as HotKV. The managed service, its instance types and the builds it offers were not measured, so the figures describe the engines.

Can an ElastiCache alternative keep my data in AWS?

HotKV Cloud runs on Google Cloud. If your data must stay in AWS, HotKV On-Premise runs in your own AWS account under a licence. The engine is the same.

How is HotKV Cloud billed?

This ElastiCache alternative bills per instance, monthly or yearly in advance, priced live per region at checkout. Outbound traffic is bundled with each plan and can be topped up. When a bundle is used up, outbound traffic pauses. HotKV Cloud does not bill overage on outbound traffic.

Put this ElastiCache alternative to the test with the clients you already have

HotKV Cloud is opening in waves. Every instance of this ElastiCache alternative is a dedicated machine with the multi-threaded engine. The AI command families come with the Performance and Scale plans.

Get early access Pricing

How this comparison was made

This page compares HotKV with Amazon ElastiCache as an ElastiCache alternative. Statements about Amazon ElastiCache describe its publicly documented properties. HotKV Ltd checked them on October 21, 2026 against the pages listed below. They may change as the product changes. Throughput figures are HotKV Ltd's own measurements under the conditions stated with them. They apply to those versions, settings and workloads. Every figure on this ElastiCache alternative page links to its source below. HotKV Ltd is not affiliated with the makers of Amazon ElastiCache. Nothing on this page is endorsed by them.

Amazon ElastiCache and AWS are trademarks of Amazon.com, Inc. or its affiliates. HotKV Ltd is not affiliated with or endorsed by Amazon. HotKV™ is a trademark of HotKV Ltd.