Skip to main content

PlanetScale Pricing, Features & Alternatives

Runtime Platform · BaaS

Managed Vitess or PostgreSQL-compatible databases with branching on hosted infrastructure or dedicated customer cloud accounts.

PlanetScale offers managed MySQL on Vitess and managed PostgreSQL. Vitess uses branches and deploy requests for schema workflows; PostgreSQL branches are created empty or from backups and do not use the same schema-promotion model. PostgreSQL network-attached storage can grow automatically, while high availability, point-in-time recovery, and read-replica behavior depend on engine and configuration. PostgreSQL disk autoscaling excludes Metal, and single-node PostgreSQL branches are not high-availability configurations.
Best for

Production MySQL and PostgreSQL applications that value database branching, managed operations, schema workflows, vertical scaling, and optional high-availability configurations.

Watch out for

PlanetScale has no free tier. Every database, production branch, development branch, storage allocation, backup, and network transfer choice can affect monthly cost.

Workloads
  • Backend Services
  • Web Applications
Services
  • Managed Databases
Delivery
  • Managed
  • BYOC

Development & Execution

Supported platform capabilities, execution environments, development technologies, deployment models, integrations, and triggers.

Database support

  • MySQL
  • PostgreSQL
  • Vitess

Capabilities

  • Storage Autoscaling
  • Automatic Failover
  • Database Branching
  • Point-in-Time Recovery
  • Read Replicas
  • Automated Backups

Client languages

  • C#
  • Go
  • Java
  • JavaScript
  • Kotlin
  • PHP
  • Python
  • Ruby
  • Rust
  • TypeScript

Framework compatibility

  • Django
  • Express.js
  • Fastify
  • Laravel
  • Next.js
  • Nuxt
  • Remix
  • Ruby on Rails
  • Spring Boot
  • SvelteKit

Integrations

  • Cloudflare
  • GitHub
  • Terraform

Deployment model

  • Serverless (Managed Runtime)

Architecture

  • x64
  • ARM

Pricing

Published pricing structure, representative costs, and material billing factors.

Starting Price
$5 / month PS-5 (single-node)
Primary Billing
Instance based Cluster SKUs
Included Usage
10 GB storage per cluster 100 GB egress per month
Commitment
Self-service No sales interaction required.

Cluster SKUs

Primary Pricing

Base self-service databases are billed by cluster SKU. Representative arm64 configurations in AWS us-east-1 are shown; other architectures and regions vary.

InstanceResourcesPrice
PS-5 (single-node) Non-HA development configuration512 MB RAM / 1/16 vCPU$5 / month
PS-320 (3-node HA)32 GB RAM / 4 vCPU$570 / month
PS-2560 (3-node HA)256 GB RAM / 32 vCPU$4,529 / month

Representative sizes. See official pricing for all available options.

Cluster Usage Additional Usage Cost

Storage, egress, and backups are billed in addition to cluster compute.

ResourceBilling UnitPrice
Included storagefirst 10 GB storage per cluster$0
Storage overageper GB-month$0.50
Included egressfirst 100 GB egress per month$0
Egress overageper GB$0.06
Backupsper GB-month$0.023

Enterprise Pricing

Custom pricing is available for single-tenant and managed deployments, larger SKUs, committed use, and bring-your-own-cloud options.

Billing Commitment

Self-service; No sales interaction required.

Infrastructure & Availability

Where workloads run, how deployment is scoped, and what underlying infrastructure the platform depends on.

Managed cloud

PlanetScale offers 19 self-service database regions across AWS and Google Cloud for its current Vitess and Postgres platform. Vitess read-only regions are deployment options within the same supported footprint rather than additional regions.

Deployment model

  • Managed cloud

Execution

  • Single Region
  • Multi Region

Deployment scope

  • Regional

Infrastructure providers

  • Amazon Web Services
  • Google Cloud Platform

Available regions (19)

LocationInfrastructureRegion ID
North America 8 regions
Montreal AWS ca-central-1; current PlanetScale self-service region.Amazon Web Servicesaws-ca-central-1
Northern Virginia AWS us-east-1; current PlanetScale self-service region.Amazon Web Servicesus-east
Ohio AWS us-east-2; current PlanetScale self-service region and default for new databases.Amazon Web Servicesaws-us-east-2
Oregon AWS us-west-2; current PlanetScale self-service region.Amazon Web Servicesus-west
Council Bluffs, Iowa GCP us-central1; current PlanetScale self-service region.Google Cloud Platformgcp-us-central1
Ashburn, Virginia GCP us-east4; current PlanetScale self-service region.Google Cloud Platformgcp-us-east4
Montréal, Québec, Canada GCP northamerica-northeast1; current PlanetScale self-service region.Google Cloud Platformgcp-northamerica-northeast1
Moncks Corner, South Carolina GCP us-east1; current PlanetScale self-service region.Google Cloud Platformgcp-us-east1
Latin America 1 region
Sao Paulo AWS sa-east-1; current PlanetScale self-service region.Amazon Web Servicesaws-sa-east-1
Europe 5 regions
Frankfurt AWS eu-central-1; current PlanetScale self-service region.Amazon Web Serviceseu-central
Dublin AWS eu-west-1; current PlanetScale self-service region.Amazon Web Serviceseu-west
London AWS eu-west-2; current PlanetScale self-service region.Amazon Web Servicesaws-eu-west-2
St Ghislain, Belgium GCP europe-west1; current PlanetScale self-service region.Google Cloud Platformgcp-europe-west1
Eemshaven, Netherlands GCP europe-west4; current PlanetScale self-service region.Google Cloud Platformgcp-europe-west4
Asia Pacific 5 regions
Tokyo AWS ap-northeast-1; current PlanetScale self-service region.Amazon Web Servicesap-northeast
Mumbai AWS ap-south-1; current PlanetScale self-service region.Amazon Web Servicesap-south
Singapore AWS ap-southeast-1; current PlanetScale self-service region.Amazon Web Servicesap-southeast
Sydney AWS ap-southeast-2; current PlanetScale self-service region.Amazon Web Servicesaws-ap-southeast-2
Seoul, South Korea GCP asia-northeast3; current PlanetScale self-service region.Google Cloud Platformgcp-asia-northeast3

Managed cloud source

Managed BYOC

PlanetScale Managed runs databases inside customer-owned AWS or Google Cloud accounts while PlanetScale operates the service. Its eligible deployment locations are separate from the public self-service region inventory.

Deployment model

  • Managed BYOC

Infrastructure providers

  • Amazon Web Services
  • Google Cloud Platform

Managed BYOC source

Availability reviewed

Security & Compliance

Security Controls

Encryption at Rest
All plans
Encryption in Transit
TLS database connections All plans
Private Networking
Private database connectivity Deployment support applies
IP Allow List
Database connections
Multi-Factor Authentication (MFA)
TOTP PlanetScale accounts
Single Sign-On
SAML Base add-on; included with Enterprise
Audit Logging
Organization actions and authentication security history Security history retained six months

Audits & Certifications

SOC Reports
SOC 1 Type II and SOC 2 Type II PlanetScale managed service
PCI DSS
PCI DSS 4.0, Level 1 Service Provider PlanetScale managed service

Compliance

HIPAA
Eligible use Qualifying customers; signed BAA and customer safeguards required

FAQ

What happened to PlanetScale's free Hobby plan?
PlanetScale retired its free Hobby plan on April 8, 2024. Databases that were not upgraded were put into sleep mode, with temporary 24-hour wake periods available to retrieve data.
Is PlanetScale PostgreSQL or MySQL?
Both. PlanetScale offers PostgreSQL clusters and Vitess clusters, with Vitess providing MySQL compatibility. The two products have different features and workflows.
How much does PlanetScale cost?
PlanetScale self-service database compute starts at $5 per month for the representative PS-5 single-node configuration. Larger and highly available cluster sizes cost more, while storage, egress, and backups are billed separately.
How much does storage and egress cost on PlanetScale?
PlanetScale includes the first 10 GB of storage per cluster and first 100 GB of egress per month. Additional storage is $0.50 per GB-month, additional egress is $0.06 per GB, and backups are $0.023 per GB-month.
What PlanetScale cluster sizes are available?
Available cluster sizes depend on the organization and whether the database uses Vitess or PostgreSQL. PlanetScale provides an organization-level API endpoint that returns the currently available cluster-size SKUs, optionally with pricing rates, rather than relying on one universal fixed size table.

Explore

Explore more runtime platforms

Alternatives to PlanetScale