Magento Cluster Hosting on MassiveGRID PaaS
The Auto-Scalable Magento Cluster v2 deploys a highly available Magento Open Source topology on MassiveGRID PaaS: a load balancer in front of auto-scaling PHP application servers, a replicated MariaDB cluster, Redis for cache and sessions, a search engine and shared media storage. It is built for stores where downtime and slow checkouts cost money.
Magento Cluster on MassiveGRID PaaS installs in one click in New York, London, Frankfurt or Singapore, costs about $246.00 a month for the Starter configuration, 2 × Load balancer (512 MiB each), 2 × PHP application server (2 GiB each), 2 × MariaDB cluster node (2 GiB each), a Redis (1 GiB), a Search engine (2 GiB) 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 Magento Cluster pre-selected. Sign up without a card, name the environment, pick a region, and the package installs in a few minutes.
Magento Cluster Package Facts
| Attribute | Value |
|---|---|
| Package | Auto-Scalable Magento Cluster v2 |
| Type | Application (installs a complete environment) |
| Category | E-commerce |
| Software vendor / project | Adobe (Magento Open Source) |
| Licence | OSL 3.0 (Magento Open Source) |
| Runtime / stack | NGINX/LiteSpeed load balancer, PHP application servers, MariaDB Galera or primary-secondary cluster, Redis, Elasticsearch/OpenSearch, shared storage |
| Regions | New York, London, Frankfurt, Singapore |
| Billing | Pay-per-use, about $246.00/month for the Starter configuration (100 cloudlets at $0.003372 per cloudlet-hour), no licence fee |
| Free trial | 14 days, no credit card |
| Uptime SLA | 100% |
What is Magento Cluster?
A single Magento server is a single point of failure and a hard performance ceiling. The cluster package removes both. Requests hit a load balancer and are spread across two or more PHP nodes; the database runs as a replicated MariaDB cluster; Redis holds the full-page cache and customer sessions so every node sees the same cart; product images and media live on shared storage; and the search engine runs as its own node. Horizontal auto-scaling adds PHP nodes during campaigns and removes them afterwards.
Version 2 of the package refines the installer with choices for web server type, database replication mode and scaling limits, and wires in the caches and session handling that Magento needs to behave correctly across multiple servers. Everything is described in a JPS manifest you can inspect, so nothing about the architecture is hidden.
What the Magento 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: NGINX or LiteSpeed ADC terminating SSL and distributing requests across the PHP layer with health checks.
- PHP application servers: Two or more NGINX or LiteSpeed PHP nodes running the same Magento code, added and removed by horizontal auto-scaling.
- MariaDB cluster: Galera multi-primary or primary-secondary replication, so a database node can fail without losing orders.
- Redis: Full-page and block cache plus a shared session store, which keeps carts and logins consistent across nodes.
- Search engine and shared storage: Elasticsearch or OpenSearch for catalogue search, and a shared volume for media and static files.
What Magento Cluster Costs to Run
Three starting configurations for the Magento 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 store that needs zero-downtime deploys | 2 × Load balancer (4 cloudlets, 512 MiB each), 2 × PHP application server (16 cloudlets, 2 GiB each), 2 × MariaDB cluster node (16 cloudlets, 2 GiB each), Redis (8 cloudlets, 1 GiB), Search engine (16 cloudlets, 2 GiB), Shared storage (4 cloudlets, 512 MiB) | 100 | $246.00 |
| StandardA busy store | 2 × Load balancer (4 cloudlets, 512 MiB each), 2 × PHP application server (24 cloudlets, 3 GiB each), 2 × MariaDB cluster node (24 cloudlets, 3 GiB each), Redis (16 cloudlets, 2 GiB), Search engine (24 cloudlets, 3 GiB), Shared storage (8 cloudlets, 1 GiB) | 152 | $373.92 |
| ProductionCampaign peaks and large catalogues | 2 × Load balancer (4 cloudlets, 512 MiB each), 4 × PHP application server (32 cloudlets, 4 GiB each), 3 × MariaDB cluster node (32 cloudlets, 4 GiB each), Redis (16 cloudlets, 2 GiB), Search engine (32 cloudlets, 4 GiB), Shared storage (8 cloudlets, 1 GiB) | 288 | $708.48 |
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.
Magento Cluster on MassiveGRID PaaS vs Adobe Commerce on Cloud vs a VPS
The same application three ways: the marketplace package here, the vendor's own hosted offer, and a server you run yourself. Adobe Commerce on Cloud figures were read from the vendor's page on 1 November 2026; re-check them before relying on them.
| Aspect | Magento Cluster on MassiveGRID PaaS | Adobe Commerce on Cloud | A plain VPS |
|---|---|---|---|
| Monthly cost | About $246.00 (Starter cluster) to $708.48 (Production cluster), before discounts; Magento Open Source has no licence fee | Not published; quoted by sales. Adobe Commerce is licensed by revenue tier and hosted on Adobe's cloud | Several servers plus a load balancer, a database cluster and a search engine; 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 | Adobe runs the platform; you run the store code | Everything: OS, runtime, database, TLS, backups, upgrades |
| Limits and metering | No tiers; capacity is the nodes' cloudlets | Licence tiers by gross merchandise value | 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 | Adobe's infrastructure, by contract | 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 | Adobe's cloud regions | Wherever the VPS is; one server, one location |
| Backups | Database Backup/Restore and Backup Storage add-ons on a schedule, environment clone for rehearsals | Adobe's responsibility | Your own cron jobs and off-server copies |
| Availability | 100% uptime SLA, nodes on separate hosts, failed containers restarted or migrated | Per contract | 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 | Commerce-only features do not exist in Open Source | None; you own the server |
Where Adobe Commerce on Cloud is the better choice: Adobe Commerce Cloud is the right answer when the merchant wants Adobe accountable for the platform and needs Commerce-only features; the cluster is the same high-availability shape on Open Source, billed by the hour.
Why Teams Choose Magento Cluster
High availability at every layer
Redundant web, database and cache tiers on MassiveGRID's redundant infrastructure, backed by the 100% uptime SLA.
Elastic capacity for campaigns
Horizontal auto-scaling adds PHP nodes on CPU or memory triggers, so a flash sale is served without over-provisioning all year.
Consistent sessions and cache
Redis-backed sessions and cache mean customers never lose a cart when the balancer moves them to another node.
Same Magento, bigger footprint
Standard Magento Open Source, so every extension, theme and integration works unchanged.
How to Install Magento 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 Magento 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 Magento Cluster node, wires them together and hands you the live URL and credentials.
Who Runs Magento Cluster on PaaS
Established online retailers
Stores with steady revenue where an hour of downtime is measurable in lost orders.
Flash-sale and campaign-driven brands
Merchants whose traffic multiplies during drops, promotions and holiday peaks.
B2B commerce platforms
Distributors serving dealer portals with large catalogues and complex pricing that must stay responsive.
Why Run Magento Cluster on MassiveGRID PaaS
Built for the day the store cannot go down. PHP nodes behind a load balancer, a MariaDB cluster, Redis, a search engine and shared storage: a deploy or a node loss is invisible to shoppers, which the flash sale post shows under load.
Peaks are a trigger. Application nodes are added for the hours of a campaign and removed afterwards, billed for those hours; the Production row runs four.
Catalogue and search on their own nodes, so reindexing does not slow checkout, and the search engine's JVM is sized on its own.
Adobe Commerce Cloud without the licence tier, as the buyer's comparison sets out, for merchants who do not need the Commerce-only features.
Related on massivegrid.com: Magento in PaaS · eCommerce Managed Hosting.
Magento Cluster Questions
Magento Cluster Guides from the MassiveGRID Blog
Scenario-driven guides on running Magento 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 Magento Cluster, or that solve the same problem a different way. Browse all 83 packages.
Deploy Magento Cluster Today
Start the free 14-day trial and have Magento Cluster running in minutes. No credit card required.