A cache you pay for per command.
Connect with any cache client or a plain HTTP request. For sessions, counters, small queues and cached responses. Billed per command, and it sleeps when idle.
What you get
Cache clients
Any cache client, in any language, on port 6379, with a token as the password.
A REST API
Send a command as a JSON array, one or many in a pipeline. For places where a lasting connection is not possible.
env.CACHE in functions
Bind a function or app to the cache, with no token in your code.
Sleeps when idle
The cache stops when there is nothing to do and keeps its data. The next command starts it again.
No acknowledged write is lost
A write is acknowledged once it is stored durably. If a server fails, the cache opens on another one with all its data.
Data larger than memory
Memory holds the hot data; it is not a limit on your data. Cold keys are read from storage, and your plan sets the stored-size limit.
Checkpoints
Checkpoints are kept 7 to 30 days by plan. Restore one over the same cache, or into a new cache.
Read-only tokens
Give a service that only reads a token that cannot write. Each token can be revoked on its own.
Memory and eviction
32 to 256 MB of memory. When full, old keys are evicted or writes fail; you choose.
Observability
Commands, hit rate, memory, key count and evictions.
Commands from the CLI and MCP
Run commands with cloudhost cache run or from your AI assistant, with no client to install.
Three ways into one cache
A cache client, an HTTP request, or a direct binding from a function.
cloudhost cache create sessions --memory 64
# host sessions.cache.trustpage.ir:6379
# token shown oncePer command
You pay for commands, bandwidth and the data you keep, not for hours switched on. An idle cache costs its storage only. Hobby includes a free amount each month.
Questions
Data commands do. Commands that change or stop the server, such as CONFIG, SHUTDOWN and DEBUG, are blocked for safety.
Yes. The cache stops when idle, its data is kept, and the next command starts it with the same data.
Our REST API takes a JSON array body and a Bearer token, the shape common REST cache clients use. Change the URL and the token.
256 MB for now. If you need more, talk to us.
Its storage only. An idle cache is stopped and costs no commands or memory; the data it keeps is billed per GB-month.
Restore a checkpoint: over the same cache (writes after it are replaced), or into a new cache to take back only what you need.
No. Nothing stays on for you. The cache starts with a command, stops when idle and is billed per command.
Create a cache
One command, one address, one token.
Sign-up is by invite for now. If you have a code, create your account.
Sign up withEmail codeSMS code