Plexivo Cache
A managed, Redis-compatible cache over TLS for sessions, queues and hot data, in Mumbai.
Plexivo Cache is a managed, Redis-compatible cache for sessions, queues, rate limits and fast reads. Any Redis client connects to it over TLS. It runs in Mumbai, next to your apps and databases.
What you get#
- A Redis-compatible server with a generated password, reached over TLS only.
- Its own certificate authority, so your client can verify the cache it connects to.
- A data volume, 10 GB by default, for persistence.
- Updates applied in your weekly maintenance window.
Sizes and client limits#
| Memory | vCPU | Client connections, by default |
|---|---|---|
| 256 MB | 0.125 | 1,000 |
| 512 MB | 0.125 | 2,000 |
| 1 GB | 0.25 | 5,000 |
| 2 GB | 0.25 | 10,000 |
| 4 GB | 0.5 | 15,000 |
| 8 GB | 1 | 25,000 |
| 16 GB | 1 | 40,000 |
| 32 GB | 2 | 50,000 |
| 64 GB | 2 | 65,000 |
Your data can use 90% of the size; the rest is kept for the cache’s own work, so your chosen eviction policy acts before memory runs out. Prices are on Pricing.
Persistence and eviction#
You choose both when you create the cache:
| Persistence | What happens |
|---|---|
| AOF (the default) | Every write is appended to a log on the data volume, so data survives a restart. |
| Snapshot | The whole dataset is saved to the data volume: after an hour if anything changed, after 5 minutes if 100 keys changed, and after a minute if 10,000 changed. |
| None | Memory only. A restart starts empty: right for a pure cache. |
When memory is full decides what happens to new writes once the cache is full:
allkeys-lru(the default): remove the least recently used keys.allkeys-lfu: remove the least frequently used keys.volatile-lru: remove the least recently used keys that have an expiry.noeviction: keep every key and refuse new writes. Right for queues and data you cannot lose.
Security#
- TLS on every connection. Clients authenticate with the password; they need no certificate of their own.
- The cache’s certificate is issued by its own certificate authority and renewed before it expires.
- Commands that change the server itself are not available, such as
CONFIG,REPLICAOF,DEBUG,MODULE,SHUTDOWN,ACLchanges,CLIENT KILL,MONITOR,SAVEandMIGRATE. Persistence, memory and eviction are set by Plexivo from your choices. - Make it private, or limit it to trusted networks, on the Network tab.
Updates and resizing#
Updates arrive in your weekly maintenance window, after an email; the cache restarts once and is unavailable while it does. You can resize it from Settings: it restarts on its new size, and with persistence on, its data is kept. See Maintenance and patches.
allkeys-lru and AOF; keep job queues on noeviction, so a full cache refuses writes instead of dropping jobs.Next steps#
Updated 27 October 2026