Managed PostgreSQL Hosting on MassiveGRID PaaS
A PostgreSQL primary with hot standbys and a Pgpool-II entry point installed in one click, sized to the working set by PostgreSQL's own memory rules, with automatic failover, optional TLS and scheduled dumps. Billed by the cloudlet-hour with no plan tiers.
PostgreSQL Cluster on MassiveGRID PaaS installs in one click in New York, London, Frankfurt or Singapore, costs about $39.36 a month for the Starter configuration, a PostgreSQL primary (1 GiB) and a Hot-standby secondary (1 GiB), and starts with a 14-day free trial. See the sizing table.
The install button opens the MassiveGRID PaaS dashboard with PostgreSQL Cluster pre-selected. Sign up without a card, name the environment, pick a region, and the package installs in a few minutes.
Why host PostgreSQL on MassiveGRID PaaS
Managed database services sell the topology a team wants, a primary with standbys and a connection pool, in plan sizes with a price per node. The PostgreSQL cluster package on MassiveGRID PaaS, built on Virtuozzo Application Platform (formerly Jelastic), installs the same topology in one click and bills the nodes by the cloudlet-hour, sized to the working set rather than to a plan.
PostgreSQL's own documentation gives the sizing rule: shared_buffers at 25% of RAM on a dedicated server, rarely above 40%, with the operating system cache holding the rest. The package's sizing table and the requirements guide apply it to a primary and its standbys.
Reads scale on the standbys: reporting and analytics queries leave the primary alone, which the read replicas post sets up for a SaaS application, and a primary failure is a promotion behind Pgpool-II rather than a page, as the failover post recounts.
What the PostgreSQL cluster package deploys
A PostgreSQL primary, one or more hot-standby secondaries with streaming replication, Pgpool-II as the single connection endpoint with read routing, and optional TLS for client connections through the PostgreSQL TLS add-on. Each node is its own container with its own cloudlet limit, scaled vertically without a restart.
Backups are separate from replication, as they should be: the Database Backup/Restore add-on dumps the primary on a timezone-aware schedule to a Backup Storage node with one-click restore, and a standby can be promoted or added from the dashboard. Applications in the same account reach the cluster over the internal network with no traffic charge.
Who hosts PostgreSQL this way
SaaS teams whose application already runs on the platform and wants its database beside it, with read scaling and failover but without a per-node managed-database price.
Teams with a working set that managed plans size badly, a 50 GB database with a 1 GB hot set, which here is a 4 GiB node rather than a plan tier.
Regulated workloads that need the data in one region with their own encryption, backups and retention.
A single small database with no replication needs is well served by a managed database at about $15 a month; the comparison table below says so.
What PostgreSQL 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 | PostgreSQL primary (8 cloudlets, 1 GiB), Hot-standby secondary (8 cloudlets, 1 GiB) | 16 | $39.36 |
| StandardProduction databases | PostgreSQL primary (16 cloudlets, 2 GiB), Hot-standby secondary (16 cloudlets, 2 GiB) | 32 | $78.72 |
| ProductionLarge datasets and read scaling | PostgreSQL primary (32 cloudlets, 4 GiB), 2 × Hot-standby secondary (32 cloudlets, 4 GiB each) | 96 | $236.16 |
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.
PostgreSQL Cluster on MassiveGRID PaaS vs DigitalOcean Managed PostgreSQL (as a managed-database example) vs a VPS
DigitalOcean Managed PostgreSQL (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 | PostgreSQL Cluster on MassiveGRID PaaS | DigitalOcean Managed PostgreSQL (as a managed-database example) | A plain VPS |
|---|---|---|---|
| Monthly cost | About $39.36 (Starter, 1 GiB primary and standby) to $236.16 (Production, 4 GiB primary and two standbys), before discounts | Smallest plan 1 GiB RAM, 1 vCPU at $15.15 a month for a single node; storage $0.215 per GiB; standby nodes priced on request | Two or three servers you configure streaming replication 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; capacity is the nodes' cloudlets, disk per gigabyte | Plan sizes; connection limits per plan | 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 nodes at the provider's price | 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, with point-in-time recovery on most managed offerings | 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 | pg_dump is standard; extensions limited to the provider's list | None; you own the server |
Where DigitalOcean Managed PostgreSQL (as a managed-database example) is the better choice: A managed database is the right answer for a single small instance where $15 a month includes backups and point-in-time recovery and nobody wants to think about it; the package wins once standbys and read scaling enter the picture.
How to deploy PostgreSQL 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 PostgreSQL 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.
PostgreSQL Cluster guides from the MassiveGRID blog
Managed PostgreSQL questions
Deploy PostgreSQL Cluster today
Start the free 14-day trial and have PostgreSQL Cluster running in minutes. No credit card required.
Install the PostgreSQL cluster with free trial