Apps / Redis
Managed Redis hosting.
One server, no app limits.
In-memory cache and queue. The cheapest speed upgrade most stacks never install. Pairs with everything.
What it is
Redis is the in-memory data store that makes everything else faster: cache, sessions, queues, and pub/sub with sub-millisecond answers. It is the most-paired app in this catalog for a reason.
Minimum RAM
1 GB
Fits on SC-1GB; SC-2GB is the comfortable pick with room to stack.
What we install
The playbook deploys current Redis bound to localhost with a password set, memory capped to a plan-appropriate limit with an eviction policy that suits caching, persistence configured, and the kernel settings Redis warns about actually fixed.
What managed covers
Updates, daily snapshots plus dual offsite backups, monitoring on memory and hit rates, and the managed firewall keeping 6379 off the public internet, where no Redis should ever be.
The app is $0. The managed server is the only bill, and everything above is part of it.
What does managed Redis hosting include?
A correctly capped, password-protected, localhost-bound Redis with the sysctl homework done, monitored and backed up, for $0 on top of your server. The most cost-effective performance upgrade in the catalog.
What difference does Redis actually make?
For CMS and store workloads, object caching through Redis turns repeated database queries into memory lookups: admin dashboards get snappy, checkouts stop recomputing, and the database breathes. For custom backends it is sessions, queues, and rate limiting without another service bill.
Which catalog apps use it?
WordPress and WooCommerce through object caching, Moodle for its application caches, Drupal for cache bins, PrestaShop, Nextcloud for file locking, and n8n for queue mode. The playbooks wire the connection when you stack them together.
Why must Redis never face the internet?
Because an open Redis is a compromised server within hours; it is one of the most scanned-for services there is. Ours binds to localhost with a password, and the managed firewall would block 6379 even if it did not. Security here is defaults, not homework.
Stack it
Redis runs well with.
Same server, no extra bill. These are the companions our team installs next to Redis most often.
WordPress
+1 GBThe CMS behind 40% of the web, deployed hardened from day one: LiteSpeed cache, SSL, and working outbound mail included.
PostgreSQL
+1 GBThe engineers’ database. Installed, tuned for your RAM, and backed up twice offsite.
Frequently asked questions
How much RAM does Redis need?
It needs what you give it: the playbook caps it (512 MB to 1 GB is typical for cache duty) so it accelerates the server instead of competing with it.
Does Redis persist data?
Yes, snapshots to disk are configured, appropriate for cache and session duty. For Redis as a primary datastore we configure AOF persistence on request.
Redis alongside every app?
Almost: if you are stacking two or more PHP apps, adding Redis is nearly always worth its 1 GB line in the meter. It is the catalog's best pound-for-pound addition.
Sizing an app stack? The VPS sizing calculator recommends a plan from your apps and traffic, with the math shown.
Shared CPU servers
The right home for Redis and most stacks: 3.0+ GHz vCPU, from $10/mo.
See Shared CPU →Dedicated CPU servers
For CPU-hungry stacks and busy databases: cores that are physically yours.
See Dedicated CPU →All plans and pricing
Every plan, both families, one honest price with everything included.
See pricing →Your server runs. You sleep.
Fully managed hosting from people who have been doing this since 2001.