Managed MariaDB Hosting on MassiveGRID PaaS
A MariaDB, MySQL or Percona cluster installed in one click in the topology you choose, Galera, primary-secondary or primary-primary, with a ProxySQL pair as the entry point, automatic failover, scheduled dumps and a recovery tool for the bad days. Billed by the cloudlet-hour with no plan tiers.
MySQL Cluster on MassiveGRID PaaS installs in one click in New York, London, Frankfurt or Singapore, costs about $49.20 a month for the Starter configuration, 2 × Database node (1 GiB each) and 2 × ProxySQL (256 MiB each), and starts with a 14-day free trial. See the sizing table.
The install button opens the MassiveGRID PaaS dashboard with MySQL Cluster pre-selected. Sign up without a card, name the environment, pick a region, and the package installs in a few minutes.
Why host MariaDB or MySQL on MassiveGRID PaaS
The topology is the decision a managed database rarely lets you make. The MySQL/MariaDB/Percona cluster package on MassiveGRID PaaS, built on Virtuozzo Application Platform (formerly Jelastic), builds primary-secondary, primary-primary or Galera from one installer, with a ProxySQL pair in front so the application connects to one hostname and never learns which node answered. The topology post chooses between them.
Galera, the topology that keeps writing through a node loss, has rules MariaDB publishes: InnoDB only, a primary key on every table, write sets capped by default at 128K rows and 2 GB. The requirements guide checks them before you cluster, and the recovery post shows the Database Cluster Recovery add-on bringing a cluster back from a lost quorum from the dashboard.
Nodes are sized to the buffer pool and billed by the cloudlet; a node failure is a retried query behind ProxySQL, which the failover post recounts at 2 a.m.
What the cluster package deploys
Database nodes in the chosen topology, a ProxySQL pair, replication and auto-discovery, Orchestrator where the topology uses it, and administrative access; the MySQL TLS add-on encrypts client connections, the Database Backup/Restore add-on takes consistent dumps on a schedule to a Backup Storage node, and the Cluster Recovery and Corruption Diagnostic add-ons attach at no cost.
Each node is its own container with its own cloudlet limit, scaled vertically without a restart; adding a node to a Galera cluster is a dashboard action with the state transfer handled, and the application never changes its connection string.
Who hosts MariaDB this way
Applications that must keep writing through a node failure, for which Galera's synchronous multi-primary is the answer managed offerings rarely sell.
Read-heavy applications that want secondaries behind ProxySQL without a per-replica managed price.
WordPress, Magento and Moodle clusters on the platform, whose database tier is this package, as the WordPress cluster and Magento cluster packages use it.
One small database with backups included and no clustering needs is well served by a managed MySQL at about $15 a month; the comparison table below says where.
What MySQL 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.
| Configuration | Topology | Cloudlets | Est. per month |
|---|---|---|---|
| StarterDevelopment and small applications | 2 × Database node (8 cloudlets, 1 GiB each), 2 × ProxySQL (2 cloudlets, 256 MiB each) | 20 | $49.20 |
| StandardProduction databases up to a few GB | 3 × Database node (16 cloudlets, 2 GiB each), 2 × ProxySQL (4 cloudlets, 512 MiB each) | 56 | $137.76 |
| ProductionLarge, write-heavy databases | 3 × Database node (32 cloudlets, 4 GiB each), 2 × ProxySQL (4 cloudlets, 512 MiB each) | 104 | $255.84 |
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.
MySQL Cluster on MassiveGRID PaaS vs DigitalOcean Managed MySQL (as a managed-database example) vs a VPS
DigitalOcean Managed MySQL (as a managed-database example) figures were read from the vendor's page on 1 November 2026; re-check them before relying on them.
| Aspect | MySQL Cluster on MassiveGRID PaaS | DigitalOcean Managed MySQL (as a managed-database example) | A plain VPS |
|---|---|---|---|
| Monthly cost | About $49.20 (Starter, two 1 GiB nodes with ProxySQL) to $255.84 (Production, three 4 GiB Galera nodes), before discounts | Smallest plan 1 GiB RAM, 1 vCPU at $15.15 a month for a single node; storage $0.215 per GiB; additional nodes priced on request | Two or three servers you configure replication or Galera on; plus your time |
| What you manage | The application inside the containers (updates, configuration); the platform runs the infrastructure, scaling and the 100% uptime SLA | Nothing; the provider runs it | Everything: OS, runtime, database, TLS, backups, upgrades |
| Limits and metering | No plan tiers; Galera, primary-primary and primary-secondary all available | Plan sizes; replication topology is the provider's choice | 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 | Resize the plan; add read-only nodes | 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 | The provider's 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 | Included | Your own cron jobs and off-server copies |
| Availability | 100% uptime SLA, nodes on separate hosts, failed containers restarted or migrated | The provider's SLA | 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 | mysqldump is standard | None; you own the server |
Where DigitalOcean Managed MySQL (as a managed-database example) is the better choice: A managed MySQL is the right answer for one small database with backups included and no clustering needs; the package wins when the topology matters, Galera in particular, which managed offerings rarely provide.
How to deploy MySQL 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 MySQL 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.
MySQL Cluster guides from the MassiveGRID blog
Managed MariaDB and MySQL questions
Deploy MySQL Cluster today
Start the free 14-day trial and have MySQL Cluster running in minutes. No credit card required.
Install the MariaDB cluster with free trial