Skip to main content

​
Overview

Understanding the relationship between databases, branches, and clusters is key to understanding your billing:
  • Database: Your overall project (e.g., “my-ecommerce-app”)
  • Branch: Isolated database deployments that provide you with separate environments for development and testing, as well as restoring from backups. Learn more about branching
  • Cluster: The underlying compute and storage infrastructure that powers each branch
Each branch runs on its own dedicated cluster and is billed separately based on its configuration and usage.
  • You are billed for the compute and storage resources (cluster) that power each branch (prorated to the millisecond each month)
  • Every database branch you launch has default included amounts of:
  • Usage beyond the included defaults is charged based on the costs for that resource, this includes:
    • Cluster disk storage used beyond the included amount (for network-attached storage)
    • Backup storage used beyond the included amount
    • Network egress beyond the included amount
    • Additional replicas
There are no upfront commitments, and as you adjust your configuration or usage changes, pricing will automatically adjust from that point.
For information on Vitess cluster pricing on the Scaler Pro plan, see Scaler Pro cluster pricing.

​
Cluster instance size

Each database branch runs on its own dedicated cluster infrastructure. Clusters are billed based on the selected instance size and prorated to the millisecond. Each instance size includes defined amounts of vCPU cores and memory, as well as storage based on the storage type selected (network-attached storage or PlanetScale Metal). See cluster pricing for more information. You can increase or decrease your cluster size at any time. Pricing is prorated to the millisecond, so if you temporarily increase, you will only be charged for the larger cluster size for the time that it was running. Billing for a modified cluster size begins once the resize is completed. You can also spin up additional production branches at any time for additional cost. The pricing for these is also prorated.

​
Cluster disk storage

We use gibibytes, otherwise known as binary gigabytes, to calculate storage and usage limits. For reference, 1 binary gigabyte is equivalent to 2^30 bytes.

​
Storage types explained

PlanetScale offers two storage options with different pricing models:
PlanetScale MetalNetwork-Attached Storage
All-inclusive pricingConfiguration-based pricing
- Storage cost is included in your cluster instance price
- High-performance NVMe SSDs directly attached to your servers
- To get more storage, you upgrade to a larger cluster size
- Best for: High-performance applications that need predictable costs		- First 10 GB included with each cluster
- Additional Storage is billed separately from your cluster instance configuration
- Flexible scaling - add storage without changing cluster size
- Automatic disk scaling with autoscaling
- Best for: Applications with variable storage needs or cost optimization

​
Network-attached storage billing

For network-attached storage clusters, pricing varies by region and cloud provider:
  • Base storage: you manually configure this in cluster settings, unless autoscaling is enabled
  • Additional IOPS: you manually configure this in cluster settings (AWS only)
  • Additional Throughput: you manually configure this in cluster settings (AWS only)
AWS vs GCP Pricing: AWS network-attached storage cluster types allow separate billing for IOPS and throughput that you manually configure. GCP network-attached storage cluster types include IOPS and throughput that scale automatically with disk size at no additional cost. See AWS Storage Pricing and GCP Storage Pricing below for detailed regional pricing.
Billing for modified storage attributes begins once the change for the cluster has completed. What are IOPS and Throughput?
  • IOPS (Input/Output Operations Per Second): How many read/write operations your database can handle per second. Higher IOPS = faster response for many small database queries.
  • Throughput: How much data can be transferred per second (MiB/s). Higher throughput = faster for large data operations like bulk imports.
For more information on changing your cluster’s storage, see the Cluster storage configuration documentation.

​
Backups

​
Included backup storage

PlanetScale automatically includes backup storage with every database branch at no extra cost. Each branch gets backup storage equal to 2x your disk size. Examples:
Disk SizeBackup Storage Included
25 GB50 GB
50 GB100 GB
1000 GB2000 GB
For clusters with network-attached storage with autoscaling enabled, backup storage changes as your disk storage autoscales.
When your backup and WAL storage exceeds the included amount, additional storage is billed at $0.023 per GB per month. Storage overage examples:
Storage OverageDurationCost
100 GB30 days$2.30
100 GB15 days$1.15

​
How backup billing works

Storage calculation: Both database data backups and WAL files are automatically compressed before being sent to backup storage. You’re billed only on the compressed size, which is typically much smaller than your active database size. Backup storage usage billing data is updated hourly. For more details on backup functionality, see Back up and restore. What affects storage costs:
FactorImpact
Database activityMore active databases generate more WAL files
Backup retentionLonger retention periods increase storage usage
Oldest backup ageWAL files are kept as long as your oldest backup exists

​
Network data transfer

Outgoing network traffic (egress) is billed based on the amount of data transferred out of PlanetScale Postgres instances to any other host or destination. You are not charged for data transfer for purposes such as Primary to Replica replication or backups. Each branch has a default amount of included network egress that is aggregated for all cluster instances in the entire branch.
Branch TypeIncluded Network Egress
Production100 GB per month
Development (PS-DEV)10 GB per month
See AWS Egress Pricing and GCP Egress Pricing below for detailed regional pricing. Incoming network traffic (ingress) is free.

​
Additional replicas

Each production cluster includes 2 replicas (excluding Single Node) to provide high availability and additional read capacity alongside the primary. Certain read-heavy workloads may demand additional read replicas. If you need additional replicas beyond what is included, you can add them for an additional cost based on the branch’s instance size and storage requirements. The cost of an additional replica instance is ~1/3 the cost of the original 3-node cluster. New replica(s) billing begins once the change has completed. Examples:
Base cluster configuration (includes 2 replicas)Monthly base cluster costAdditional monthly replica costMonthly total
M-160 (r8gd)$589$197$786
M-320 (r8gd)$1,149$383$1,532
M-1280 (i8g)$5,319$1,773$7,092
PS-10 (aarch64 CPU) with 100 GB storage34+34 + 33.75 (additional storage)12+12 + 12.50 (*additional storage)$92.25
PS-160 (aarch64 CPU) with 1000 GB storage286+286 + 371.25 (additional storage)96+96 + 125 (*additional storage)$878.25
*Note: Replicas with network-attached storage do not include the default included cluster storage disk amount of 10GB. You pay for the entire configured disk size. Figures shown here are for AWS based instances with additional storage amounts and no additional IOPS/Throughput configured. Development branches and Single Node databases do not support replicas. For more information on replicas, see Replicas.

​
Cluster pricing

Cluster instance pricing is based on the cloud provider’s own pricing for the compute resources. Prices shown are for the us-east-1 (N. Virginia) region. Pricing may vary by region.
Visit our pricing page for interactive pricing configuration and region-specific details.

​
Network-attached storage clusters

These clusters use network-attached storage, which is billed separately from compute. Storage can scale independently of your instance size.
  • Single Node clusters are a single database instance, ideal for development, cost-sensitive startups, or non-critical workloads.
  • Highly Available clusters are 3-node clusters with automatic failover for production workloads.
Single Node PlanetScale Postgres databases start at $5 per month.
NameConfigurationMonthly CostCPUMemory
PS-5-AWS-X86Single Node$51/16 vCPU512 MB
PS-5-AWS-X86Highly Available$151/16 vCPU512 MB
PS-5-AWS-ARMSingle Node$51/16 vCPU512 MB
PS-5-AWS-ARMHighly Available$151/16 vCPU512 MB
PS-10-AWS-ARMSingle Node$101/8 vCPU1 GB
PS-10-AWS-ARMHighly Available$301/8 vCPU1 GB
PS-10-AWS-X86Single Node$131/8 vCPU1 GB
PS-10-AWS-X86Highly Available$391/8 vCPU1 GB
PS-20-AWS-ARMSingle Node$171/4 vCPU2 GB
PS-20-AWS-ARMHighly Available$501/4 vCPU2 GB
PS-20-AWS-X86Single Node$201/4 vCPU2 GB
PS-20-AWS-X86Highly Available$591/4 vCPU2 GB
PS-40-AWS-ARMSingle Node$281/2 vCPU4 GB
PS-40-AWS-ARMHighly Available$831/2 vCPU4 GB
PS-40-AWS-X86Single Node$331/2 vCPU4 GB
PS-40-AWS-X86Highly Available$991/2 vCPU4 GB
PS-80-AWS-ARMSingle Node$491 vCPU8 GB
PS-80-AWS-ARMHighly Available$1481 vCPU8 GB
PS-80-AWS-X86Single Node$601 vCPU8 GB
PS-80-AWS-X86Highly Available$1791 vCPU8 GB
PS-160-AWS-ARMSingle Node$952 vCPUs16 GB
PS-160-AWS-ARMHighly Available$2862 vCPUs16 GB
PS-160-AWS-X86Single Node$1162 vCPUs16 GB
PS-160-AWS-X86Highly Available$3492 vCPUs16 GB
PS-320-AWS-ARMSingle Node$1904 vCPUs32 GB
PS-320-AWS-ARMHighly Available$5704 vCPUs32 GB
PS-320-AWS-X86Single Node$2334 vCPUs32 GB
PS-320-AWS-X86Highly Available$6994 vCPUs32 GB
PS-640-AWS-ARMSingle Node$3788 vCPUs64 GB
PS-640-AWS-ARMHighly Available$1,1358 vCPUs64 GB
PS-640-AWS-X86Single Node$4668 vCPUs64 GB
PS-640-AWS-X86Highly Available$1,3998 vCPUs64 GB
PS-1280-AWS-ARMSingle Node$75516 vCPUs128 GB
PS-1280-AWS-ARMHighly Available$2,26516 vCPUs128 GB
PS-1280-AWS-X86Single Node$93316 vCPUs128 GB
PS-1280-AWS-X86Highly Available$2,79916 vCPUs128 GB
PS-2560-AWS-ARMSingle Node$1,51032 vCPUs256 GB
PS-2560-AWS-ARMHighly Available$4,52932 vCPUs256 GB
PS-2560-AWS-X86Single Node$1,86632 vCPUs256 GB
PS-2560-AWS-X86Highly Available$5,59932 vCPUs256 GB

​
PlanetScale Metal clusters

PlanetScale Metal clusters include high-performance NVMe storage directly attached to your servers. Storage is included in the cluster price.
PlanetScale Postgres Metal clusters start at $50 per month.
NameConfigurationMonthly CostCPUMemoryStorage
M1-10-AWS-ARM-D-METAL-10Highly Available$501/8 vCPU1 GB10 GB
M1-10-AWS-AMD-D-METAL-10Highly Available$601/8 vCPU1 GB10 GB
M1-10-AWS-ARM-D-METAL-25Highly Available$601/8 vCPU1 GB25 GB
M1-10-AWS-AMD-D-METAL-25Highly Available$701/8 vCPU1 GB25 GB
M1-10-AWS-ARM-D-METAL-50Highly Available$801/8 vCPU1 GB50 GB
M1-10-AWS-AMD-D-METAL-50Highly Available$901/8 vCPU1 GB50 GB
M1-10-AWS-ARM-D-METAL-100Highly Available$1101/8 vCPU1 GB100 GB
M1-10-AWS-AMD-D-METAL-100Highly Available$1201/8 vCPU1 GB100 GB
M1-10-AWS-ARM-D-METAL-200Highly Available$1801/8 vCPU1 GB200 GB
M1-10-AWS-AMD-D-METAL-200Highly Available$2001/8 vCPU1 GB200 GB
M1-20-AWS-ARM-D-METAL-10Highly Available$801/4 vCPU2 GB10 GB
M1-20-AWS-AMD-D-METAL-10Highly Available$901/4 vCPU2 GB10 GB
M1-20-AWS-ARM-D-METAL-25Highly Available$901/4 vCPU2 GB25 GB
M1-20-AWS-AMD-D-METAL-25Highly Available$1001/4 vCPU2 GB25 GB
M1-20-AWS-ARM-D-METAL-50Highly Available$1101/4 vCPU2 GB50 GB
M1-20-AWS-AMD-D-METAL-50Highly Available$1201/4 vCPU2 GB50 GB
M1-20-AWS-ARM-D-METAL-100Highly Available$1401/4 vCPU2 GB100 GB
M1-20-AWS-AMD-D-METAL-100Highly Available$1501/4 vCPU2 GB100 GB
M1-20-AWS-ARM-D-METAL-200Highly Available$2101/4 vCPU2 GB200 GB
M1-20-AWS-AMD-D-METAL-200Highly Available$2301/4 vCPU2 GB200 GB
M1-40-AWS-ARM-D-METAL-10Highly Available$1501/2 vCPU4 GB10 GB
M1-40-AWS-AMD-D-METAL-10Highly Available$1601/2 vCPU4 GB10 GB
M1-40-AWS-ARM-D-METAL-25Highly Available$1601/2 vCPU4 GB25 GB
M1-40-AWS-AMD-D-METAL-25Highly Available$1701/2 vCPU4 GB25 GB
M1-40-AWS-ARM-D-METAL-50Highly Available$1801/2 vCPU4 GB50 GB
M1-40-AWS-AMD-D-METAL-50Highly Available$1901/2 vCPU4 GB50 GB
M1-40-AWS-ARM-D-METAL-100Highly Available$2001/2 vCPU4 GB100 GB
M1-40-AWS-AMD-D-METAL-100Highly Available$2101/2 vCPU4 GB100 GB
M1-40-AWS-ARM-D-METAL-200Highly Available$2701/2 vCPU4 GB200 GB
M1-40-AWS-AMD-D-METAL-200Highly Available$2901/2 vCPU4 GB200 GB
M1-40-AWS-ARM-D-METAL-400Highly Available$3301/2 vCPU4 GB400 GB
M1-40-AWS-AMD-D-METAL-400Highly Available$3401/2 vCPU4 GB400 GB
M1-40-AWS-ARM-D-METAL-800Highly Available$4801/2 vCPU4 GB800 GB
M1-40-AWS-AMD-D-METAL-800Highly Available$4901/2 vCPU4 GB800 GB
M1-40-AWS-ARM-D-METAL-1200Highly Available$6101/2 vCPU4 GB1,228 GB
M1-40-AWS-AMD-D-METAL-1200Highly Available$6201/2 vCPU4 GB1,228 GB
M1-80-AWS-ARM-D-METAL-100Highly Available$3201 vCPU8 GB100 GB
M1-80-AWS-AMD-D-METAL-100Highly Available$3401 vCPU8 GB100 GB
M1-80-AWS-ARM-D-METAL-200Highly Available$3901 vCPU8 GB200 GB
M1-80-AWS-AMD-D-METAL-200Highly Available$4101 vCPU8 GB200 GB
M1-80-AWS-ARM-D-METAL-400Highly Available$4601 vCPU8 GB400 GB
M1-80-AWS-AMD-D-METAL-400Highly Available$4801 vCPU8 GB400 GB
M1-80-AWS-ARM-D-METAL-800Highly Available$6001 vCPU8 GB800 GB
M1-80-AWS-AMD-D-METAL-800Highly Available$6101 vCPU8 GB800 GB
M1-80-AWS-ARM-D-METAL-1200Highly Available$7401 vCPU8 GB1,228 GB
M1-80-AWS-AMD-D-METAL-1200Highly Available$7501 vCPU8 GB1,228 GB
M1-160-AWS-ARM-D-METAL-100Highly Available$5702 vCPUs16 GB100 GB
M1-160-AWS-AMD-D-METAL-100Highly Available$5802 vCPUs16 GB100 GB
M1-160-AWS-ARM-D-METAL-200Highly Available$6302 vCPUs16 GB200 GB
M1-160-AWS-AMD-D-METAL-200Highly Available$6502 vCPUs16 GB200 GB
M1-160-AWS-ARM-D-METAL-400Highly Available$6802 vCPUs16 GB400 GB
M1-160-AWS-AMD-D-METAL-400Highly Available$7202 vCPUs16 GB400 GB
M1-160-AWS-ARM-D-METAL-800Highly Available$8002 vCPUs16 GB800 GB
M1-160-AWS-AMD-D-METAL-800Highly Available$8302 vCPUs16 GB800 GB
M1-160-AWS-ARM-D-METAL-1200Highly Available$9802 vCPUs16 GB1,228 GB
M1-160-AWS-AMD-D-METAL-1200Highly Available$1,0002 vCPUs16 GB1,228 GB
M8-160-AWS-ARM-D-METAL-118Highly Available$5892 vCPUs16 GB118 GB
M6-160-AWS-INTEL-D-METAL-118Highly Available$6092 vCPUs16 GB118 GB
M7-160-AWS-INTEL-D-METAL-468Highly Available$7292 vCPUs16 GB468 GB
M7-160-AWS-INTEL-D-METAL-1250Highly Available$1,0092 vCPUs16 GB1,280 GB
M8-320-AWS-ARM-D-METAL-237Highly Available$1,1494 vCPUs32 GB237 GB
M6-320-AWS-INTEL-D-METAL-237Highly Available$1,1794 vCPUs32 GB237 GB
M7-320-AWS-INTEL-D-METAL-937Highly Available$1,4294 vCPUs32 GB937 GB
M7-320-AWS-INTEL-D-METAL-2500Highly Available$1,9994 vCPUs32 GB2,560 GB
M8-640-AWS-ARM-D-METAL-474Highly Available$2,2698 vCPUs64 GB474 GB
M6-640-AWS-INTEL-D-METAL-474Highly Available$2,3298 vCPUs64 GB474 GB
M7-640-AWS-INTEL-D-METAL-1875Highly Available$2,8398 vCPUs64 GB1,875 GB
M7-640-AWS-INTEL-D-METAL-5000Highly Available$3,9598 vCPUs64 GB5,120 GB
M7-960-AWS-INTEL-D-METAL-7500Highly Available$5,92912 vCPUs96 GB7,680 GB
M8-1280-AWS-ARM-D-METAL-950Highly Available$4,49916 vCPUs128 GB950 GB
M6-1280-AWS-INTEL-D-METAL-950Highly Available$4,62916 vCPUs128 GB950 GB
M7-1280-AWS-INTEL-D-METAL-3750Highly Available$5,63916 vCPUs128 GB3,840 GB
M7-1920-AWS-INTEL-D-METAL-15000Highly Available$11,82924 vCPUs192 GB15,360 GB
M8-2560-AWS-ARM-D-METAL-1900Highly Available$8,97932 vCPUs256 GB1,945 GB
M6-2560-AWS-INTEL-D-METAL-1900Highly Available$9,22932 vCPUs256 GB1,945 GB
M7-2560-AWS-INTEL-D-METAL-7500Highly Available$11,24932 vCPUs256 GB7,680 GB
M8-3840-AWS-ARM-D-METAL-2850Highly Available$13,44948 vCPUs384 GB2,918 GB
M6-3840-AWS-INTEL-D-METAL-2850Highly Available$13,82948 vCPUs384 GB2,918 GB
M7-3840-AWS-INTEL-D-METAL-11250Highly Available$16,85948 vCPUs384 GB11,520 GB
M7-3840-AWS-INTEL-D-METAL-30000Highly Available$23,62948 vCPUs384 GB30,720 GB
M8-5120-AWS-ARM-D-METAL-3800Highly Available$17,91964 vCPUs512 GB3,891 GB
M6-5120-AWS-INTEL-D-METAL-3800Highly Available$18,43964 vCPUs512 GB3,891 GB
M7-5120-AWS-INTEL-D-METAL-15000Highly Available$22,46964 vCPUs512 GB15,360 GB
M7-5760-AWS-INTEL-D-METAL-45000Highly Available$35,42972 vCPUs576 GB46,080 GB
M8-7680-AWS-ARM-D-METAL-5700Highly Available$26,86996 vCPUs768 GB5,836 GB
M6-7680-AWS-INTEL-D-METAL-5700Highly Available$27,63996 vCPUs768 GB5,836 GB
M7-7680-AWS-INTEL-D-METAL-22500Highly Available$33,68996 vCPUs768 GB23,040 GB
M7-7680-AWS-INTEL-D-METAL-60000Highly Available$47,22996 vCPUs768 GB61,440 GB
M6-10240-AWS-INTEL-D-METAL-7600Highly Available$33,509128 vCPUs1 TB7,782 GB
M8-15360-AWS-ARM-D-METAL-11400Highly Available$48,849192 vCPUs1 TB11,673 GB
M7-15360-AWS-INTEL-D-METAL-45000Highly Available$67,349192 vCPUs1 TB46,080 GB
M7-15360-AWS-INTEL-D-METAL-120000Highly Available$94,429192 vCPUs1 TB122,880 GB

​
Storage pricing

Network-attached storage pricing varies by region and includes three billable components:
  • Storage: The cost per GB of data stored per month (can auto-scale with usage if enabled)
  • Additional IOPS: Cost when you manually configure more input/output operations per second beyond the included baseline
  • Additional Throughput: Cost when you manually configure more data transfer throughput (MiB/s) beyond the included baseline
Most applications only pay for base storage. IOPS and throughput charges only apply if you manually increase these settings beyond the included baseline in your cluster configuration.
The table below shows the pricing for all three components across different AWS regions. Your total storage cost will depend on your configuration of each component.

​
AWS storage pricing

Cloud ProviderRegionStorage (per GB/month)Additional IOPS (per IOPS/month)Additional Throughput (per MiB/s/month)
AWSap-northeast-1 (Tokyo)$0.150$0.011$0.088
AWSap-south-1 (Mumbai)$0.143$0.103$0.084
AWSap-southeast-1 (Singapore)$0.150$0.011$0.088
AWSap-southeast-2 (Sydney)$0.150$0.011$0.088
AWSca-central-1 (Montreal)$0.138$0.010$0.081
AWSeu-central-1 (Frankfurt)$0.149$0.011$0.088
AWSeu-west-1 (Dublin)$0.138$0.010$0.081
AWSeu-west-2 (London)$0.145$0.011$0.084
AWSsa-east-1 (Sao Paulo)$0.238$0.018$0.139
AWSus-east-1 (N. Virginia)$0.125$0.009$0.073
AWSus-east-2 (Ohio)$0.125$0.009$0.073
AWSus-west-2 (Oregon)$0.125$0.009$0.073

​
GCP storage pricing

The table below shows the storage pricing for Google Cloud Platform regions. GCP storage pricing includes only base storage costs, with IOPS and throughput that scale with disk size.
Cloud ProviderRegionStorage (per GB/month)
GCPasia-northeast3 (Seoul, South Korea)$0.221
GCPnorthamerica-northeast1 (Montréal, Québec)$0.187
GCPus-central1 (Council Bluffs, Iowa)$0.170
GCPus-east4 (Ashburn, Virginia)$0.187

​
Egress pricing

​
AWS egress pricing

The table below shows the egress pricing (per GB beyond included amounts) for AWS regions.
Cloud ProviderRegionEgress (per GB)
AWSap-northeast-1 (Tokyo)$0.101
AWSap-south-1 (Mumbai)$0.096
AWSap-southeast-1 (Singapore)$0.096
AWSap-southeast-2 (Sydney)$0.111
AWSca-central-1 (Montreal)$0.060
AWSeu-central-1 (Frankfurt)$0.060
AWSeu-west-1 (Dublin)$0.060
AWSeu-west-2 (London)$0.060
AWSsa-east-1 (Sao Paulo)$0.137
AWSus-east-1 (N. Virginia)$0.060
AWSus-east-2 (Ohio)$0.060
AWSus-west-2 (Oregon)$0.060

​
GCP egress pricing

The table below shows the egress pricing (per GB beyond included amounts) for Google Cloud Platform regions.
Cloud ProviderRegionEgress (per GB)
GCPasia-northeast3 (Seoul, South Korea)$0.117
GCPeurope-west1 (St Ghislain, Belgium)$0.060
GCPnorthamerica-northeast1 (Montréal, Québec)$0.060
GCPus-central1 (Council Bluffs, Iowa)$0.060
GCPus-east4 (Ashburn, Virginia)$0.060

​
PgBouncer pricing

Dedicated PgBouncer instances are billed monthly based on their size and region. The local PgBouncer (included on the primary database instance) is free. Learn more about PgBouncer configuration in the PgBouncer documentation. PgBouncer instances are available in six sizes:
SizeCPUMemory
PGB-51/16 vCPU128 MB
PGB-101/8 vCPU256 MB
PGB-201/4 vCPU512 MB
PGB-401/2 vCPU1 GB
PGB-801 vCPU2 GB
PGB-1602 vCPU4 GB

​
AWS PgBouncer pricing

The table below shows the monthly pricing for dedicated PgBouncer instances across AWS regions.
RegionPGB-5PGB-10PGB-20PGB-40PGB-80PGB-160
ap-northeast-1 (Tokyo)$21$41$82$164$327$653
ap-south-1 (Mumbai)$12$24$47$93$186$371
ap-southeast-1 (Singapore)$21$41$82$164$327$653
ap-southeast-2 (Sydney)$21$41$82$163$325$649
ca-central-1 (Montreal)$19$38$75$150$299$598
eu-central-1 (Frankfurt)$21$41$82$164$327$653
eu-west-1 (Dublin)$20$39$77$153$305$610
eu-west-2 (London)$22$44$88$176$351$701
sa-east-1 (Sao Paulo)$30$59$117$234$467$933
us-east-1 (N. Virginia)$18$35$69$138$276$551
us-east-2 (Ohio)$18$35$69$138$276$551
us-west-2 (Oregon)$18$35$69$138$276$551

​
GCP PgBouncer pricing

The table below shows the monthly pricing for dedicated PgBouncer instances across Google Cloud Platform regions.
RegionPGB-5PGB-10PGB-20PGB-40PGB-80PGB-160
asia-northeast3 (Seoul, South Korea)$22$44$87$174$348$695
europe-west1 (Belgium)$19$38$76$151$302$603
northamerica-northeast1 (Montréal, Québec)$19$38$76$151$302$604
us-central1 (Council Bluffs, Iowa)$18$35$70$139$277$554
us-east4 (Ashburn, Virginia)$20$39$78$155$309$617

​
Need help?

Get help from the PlanetScale Support team, or join our GitHub discussion board to see how others are using PlanetScale.