Redis holds data structures in memory — strings, hashes, lists, sets, sorted sets and streams — and answers in microseconds, which is why it sits in front of so many databases.
It is the usual choice for session storage, rate limiting, job queues and caches, and it persists to disk so a restart does not necessarily start cold.
What you get
Native install managed by systemd, with a password set
Rich data structures, not just key-value strings
Pub/sub and streams for queues and event fan-out
Optional persistence so state survives a restart
Running Redis on Autogineer Cloud
Redis is a one-click install here: choose it at checkout, set a root password, and the server is built, the software installed and configured, and its service started and its credentials set — usually in about a minute, with the whole build streamed to your browser as it runs.
Installed and configured, not just downloaded. The build finishes only once Redis is answering and its credentials authenticate — a server that could not finish is reported as failed rather than handed over looking complete.
Full root over SSH. The one-click install is a starting point, not a cage: you can reconfigure Redis, install anything beside it, or replace it entirely.
Backups you can restore from. On-demand backups of the whole server on every paid plan, which for Redis means its data as well as its configuration.
Room to grow. Resize the plan as Redis grows, or rebuild the same server with a different app when the project changes.
Who it suits
Applications that need a cache, a queue or shared session state, kept off the web server so a restart does not empty it.
Getting started with Redis
When the build finishes, your server's page in the dashboard shows its connection details, its root password and any sign-in details the installer set for Redis. The build console streams every step as it happens, so you can see exactly what was installed rather than taking it on trust.
There is no web interface — connect with redis-cli or your client library using the password on your server's page. Point your application's cache or queue at it and watch the keys appear.
Connect your application using the credentials on that page, and restrict access with the firewall so that only the addresses which need this service can reach it.
Take a backup once Redis is configured the way you want it. A backup captures the whole server, so restoring one brings back Redis and its data together — and it is the only thing that will bring them back.
Frequently asked questions
Should Redis share a server with my app?
For small workloads it can. Separating it means an app deploy cannot flush your cache and a memory spike in one does not evict the other.
How much data can it hold?
Redis is memory-bound, so its capacity is the plan's RAM minus the operating system. Choose the plan by working set size.
How long does it take to install Redis?
About a minute. Choosing Redis at checkout builds the server, installs it, and publishes it on an HTTPS address, streaming the progress to your browser as it happens.
What size server does Redis need?
At least 1 vCPU, 1 GB of memory and 10 GB of disk, which is the Starter plan or larger. These are the figures the installer is tested against rather than the smallest configuration that will boot.
Do I get root access to the server?
Yes. Every server includes full root access over SSH on its own port, so you can configure, extend or replace anything the one-click installer set up.
Reviewed . Requirements and plan sizes on this page are read from the live catalogue, so they are current whenever you load it.
Redis is developed by its own project and is not affiliated with Autogineer Cloud. Its name and logo are the property of their respective owners and appear here only to identify the software this platform installs. Read more at the official site or in its documentation.
Deploy Redis now
Pick a plan, set a root password, and Redis will be installed and running in about a minute.