Managed Redis Hosting on MassiveGRID PaaS
The six-node Redis Cluster that Redis itself describes, three primaries with a replica each over 16,384 hash slots, installed in one click with automatic failover and optional TLS. Nodes are sized to the dataset and billed by the cloudlet-hour, with no dataset tiers.
Redis Cluster on MassiveGRID PaaS installs in one click in New York, London, Frankfurt or Singapore, costs about $29.52 a month for the Starter configuration, 6 × Redis node (256 MiB each), and starts with a 14-day free trial. See the sizing table.
The install button opens the MassiveGRID PaaS dashboard with Redis Cluster pre-selected. Sign up without a card, name the environment, pick a region, and the package installs in a few minutes.
Why host Redis on MassiveGRID PaaS
Redis is memory-bound, which makes the cloudlet the right unit to buy it in: a session store needs 256 MiB per node and a feature store needs gigabytes, and the Redis Cluster package on MassiveGRID PaaS, built on Virtuozzo Application Platform (formerly Jelastic), prices each node by its allocation rather than by a dataset tier. The smallest honest cluster, six nodes, costs under $30 a month.
Redis's scaling guide fixes the cluster's shape: at least three primaries, a replica each, 16,384 slots, a cluster bus port per node, availability while a majority of primaries is up. The package installs exactly that, as the requirements guide explains, and the operations post covers failure, resharding and scaling by pairs.
The common use is a session store or cache for an application scaled across several nodes, which the session store post configures for PHP and Node.js behind a load balancer.
What the Redis Cluster package deploys
Six Redis nodes, three primaries and three replicas, with the cluster configuration, slot assignment and failover set up, and the Redis TLS add-on available for encrypted client connections and cluster bus. Persistence (RDB, AOF) is configured per node for data that must survive a restart; maxmemory and the eviction policy are yours to set.
Growing from three shards to four moves slots live, a node failure is a replica promotion and a container restart, and the whole cluster lives on the internal network beside the application, with no traffic charge between them.
Who hosts Redis this way
Applications scaled across several nodes that need a shared session store or cache with no single point of failure.
Queues and rate limiters that need Redis to survive a node loss without losing the queue.
Teams already on the platform who want Redis beside the application rather than across the internet to a managed service.
A small cache for a single application is cheaper on a managed Redis's entry tier; the comparison table below says where.
What Redis Cluster costs to run here
Three starting configurations, sized in cloudlets (1 cloudlet = 128 MiB RAM + 400 MHz CPU) and priced at the published rate of $0.003372 per cloudlet-hour, or $2.46 per cloudlet-month. A Redis cluster is six nodes at minimum (three primaries with a replica each); Redis is memory-bound, so size the nodes to the dataset.
| Configuration | Topology | Cloudlets | Est. per month |
|---|---|---|---|
| StarterSessions and small caches | 6 × Redis node (2 cloudlets, 256 MiB each) | 12 | $29.52 |
| StandardApplication caches up to a few hundred MB | 6 × Redis node (4 cloudlets, 512 MiB each) | 24 | $59.04 |
| ProductionLarge datasets | 6 × Redis node (8 cloudlets, 1 GiB each) | 48 | $118.08 |
Estimates assume the environment averages the listed cloudlets around the clock; billing is hourly, vertical auto-scaling lowers the figure when the application is idle, and volume discounts apply as usage grows. Disk and external traffic are billed per gigabyte on top. No licence fee applies to the package. Price a different topology or a working-hours schedule in the PaaS pricing calculator.
Redis Cluster on MassiveGRID PaaS vs Redis Cloud vs a VPS
Redis Cloud figures were read from the vendor's page on 1 November 2026; re-check them before relying on them.
| Aspect | Redis Cluster on MassiveGRID PaaS | Redis Cloud | A plain VPS |
|---|---|---|---|
| Monthly cost | About $29.52 (Starter, six 256 MiB nodes) to $118.08 (Production, six 1 GiB nodes), before discounts | Free 30 MB; Essentials from $5 a month (250 MB to 100 GB, shared deployment); Pro from $0.014 an hour with a $200 monthly minimum (dedicated, multi-region) | Six small servers or six processes on fewer; plus the clustering work |
| What you manage | The application inside the containers (updates, configuration); the platform runs the infrastructure, scaling and the 100% uptime SLA | Nothing; Redis runs it | Everything: OS, runtime, database, TLS, backups, upgrades |
| Limits and metering | No dataset tiers; capacity is the nodes' cloudlets | Dataset size per plan; Essentials is a shared single database | No metering; limited by the server's size |
| Scaling | Vertical by the cloudlet, automatic and without restart; horizontal on a trigger behind the platform's load balancer | Change the plan size; Pro scales on demand | Resize the server, usually with a reboot; no horizontal scaling without your own load balancer |
| Data location | New York, London, Frankfurt or Singapore, chosen at install; data stays there | Redis Cloud's regions on the hyperscalers | Wherever the VPS is; one server, one location |
| Backups | Database Backup/Restore and Backup Storage add-ons on a schedule, environment clone for rehearsals | Included per plan | Your own cron jobs and off-server copies |
| Availability | 100% uptime SLA, nodes on separate hosts, failed containers restarted or migrated | Up to 99.99% (Essentials) and 99.999% (Pro) per Redis's page | Single server; the provider's hardware SLA only |
| Lock-in | Standard JPS manifest and root access; export the manifest or move the containers at any time | RDB export is standard | None; you own the server |
Where Redis Cloud is the better choice: Redis Cloud is the right answer for a small cache on the Essentials tier where $5 a month and no operations beat any self-managed option, and for multi-region active-active on Pro.
How to deploy Redis Cluster here
Three steps and a few minutes of waiting. No servers to provision, no configuration files to edit.
Open the installer
Click Install with free trial. The MassiveGRID PaaS dashboard opens with the Redis Cluster package pre-selected.
Sign up or sign in
The free 14-day trial needs no credit card. Existing customers sign in with their dashboard credentials.
Choose region and deploy
Name the environment, pick New York, London, Frankfurt or Singapore, and confirm. The platform builds every node and hands you the live URL and credentials.
Redis Cluster guides from the MassiveGRID blog
Managed Redis questions
Deploy Redis Cluster today
Start the free 14-day trial and have Redis Cluster running in minutes. No credit card required.
Install the Redis cluster with free trial