Websites & CMS on MassiveGRID PaaS

A content management system is the one application most organisations run for years, and the hosting decision made on day one follows it. The marketplace packages in this category install the application the way its own project recommends, on MassiveGRID PaaS, built on Virtuozzo Application Platform (formerly Jelastic): PHP platforms such as WordPress, Drupal, Joomla, MODX and Moodle get an NGINX or Apache node with PHP-FPM and OPcache and a MariaDB node; Java platforms such as Liferay, Magnolia, OpenCms, Ametys, Alfresco and XWiki get a Java application server with the heap the project needs; Odoo and django CMS get Python and PostgreSQL. Every environment carries a platform subdomain with a valid certificate from the first minute, and a custom domain takes one add-on.

What the platform adds is operational. Each node scales vertically by the cloudlet (128 MiB RAM plus 400 MHz CPU) as traffic changes, so a quiet site costs a few dollars and a campaign day costs more only for its hours. Application nodes can be scaled horizontally behind a load balancer when a single node is no longer enough, the whole environment can be cloned for an upgrade rehearsal, and backups are add-ons you attach from the same marketplace. Billing is hourly at $0.003372 per cloudlet-hour, $2.46 per cloudlet-month, with no licence fee for any package.

Pick by the editorial model, not by the hosting. WordPress suits sites and shops that live on plugins and themes; the WordPress cluster is the choice when the site cannot be down for a deploy. Drupal fits structured content with many editors and public-sector workflows. Joomla and MODX sit between the two. Moodle is a learning platform with its own sizing rules (concurrent users, not enrolments), and Odoo is an ERP that happens to include a website builder.

Java platforms cost more at rest and scale further. Liferay, Magnolia, OpenCms, Ametys and Alfresco each want several gigabytes for the JVM before the first page is served, which is why their Starter estimates are higher than the PHP packages. If the requirement is a portal, an enterprise document repository or a multi-site publishing operation, that footprint pays for itself; for a marketing site it does not.

Start with the Starter row and let the platform grow it. Every package page carries a sizing table with three configurations and the monthly estimate for each. Install the Starter configuration during the trial, watch the cloudlet usage in the dashboard for a week, and raise the limits or add a node when the graph says so.

Every package page carries a sizing table with three configurations. To price a configuration of your own, or to see what a package costs on a working-hours schedule, use the PaaS pricing calculator.