Skip to main content
Each Neki branch has its own database infrastructure. Its estimated monthly price depends on the Postgres clusters provisioned for its shards, its router compute, and its storage, backup, and network usage. The PlanetScale dashboard shows the rates available to your organization. SKU prices vary by cloud provider, region, and your organization’s commercial terms. Use the dashboard estimate or the pricing calculator for the current rate of a specific size. Do not assume a us-east-1 example applies everywhere.

pricing.md

For an agent-friendly catalog of live cluster SKU rates and example SQL, fetch https://planetscale.com/pricing.md.

​
What appears on the bill

A configuration profile has no compute cost by itself. Adding a shard adds another copy of that profile’s cluster SKU to the bill. Routers are not multiplied by shard count. There are no upfront commitments. Clusters are billed based on the selected instance size and prorated to the millisecond. Router compute is billed based on the selected router size and number of routers and prorated to the millisecond.

​
Cluster SKU rates

Every shard assigned to a configuration profile uses that profile’s cluster size. Neki does not offer a single-node configuration. The highly available SKU rate covers one primary and two replicas.
The size menu in Clusters shows the monthly rate, additional-replica rate, vCPU, and memory for each option. Metal SKUs include local NVMe storage in that rate. Network-attached storage SKUs bill network-attached storage separately. If four shards share one profile, you pay four times that profile’s highly available SKU rate. See Cluster sizing.

​
Additional replicas

You can add replicas above the two included with the SKU. You cannot set the replica count to anything lower than 2. Extra replicas use the SKU’s additional-replica rate, which is about one third of the highly available rate.
Each extra network-attached storage replica also gets its own network-attached disk. Those volumes do not receive the 10 GB included allowance; you pay for the full allocated size. See Database replicas.

​
Router SKU rates

Every Neki branch has routers, which use a separate SKU from shard compute. A production branch starts with one router in each availability zone. Upsizing shards does not change the router size. The monthly production rate shown for a router size covers the three-router baseline: one router in each of three availability zones (AZ). For a fixed production router configuration with the same replica count in every AZ:
When AZs do not have the same number of running routers, production billing uses the observed total:
A development branch uses one AZ, so its development router rate applies to each running router without the three-AZ divisor. Autoscaling and size changes are prorated to the millisecond.

​
Storage

We use GB as 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:

​
Metal

Local NVMe capacity is included in the Metal SKU rate. To get more local storage, choose a larger Metal size.

​
Network-attached storage

Network-attached storage clusters bill allocated disk separately from compute. Neki measures capacity per shard and attributes it to that shard’s configuration profile. You pay for current allocated capacity, not the configured minimum. AWS gp3 volumes include 10 GB, 3,000 IOPS, and 125 MiB/s per volume on the primary and the two replicas that come with the SKU. Charges apply only to capacity and provisioned IOPS or throughput above those baselines. GCP uses Hyperdisk Balanced. IOPS and throughput scale with disk size at no separate charge; you pay for allocated disk. The configured IOPS and throughput apply to each network volume on every shard in the profile. Regional rates are below. Configure minimum disk, autoscaling, IOPS, and bandwidth from the profile Storage tab.

​
AWS storage rates

​
GCP storage rates

​
Backups

Each branch includes backup storage equal to twice the allocated disk on that branch. Required schedules (every 12 hours, two-day retention) use this allowance. Compressed backup data and WAL above the included amount are billed at $0.023 per GB per month. A protected backup that outlives the default two-day window continues to contribute storage until you turn protection off or delete it. See Back up and restore.

​
Network transfer

Replication between a shard’s primary and its replicas, and backup traffic, are not billed as network transfer.

​
Public traffic

Outgoing public traffic (egress) is billed. Public ingress is free.

​
Private traffic

AWS PrivateLink and GCP Private Service Connect traffic — ingress and egress — is billed at $0.01 per GB, regardless of region. Each branch includes the same allowance as public traffic: 100 GB for production, 10 GB for development.

​
Public egress rates

​
Development branches

A development branch is billed on its own. It uses development SKU rates and the development network allowance. Each development shard is highly available (primary plus at least two replicas). Compute and router charges are prorated to the millisecond and end when you delete the branch. Restoring a backup or point-in-time recovery always creates a new branch, so the restored environment is an additional billed branch until you delete it.

​
Estimate a monthly total

Actual charges differ from a full-month estimate when resources or usage change during the billing period.

​
Need help?

Get help from the PlanetScale Support team, or join our Discord community to see how others are using PlanetScale.