Pricing for Gen 2 Cloud Databases

Gen 2

The charge for an Cloud Databases instance is determined by the following five factors:

  • Database: PostgreSQL, MongoDB
  • Quantity of vCPU allocated per database instance member
  • GB of RAM allocated per database instance member
  • GB of disk storage allocated per database instance member
  • Backup size and retention
Out of the box configurations per database
Database Database type Default configuration
Databases for PostgreSQL Relational 2-member
Databases for MongoDB Non-relational 3-member

Each database instance consists of two or three members, depending on the database type, with each member holding a copy of the data to provide resiliency and high availability. Cloud Databases instances are only available with Isolated compute hosting. Isolated compute offers a choice of standard vCPU x RAM resource profiles that are hosted on single-tenant compute instances for maximum workload isolation and security. Disk storage capacity per member is specified independently of the vCPU x RAM profile selected. Gen 2 deployments depend on regional availability, for more information, see Isolated Compute sizing.

Using the pricing calculator

For pricing estimation, use the Add to estimate button on the provisioning page of each service. Input your total consumption across each data members into the calculator. This is equal to the number of members because your data is replicated to all members. For example, a 2-member Cloud Databases deployment with 5 GB of disk on a 4 vCPU x 20 GB RAM profile would have a total bill for 10 GB of disk and the total cost of 2 members.

Backup storage

Free allocation

  • You receive free backup storage equal to the total provisioned disk size of your deployment.
  • This includes both automated daily backups and manual (on-demand) snapshots.

To help manage variability in monthly charges, especially during failover events or update events, the free backup storage Cloud Databases with every instance is for each member. This buffer ensures that when a failover or cluster update occurs, resulting in a switch in the database primary, it does not result in unexpected costs. In the rare case where there’s no update or failover activity during a given month, your usage may fall below the free allocation, and you'll be charged less accordingly. This approach gives you predictable pricing while still accounting for the realities of high availability.

  • Example: If a 3-member Cloud Databases deployment is provisioned with 100 GB of disk per member, you get 300 GB of backup storage included at no cost.

Overage charges

  • Overage is billed monthly and applies when your snapshot storage exceeds the included allocation.
  • Total snapshot storage = (Initial single member snapshot * number of members) + (Daily change × 29 days).
  • Any usage beyond the free allocation is charged at $0.095 per GB per month.

Worked example, for a 3-member Cloud Databases deployment with 100 GB of data per member

  • Day 1: A full snapshot is taken from the current primary. This consumes 100 GB of snapshot storage.

This models the worst case scenario where the full snapshot is equal to the file system. In practice, especially for new databases (which will grow over time), the snapshot size is often smaller, reducing your backup bill.

  • Day 2-16: You write 10 GB of new data per day. Snapshots are incremental and only store changes. Over 15 days, this adds 150 GB, bringing total snapshot usage to 100 GB + 150 GB = 250 GB.
  • Day 17: A failover occurs, and one secondary member becomes the new primary. A full snapshot is taken from this new primary, consuming another 100 GB. This uses up the remaining free allocation and brings total snapshot usage to 350 GB.
  • Day 18-30: You continue writing 10 GB per day, adding 130 GB over 13 days.
  • Total snapshot = 100 GB (initial) + 150 GB (incremental) + 100 GB (failover snapshot) + 130 GB (post-failover incremental) = 480 GB.
  • Free allocation = 100 GB x 3 members = 300 GB.
  • Overage = 480 GB - 300 GB = 180 GB.
  • Monthly charge = (480 GB - 300 GB) X $0.095 = $17.1.

Scaling per member

Cloud Databases deployments have minimum and maximum allocation for disk and RAM as shown. Scaling deployments through the UI, API and CLI. You can scale database storage up to 4 TB of disk per member, minimum and maximum CPU and RAM combinations vary per region, see Isolated compute.

Scaling limits
Resource Minimum Maximum Scaling granularity
Disk 5 GB per member 4 TB per member 1024 MB per member
RAM 16 GB 240 GB Isolated compute – Resource scaling with host sizes
CPU 4 vCPU 48 vCPU Isolated compute – Resource scaling with host sizes