Redis VPS
An in-memory store for caches, queues and sessions, on localhost. The recipe installs Redis or Valkey depending on what your distribution packages; both speak the same protocol on port 6379.
Who it suits
Apps on the same server that need a cache, job queue or session store. Valkey is a BSD-licensed fork of Redis 7.2, and most clients work with either; check before relying on features from newer Redis releases or on Redis's own licence terms.
Which plan
Everything it stores lives in memory, so size the plan for your data set plus room for the rest of the server. Budget suits a modest cache; queues and large sessions want more.
What we install
An in-memory key-value store for caches, queues and sessions, bound to localhost and started at boot. On Ubuntu and Debian you get Redis when the distribution packages it, Valkey otherwise; on AlmaLinux, Rocky Linux and Fedora it's Valkey when the repositories carry it, Redis otherwise.
- redis-server
- valkey
From order to ready
- Server ready. We email you when the server is running, and you can log in with SSH. The installer starts on that same first boot.
- Installer running. It logs to
/var/log/vps9-setup.log;tail -fit to watch. - Application ready. This can be minutes after SSH works. The installer writes its exit code to
/var/lib/vps9-setup.exit; a value of 0 means installation succeeded. It's ready whenredis-cli pingorvalkey-cli pinganswers PONG. Whichever of the two commands exists tells you which one you got.
What you still do
- Check it with
redis-cli ping(orvalkey-cli ping). - Point your app at 127.0.0.1:6379.
Exposure and security
Nothing is open: it binds to localhost, as the distribution's package does by default. It has no password, so keep it that way: programs on the server can reach it, nothing outside can.
Backups and upgrades
Persistence follows the package's own config file (check the save lines in redis.conf or valkey.conf), so treat it as a cache unless you've set up persistence and back up its dump file. Updates arrive with the system's packages. We run the hardware, the network and the first-boot install; after that, Redis is yours to run, and we don't manage or update it for you. Off-site backups of the whole disk are an optional paid add-on; they copy the disk as it is at one moment, so keep the app's own backups as well.