Skip to content
HotKVDocs

Ask the HotKV docs

Answers come only from these docs and can be wrong; check the linked pages before you rely on them.

Introduction

Last updated

HotKV is a proprietary, multi-threaded, in-memory data store that speaks the Redis wire protocol (RESP2 and RESP3) and adds a set of AI-native commands on top: a prompt cache, a semantic cache, agent memory, a RAG pipeline, and LLM cost and budget tracking. It is written from scratch in C++20.

Because HotKV speaks RESP2/RESP3, your existing Redis or Valkey clients, redis-cli, and tooling connect to it without code changes beyond the hostname. HotKV also ships 12 official client SDKs with typed wrappers for its own exclusive and AI commands; see Connecting and SDKs.

What HotKV includes

Section titled “What HotKV includes”
  • Classic data types: strings, lists, sets, hashes, sorted sets, streams, geospatial, bitmaps, and HyperLogLog, plus Lua scripting and pub/sub.
  • HotKV-exclusive commands available on every plan: nanosecond-precision TTLs (NEXPIRE/NTTL), key tagging (TAG.*), native vector similarity search (VSIM.*, HNSW-indexed), hot key tracking, and a GCRA rate limiter.
  • AI and LLM features on HotKV Cloud’s Performance plan and above, or under an On-Premise license with the matching feature enabled: an exact prompt cache (PCACHE), a semantic cache (SCACHE), LLM usage stats and budgets, agent memory, a RAG pipeline, embedding de-duplication, and a set of smaller keyed caches for tool calls, guardrails, and reranking. See the AI features guide.
  • Governance features on HotKV Cloud’s Scale plan, or under an On-Premise license that includes them: replication, encryption at rest, a tamper-evident audit log, and multi-tenancy. See Security.
  • Roles and single sign-on under an On-Premise license that includes them: log in through an LDAP directory or an OpenID Connect provider, and give logins roles that say which commands and keys they can use. See Roles and single sign-on.

The full list, with exact syntax and which plan or license feature each command needs, is in the command reference.

HotKV Cloud vs. HotKV On-Premise

Section titled “HotKV Cloud vs. HotKV On-Premise”

HotKV is sold two ways. Both run the same server binary and the same command set; they differ in who operates it and how it is licensed.

 HotKV CloudHotKV On-Premise
Who runs itHotKV Ltd, on Google CloudYou, on your own servers or cloud account
Get startedSign up in the portalContact sales@hotkv.com for a license
PlansStarter, Performance, and ScaleLicensed per the agreed feature set
BillingMonthly or yearly in USD, priced live per region at checkoutCommercial agreement with HotKV Ltd
OperationsProvisioning, upgrades, and monitoring handled for you, plus daily backups on Performance and ScaleYou control data residency, network access, and upgrade timing

Start with whichever fits how you want to operate it:

Redis protocol compatibility

Section titled “Redis protocol compatibility”

HotKV implements RESP2 and RESP3, including HELLO protocol negotiation, so Redis and Valkey client libraries, redis-cli, redis-cli --cluster, and GUI tools connect to it unmodified. The command reference notes which commands are part of that standard surface and which are HotKV-exclusive or enterprise/AI additions; HotKV’s own SDKs additionally expose typed helpers for every exclusive and AI command family. See Connecting and SDKs for connection strings and examples in each supported language, and the command reference for the full command list.

Next steps

Section titled “Next steps”