Google AlloyDB Pricing
Monthly price of every Google AlloyDB machine shape — PostgreSQL-compatible, on-demand, across Google Cloud regions. Pick your region and sort by any column.
| alloydb-2 | 2 | 16 | $227 |
| alloydb-4 | 4 | 32 | $455 |
| alloydb-8 | 8 | 64 | $909 |
| alloydb-16 | 16 | 128 | $1,818 |
| alloydb-32 | 32 | 256 | $3,637 |
| alloydb-64 | 64 | 512 | $7,273 |
| alloydb-96 | 96 | 768 | $10,910 |
| alloydb-128 | 128 | 1024 | $14,547 |
8 instances · US Central (Iowa) · prices are for the database instance (compute) only — storage, backups, and networking are billed separately. Indicative prices as of July 8, 2026; verify with the provider.
How Google AlloyDB pricing works
AlloyDB is PostgreSQL-compatible and prices the database instance by its resources: you pay per vCPU and per GB of memory, by the hour, at a fixed 8 GB per vCPU across one machine family from 2 to 128 vCPU. The table shows that as a monthly figure (hourly rate × 730).
An AlloyDB cluster runs a primary instance plus optional read-pool instances, and you pay for each instance’s compute at the rates here. Storage is usage-based — it scales automatically rather than being pre-provisioned — and it, along with backups and networking, is billed separately and varies by region.
AlloyDB has no committed-use discount shown here (Google’s commitments are spend-based, not per instance). For standard managed databases see the Google Cloud SQL, Amazon RDS, and Amazon Aurora pricing tables.
Google AlloyDB pricing FAQ
- How much does Google AlloyDB cost?
- On-demand AlloyDB starts around $227/month for the smallest machine (alloydb-2, 2 vCPU / 16 GB) and scales to over fourteen thousand per month for the largest 128-vCPU shape (us-central1). That is the price of one instance's compute only — storage, backups, and networking are billed separately. AlloyDB has no free tier.
- How is AlloyDB priced?
- AlloyDB is PostgreSQL-compatible and priced per vCPU-hour plus per GB-of-memory-hour, at a fixed 8 GB per vCPU across one machine family from 2 to 128 vCPU. The table shows the monthly figure (hourly rate × 730). You pay per instance in the cluster — the primary and each read-pool node.
- Does the price include storage?
- No. The table prices the database instance (compute) only. AlloyDB storage is usage-based and scales automatically (you don't pre-provision it), and it — along with automated backups and networking — is billed separately by Google Cloud and varies by region.
- How does AlloyDB pricing compare to Cloud SQL?
- AlloyDB costs more per vCPU than Cloud SQL and targets demanding transactional and analytical PostgreSQL workloads with higher performance and read scale-out. For standard managed PostgreSQL or MySQL, Cloud SQL is usually cheaper — see its pricing table to compare.
- Does AlloyDB have committed-use discounts?
- Yes, but they are spend-based (a 1- or 3-year commitment to a dollar amount of usage) applied at the billing account, not tied to a specific instance — so they can't be shown per row. This table lists on-demand rates.
- Is AlloyDB pricing the same in every region?
- No. Rates vary by Google Cloud region; us-central1 (Iowa) is usually among the cheapest. Switch regions with the selector above to see local pricing.