HotKV Cloud vs Upstash
An Upstash alternative makes sense once traffic is steady or heavy. Upstash Redis is serverless and billed per command, which suits small and spiky workloads. HotKV Cloud is the other shape. A dedicated machine per instance, billed per instance. Its multi-threaded engine speaks the same Redis protocol and has the AI command families built in from the Performance plan up.
Monthly cost as traffic grows
This Upstash alternative, run as a single instance on one 160-vCPU machine. 36.6M GET* and 50.5M SET operations per second, HotKV built from source for that CPU.
Drop-in
HotKV implements the Redis wire protocol. Moving from Upstash is usually a change of host and credentials. Check the command reference for anything outside the core set.
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.
Redis and Valkey client libraries, redis-cli, redis-cli --cluster and GUI tools connect to HotKV without code changes for the core commands.
300 core commands, Lua scripting and function libraries, plus HotKV's own command families when you want them.
$ 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) 1The case for an Upstash alternative
Documented properties of Upstash that send teams looking for an Upstash alternative, checked on October 21, 2026.
Upstash's pay-as-you-go plan is priced per 100,000 commands, with fixed-price plans for steady use. A cache that serves many small reads pays for each one. An Upstash alternative billed per instance, like HotKV Cloud, costs the same at any command rate.
Upstash states a maximum request size per plan, 10 MB on the pay-as-you-go plan, and a monthly bandwidth allowance beyond which bandwidth is charged. HotKV Cloud bundles outbound traffic and pauses it when the bundle is used up.
Upstash's documentation says databases share hardware resources such as CPU and network, with dedicated or more isolated hardware on enterprise plans. Every instance of this Upstash alternative is an isolated machine with dedicated vCores, RAM and disk.
Vector search at Upstash is a separate product. On HotKV, vector search is a core command on every plan. Prompt and semantic caches, agent memory, RAG and LLM cost tracking are commands of the same server from the Performance plan up.
Measured, not claimed
Upstash is a Redis-compatible serverless service on shared infrastructure, and was not measured by HotKV Ltd. The HotKV figures below, the ones behind this Upstash alternative, come from a self-hosted single instance on a 160-vCPU machine, published with the method and raw data.
* Network-limited: the instance's network set this result, so the server's own limit is higher.
Median of 3 runs on Azure D160alds_v7 (AMD EPYC 9V45 (Turin), 160 vCPUs). 256-byte values, pipeline depth 30, 5,000,000 prefilled keys. Three dedicated load-generator machines. HotKV Ltd built HotKV from source for this CPU. Full method and results · Harness and raw data
Side by side
In fairness
This Upstash alternative page is only useful when it says this part too.
Moving over
What switching to an Upstash alternative involves in practice.
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.
Keep the client library you already use. Change the host, port and credentials from Upstash to the HotKV instance. TLS and password authentication are on from the start, with ACL users available. An Upstash alternative that speaks the same protocol needs no client changes for the core commands.
Use the tools you already know. DUMP and RESTORE, MIGRATE, or a replay of your writes all work, because HotKV implements these commands.
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 Upstash alternative should add.
Questions
Clients that speak the Redis protocol do, for the core commands. Code that uses Upstash's REST API or REST SDKs has to switch to a Redis client library, which every major language has.
When the command count is high and steady. Upstash's pay-as-you-go price is per 100,000 commands, so a cache serving millions of reads a day pays for each one. A HotKV Cloud instance has one price per month whatever the command rate, with traffic bundled. Compare both against your own numbers.
No. Upstash is a serverless service on shared infrastructure, so there is no like-for-like single-instance measurement. HotKV's own figures are published with the method and raw data.
No. An instance of this Upstash alternative is a machine that is always on, which is what gives it dedicated resources and a fixed price. If your workload is idle most of the time, a serverless service may suit it better.
HotKV Cloud is opening in waves. Every instance of this Upstash alternative is a dedicated machine with the multi-threaded engine. The AI command families come with the Performance and Scale plans.