WordPress Cluster Hosting on MassiveGRID PaaS
The WordPress Cluster Kit v2 deploys a highly available, horizontally scalable WordPress topology on MassiveGRID PaaS: a load balancer in front of several application servers, a replicated MariaDB cluster, Redis caching and shared file storage. It is the package for WordPress sites that cannot afford downtime or a traffic ceiling.
WordPress Cluster on MassiveGRID PaaS installs in one click in New York, London, Frankfurt or Singapore, costs about $118.08 a month for the Starter configuration, 2 × Load balancer (512 MiB each), 2 × Application server (1 GiB each), 2 × MariaDB cluster node (1 GiB each), a Redis cache (512 MiB) and a Shared storage (512 MiB), and starts with a 14-day free trial. See the sizing table.
Both buttons open the MassiveGRID PaaS dashboard with WordPress Cluster pre-selected. Sign up without a card, name the environment, pick a region, and the package installs in a few minutes.
WordPress Cluster Package Facts
| Attribute | Value |
|---|---|
| Package | WordPress Cluster Kit v2 |
| Type | Application (installs a complete environment) |
| Category | Websites & CMS |
| Software vendor / project | WordPress.org |
| Licence | GPLv2 or later (open source) |
| Runtime / stack | LiteSpeed or NGINX PHP application servers behind a load balancer, MariaDB primary-primary cluster (or Galera), shared storage or GlusterFS, Redis |
| Regions | New York, London, Frankfurt, Singapore |
| Billing | Pay-per-use, about $118.08/month for the Starter configuration (48 cloudlets at $0.003372 per cloudlet-hour), no licence fee |
| Free trial | 14 days, no credit card |
| Uptime SLA | 100% |
What is WordPress Cluster?
A standalone WordPress server has two hard limits: one machine can only serve so many requests, and if that machine fails the site is down. The Cluster Kit removes both. Requests arrive at a load balancer and are spread across two or more PHP application servers; the database runs as a replicated MariaDB cluster; uploads and plugin files are kept in sync across servers; and Redis holds object-cache data so repeated queries never hit the database.
Version 2 of the kit adds a guided installer that picks sensible servers for your expected traffic, lets you choose between MariaDB Galera (multi-primary) and primary-secondary replication, and switches on horizontal auto-scaling so extra application servers are added and removed on load triggers. The whole topology is described in a JPS manifest that you can inspect, export and re-use.
What the WordPress Cluster Package Deploys
Marketplace packages are not bare container images. One click provisions a complete, production-shaped environment on MassiveGRID infrastructure. How these nodes are sized and what they cost.
- Load balancer: LiteSpeed ADC or NGINX, terminating SSL and distributing requests across the application layer with health checks and session persistence.
- Application servers: Two or more LiteSpeed or NGINX PHP nodes, all serving the same WordPress code, scaled horizontally on CPU and memory triggers.
- MariaDB cluster: A primary-primary MariaDB cluster by default, or MariaDB Galera if you tick that option in the installer, so a database node can fail without losing writes or taking the site offline.
- Redis cache: An object-cache layer shared by every application server, cutting database queries and response times for logged-in users and WooCommerce carts.
- Shared storage: Uploads, themes and plugins live on a shared storage container, or on a fault-tolerant GlusterFS cluster if selected, so every application server sees the same files immediately.
What WordPress Cluster Costs to Run
Three starting configurations for the WordPress Cluster package, 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.
| Configuration | Topology | Cloudlets | Est. per month |
|---|---|---|---|
| StarterA site that needs zero-downtime deploys | 2 × Load balancer (4 cloudlets, 512 MiB each), 2 × Application server (8 cloudlets, 1 GiB each), 2 × MariaDB cluster node (8 cloudlets, 1 GiB each), Redis cache (4 cloudlets, 512 MiB), Shared storage (4 cloudlets, 512 MiB) | 48 | $118.08 |
| StandardA high-traffic site or small WooCommerce store | 2 × Load balancer (4 cloudlets, 512 MiB each), 2 × Application server (16 cloudlets, 2 GiB each), 2 × MariaDB cluster node (16 cloudlets, 2 GiB each), Redis cache (8 cloudlets, 1 GiB), Shared storage (4 cloudlets, 512 MiB) | 84 | $206.64 |
| ProductionCampaign peaks and large stores | 2 × Load balancer (4 cloudlets, 512 MiB each), 4 × Application server (16 cloudlets, 2 GiB each), 3 × MariaDB cluster node (16 cloudlets, 2 GiB each), Redis cache (16 cloudlets, 2 GiB), Shared storage (8 cloudlets, 1 GiB) | 144 | $354.24 |
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. Pick a row in the installer by setting the cloudlet limits per node, or start small and let auto-scaling grow it. Price a different topology or a working-hours schedule in the PaaS pricing calculator; the PaaS page describes the billing model.
WordPress Cluster on MassiveGRID PaaS vs WordPress.com Business and Commerce vs a VPS
The same application three ways: the marketplace package here, the vendor's own hosted offer, and a server you run yourself. WordPress.com Business and Commerce figures were read from the vendor's page on 1 November 2026; re-check them before relying on them.
| Aspect | WordPress Cluster on MassiveGRID PaaS | WordPress.com Business and Commerce | A plain VPS |
|---|---|---|---|
| Monthly cost | About $118.08 (Starter cluster) to $354.24 (Production cluster), before discounts; no licence fee | Business US$25 and Commerce US$45 per month billed yearly with 50 GB; Enterprise unpriced | Two or more servers plus a load balancer and a database server; plus the engineering to cluster them |
| What you manage | The application inside the containers (updates, configuration); the platform runs the infrastructure, scaling and the 100% uptime SLA | Nothing; WordPress.com runs it | Everything: OS, runtime, database, TLS, backups, upgrades |
| Limits and metering | No tiers; disk and traffic per gigabyte | Storage per plan; plugins allowed on Business and Commerce | 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 | WordPress.com's infrastructure | 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 | WordPress.com's hosting | 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 on WordPress.com | Your own cron jobs and off-server copies |
| Availability | 100% uptime SLA, nodes on separate hosts, failed containers restarted or migrated | WordPress.com's availability commitment | 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 | Standard WordPress export | None; you own the server |
Where WordPress.com Business and Commerce is the better choice: WordPress.com Business is the right answer for a content site that wants managed WordPress with plugins and no infrastructure decisions; the cluster is for stores and publishers who need the topology and the control.
Why Teams Choose WordPress Cluster
No single point of failure
Every layer runs on at least two nodes. Combined with MassiveGRID's redundant infrastructure and 100% uptime SLA, the site stays up through hardware and software faults.
Horizontal auto-scaling
Application servers are added when load rises and removed when it falls, so you pay for cluster capacity only while you need it.
Optimised for WooCommerce
Redis-backed sessions, replicated MariaDB and sticky load balancing keep carts and checkouts consistent across servers, which is where naive WordPress clusters break.
Guided installer
The kit asks about expected traffic and picks server types, database mode and scaling limits for you. Every choice can be changed later from the dashboard.
How to Install WordPress Cluster on MassiveGRID PaaS
Installing the package takes 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 or Install to my account. The MassiveGRID PaaS dashboard opens with the WordPress Cluster package pre-selected, so nothing has to be copied or pasted.
Sign up or sign in
New to the platform? Sign up for the free 14-day trial, which needs no credit card. Existing customers sign in with their usual dashboard credentials.
Choose region and deploy
Name the environment, pick New York, London, Frankfurt or Singapore, and confirm. The platform builds every WordPress Cluster node, wires them together and hands you the live URL and credentials.
Who Runs WordPress Cluster on PaaS
High-traffic publishers
News, media and content sites where a front-page story can multiply traffic tenfold within minutes.
WooCommerce stores
Shops that lose revenue every minute they are down and need consistent sessions across servers during sales.
Enterprise and government sites
Organisations with uptime requirements written into contracts, running in a region of their choice with data replicated inside it.
Why Run WordPress Cluster on MassiveGRID PaaS
Deploys and node failures do not take the site down. Two application nodes behind a load balancer, a MariaDB cluster and shared storage mean a node can be redeployed or lost while visitors keep browsing, which the zero-downtime post shows in practice.
Campaign traffic is a trigger, not a migration. A horizontal trigger adds application nodes for the hours of a sale and removes them afterwards; the Black Friday post prices a peak against a VPS.
The database is a cluster with an entry point, so a MariaDB node failure is a retried query, and the Database Backup/Restore add-on dumps it consistently.
It is still WordPress with root access: any plugin, any theme, the same WP-CLI, on nodes you can reach over SSH.
Related on massivegrid.com: WordPress in PaaS · Managed WooCommerce Hosting.
WordPress Cluster Questions
WordPress Cluster Guides from the MassiveGRID Blog
Scenario-driven guides on running WordPress Cluster on MassiveGRID PaaS, written for the developers, operators and buyers who deploy it. Browse the blog.
More from the Marketplace
Packages that are often deployed alongside WordPress Cluster, or that solve the same problem a different way. Browse all 83 packages.
Deploy WordPress Cluster Today
Start the free 14-day trial and have WordPress Cluster running in minutes. No credit card required.