Redis for cache, sessions and queues — on your box.

Depfloy installs Redis on a server you own and configures it for the job you are using it for. Cache servers are a distinct server role, so a Redis box is set up as one rather than being an afterthought on the app server.

Start free trial Read the docs

Redis

Version provisioned: 8.4
Runs on: A server you own
Scheduled backups: Supported

Cache gets its own server role

Cache is one of the five server roles. Provisioning a cache server sets up the service, the firewall and the private-network access in one pass.

The memory limit and eviction policy are settings

maxmemory and the eviction policy are configured from the dashboard, so a cache that should evict does, instead of filling the disk with swap.

The dataset can be backed up

Redis is often treated as disposable, but queues and sessions rarely are. A schedule dumps the dataset to your chosen destination like any other source.

Most projects reach for Redis for three things at once — cache, sessions and the queue backend. Depfloy treats it as infrastructure with its own server role rather than a package installed next to the app.

FAQ

Redis questions

Should Redis run on the app server or its own? +

Its own, once it matters. A separate cache server keeps a memory spike in the cache from taking the application down with it.

Is it reachable from the internet? +

Not unless you open it. The usual setup is the private network plus a firewall rule limited to your app subnet.

Redis or Valkey? +

Both are available and both are managed the same way. Valkey is the community fork; if you have no licensing preference, either works.

Six other services, provisioned the same way.

Each one is installed, firewalled and monitored from the same console.

PostgreSQL MySQL Valkey ClickHouse Meilisearch

Run Redis on your own server.

7 days free, no credit card. Your provider bills you for the machine; we bill a flat plan.

Start free trial How releases work