Pay per use $0.003372 per cloudlet-hour

PaaS Pricing Calculator

MassiveGRID PaaS bills every container hourly for the cloudlets it uses, at $0.003372 per cloudlet-hour ($2.46 per cloudlet-month), with no licence fee for any marketplace package and the same rate in all four regions. Pick a package configuration below or build your own topology, set the hours it runs, and read the estimate.

$2.46

Per cloudlet-month

128 MiB

RAM per cloudlet

Package presets

14 days

Free trial

Calculator

Estimate a configuration

Start from a package preset (every sizing row on the marketplace is here) or add nodes by hand. One cloudlet is 128 MiB RAM plus 400 MHz CPU; a node's figure is its allocation, and the environment is billed for what the nodes actually use up to it.

Package and configuration

Hours per month

Node	Cloudlets each	Count	Subtotal	Remove

Custom topology

$0.00per month

$0.0000per hour

$0.00per year

0 cloudlets0 MiB RAM

Before volume discounts. Disk and external traffic are billed per gigabyte on top. A quiet environment uses fewer cloudlets than its allocation and is billed for what it used.

Install with free trial

How Billing Works

How PaaS billing works

Cloudlets, not plans. Every container in an environment has a cloudlet limit you set in the topology wizard. The container uses as many cloudlets as its load needs, up to the limit, and the hour is billed for the cloudlets it actually used. There are no plan tiers, no minimum term and no licence fee for the marketplace packages.

Vertical scaling is automatic. A node that needs more memory at 09:00 gets it without a restart and gives it back at 18:00. Horizontal scaling, adding nodes behind a load balancer, is a trigger you set on the layer; the new nodes are billed from the hour they start to the hour they stop.

Hours matter. An environment that is stopped is billed only for its stopped storage, which is why the Start/Stop Scheduler add-on makes development and staging environments cheap: a Standard-sized environment that runs working hours costs about a quarter of the always-on figure.

Disk and traffic are separate. Disk is billed per gigabyte used and external traffic per gigabyte transferred; internal traffic between environments in the same account is free. Neither is in the calculator, because both depend on the application rather than the topology.

Volume discounts apply automatically as an account's monthly usage grows, so the figures here are the ceiling for a new account. The PaaS page describes the platform, and every marketplace package page carries its own sizing table.

Examples

What common packages cost

The Starter configuration of six popular packages, always on and on a working-hours schedule (176 hours), at the published rate before discounts.

Package	Starter topology	Cloudlets	Always on	Working hours
WordPress Standalone	LiteSpeed WordPress node (web, MariaDB and Redis) (8 cloudlets, 1 GiB)	8	$19.68	$4.75
n8n	Node.js application server (8 cloudlets, 1 GiB), PostgreSQL database (4 cloudlets, 512 MiB)	12	$29.52	$7.12
GitLab Server	GitLab CE server (64 cloudlets, 8 GiB)	64	$157.44	$37.98
Kubernetes Cluster	Control plane (16 cloudlets, 2 GiB), Worker node (16 cloudlets, 2 GiB)	32	$78.72	$18.99
Odoo	Odoo application server (16 cloudlets, 2 GiB), PostgreSQL database (8 cloudlets, 1 GiB)	24	$59.04	$14.24
Redis Cluster	6 × Redis node (2 cloudlets, 256 MiB each)	12	$29.52	$7.12

FAQ

Pricing Questions

A cloudlet is the platform's billing unit: 128 MiB of RAM plus 400 MHz of CPU. Every container in an environment is given a cloudlet limit, uses as many as it needs up to that limit, and is billed hourly for the cloudlets it actually used. Eight cloudlets are 1 GiB of RAM.

$0.003372 per cloudlet-hour, which is $2.46 per cloudlet for a 730-hour month. The rate is the same in New York, London, Frankfurt and Singapore, and there is no licence fee for any marketplace package. Volume discounts apply automatically as an account's usage grows.

Because billing is hourly. A production environment runs 730 hours a month; a development or staging environment stopped with the Start/Stop Scheduler outside working hours runs about 176 (eight hours on 22 weekdays) and is billed for those hours plus a small charge for stopped storage. The buttons set the common cases; type any figure.

It is the cost of the configuration if every node averages the listed cloudlets for the hours you set, before volume discounts. Real bills are usually lower for a quiet environment, because vertical auto-scaling releases cloudlets the application is not using, and higher when traffic grows. Disk and external traffic are billed per gigabyte on top and are not in the estimate.

From the sizing table on each package page: three starting configurations per application, built from the project's published requirements and typical allocations. They are starting points, not measurements; the dashboard's statistics show what your environment actually uses after a week.

Yes. New accounts get a 14-day free trial with no credit card. Install the configuration you priced, watch its usage, and convert to pay-per-use billing only when you add a payment method.

Price it, then try it free

Install the configuration you priced on the 14-day trial, no credit card required, and compare the estimate with the dashboard's usage graph.

Start Free 14-Day Trial