Managed Valkey Cache
Quant Cloud can provision a managed Valkey cache for your application — a high-performance, in-memory key/value store for application caching, sessions, and queues. Valkey is a 1:1 Redis-compatible drop-in: it speaks the Redis protocol, works with every existing Redis client library and framework integration (phpredis, Predis, ioredis, redis-py, Drupal’s Redis module, Laravel’s Redis driver, and so on), and requires no code changes. If your application already supports Redis, it supports the managed cache.
One cache is provisioned per application and shared by all of its environments, with per-environment key isolation built in.
Enabling the Managed Cache
Section titled “Enabling the Managed Cache”For an existing application, open the application’s Environments page in the dashboard and switch on Enable managed cache. Choose a storage cap (1–50 GB) before enabling — this is the maximum amount of data the cache will hold.
For a new application, tick Provision managed cache (Valkey) during application creation.
Provisioning takes a few minutes. Once the cache shows as enabled, edit & save each environment you want connected — the cache connection is injected into the environment on that deploy.
Connecting Your Application
Section titled “Connecting Your Application”When an environment deploys with the cache enabled, Quant Cloud injects the connection details automatically. Your containers receive:
| Variable | Value |
|---|---|
REDIS_ENABLED |
true |
REDIS_HOST |
The cache endpoint hostname |
REDIS_SERVICE_PORT |
6379 |
REDIS_TLS |
1 — connections must use TLS |
REDIS_USER |
Cache username (injected as a secret) |
REDIS_PASSWORD |
Cache password (injected as a secret) |
CACHE_PREFIX |
A per-environment key prefix (see below) |
Configure your Redis client with these values. Note that:
- TLS is required. Most clients accept a
tls://scheme on the host or an explicit TLS/SSL option. - Authentication is required using
REDIS_USERandREDIS_PASSWORD(Redis 6+ ACL-style auth — pass both, not just a password). - Quant’s Drupal application templates detect
REDIS_ENABLED=trueand configure the Redis module automatically — no manual settings needed.
Environments Share One Cache
Section titled “Environments Share One Cache”All environments of the application connect to the same cache. Isolation comes from CACHE_PREFIX, which is unique per environment — prefix your keys with it so production and staging never collide. Framework integrations that support a cache/key prefix should use CACHE_PREFIX directly.
Cluster Mode Note
Section titled “Cluster Mode Note”The cache runs in cluster mode. Multi-key operations (MGET, pipelines with multiple keys, RENAME, etc.) require the keys to live in the same hash slot — wrap your common prefix in braces (a Redis hash tag, e.g. {myprefix}:item:1) if your application relies on multi-key commands. Most framework cache integrations handle single keys only and need no changes.
Storage Cap and Eviction
Section titled “Storage Cap and Eviction”The storage cap is a hard ceiling, not a pre-allocation. When the cache fills, the least-recently-used evictable entries are removed to make room — a full cache keeps working, it just holds your hottest data. Set TTLs (or an evictable policy) on cache entries so they can be reclaimed.
If your hit rate drops because the working set outgrows the cap, raise the cap from the Environments page.
Pricing
Section titled “Pricing”The managed cache is billed at a flat monthly rate per GB of storage cap, regardless of how much of the cap is in use. The cache is per-application — environments share it at no extra cost. Disabling the cache removes it and stops billing immediately.
Disabling the Managed Cache
Section titled “Disabling the Managed Cache”Switch off the toggle on the Environments page. The cache and its data are deleted, and environments fall back to their non-cache configuration (for Quant’s Drupal templates, the database cache backend) on their next deploy.