Cache Server (Redis)
Use a Cache Server when you want Redis (or Valkey) to run on its own machine, separate from your application servers. Typical reasons: keep cache traffic off your App Server's network, share a cache across multiple App Servers, or scale cache capacity independently.
The Redis screen on a Cache Server is where you grab the connection URL, rotate the password, and edit the configuration.
Redis vs. Valkey
When you create the server, you can choose Redis or Valkey as the engine. Valkey is the community fork of Redis that emerged after Redis's licence change in 2024 — protocol-compatible, drop-in replacement. Pick whichever fits your policy; the management UI is the same for both.
Creating a Cache Server
- In the Console, click Add Server.
- Pick Cache Server as the server type.
- Pick Redis or Valkey as the engine.
- Pick a provider (Hetzner or Custom Setup) and continue with the standard provisioning flow.
Depfloy installs the engine, opens port 6379 in the firewall, and generates a strong password that becomes the initial AUTH key.
Connection details
The Redis screen shows:
- Host — the server's public IP
- Port —
6379(the standard Redis port) - Password — the AUTH key
- Connection URL —
redis://:<password>@<host>:6379, ready to paste into your application or a client like RedisInsight
Click the copy buttons to grab the values without revealing the password on screen. The password is masked by default; click to reveal.
Update the password
Click Update Password to set a new AUTH key:
- Generate a strong random one, or
- Enter your own
Saving the new password updates the running service and disconnects any clients that were using the old one. Update every application that connects to the cache as part of the same change so you don't leave anything pointing at the old credentials.
Configuration
You can edit the engine's configuration file directly from the Console. The editor opens the current redis.conf (or valkey.conf); make your changes and save to apply them. Depfloy reloads the service after a successful save.
Saving configuration changes restarts the cache engine. Any in-flight commands and connections are dropped — plan it for a low-traffic moment.
Restart the service
To restart the engine without other changes, use the More menu in the server header — the Restart Redis (or Restart Valkey) entry restarts the service after a confirmation dialog.
Connecting from your application
Most Redis clients accept the connection URL directly. For Laravel, set REDIS_URL=redis://:password@host:6379 in your project's Environments tab; for Node, use it with ioredis or node-redis; for Python, with redis-py. No extra configuration is required on the cache server's side beyond what Depfloy sets up.