Pricing for Gen 2 Cloud Databases

Fixed profiles

Flex profiles

The total cost of your Cloud Databases deployment will consist of the the cost of each vCPU x RAM profile, disk storage in GB and backup storage (for all members), prorated hourly.

Disk storage

Disk storage is provisioned per member and billed based on the total allocated capacity (GB) across all members in a deployment. Cloud Databases uses IBM Cloud VPC Block Storage as the underlying storage layer. Storage capacity can be configured independently of the selected compute profile, allowing customers to scale storage based on workload requirements.

The available storage performance profile is determined by the region in which the service is deployed. Most regions support the latest generation of storage capabilities (SSD Defined Performance (sdp)), which provides more flexible and consistent performance characteristics. In Chennai - Airtel (in-che), Mumbai - Airtel (in-mum), Montreal (ca-mon), Frankfurt (eu-de), and Washington DC (us-east) regions, storage is delivered using standard profiles with predefined performance levels at 5 IOPS/GB. As a result, both storage performance characteristics and pricing varies by region, reflecting differences in the underlying storage infrastructure.

For customers with specific performance or compliance requirements, it is recommended to validate regional capabilities during deployment planning.

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.