PlanetScale

active

by PlanetScale, Inc. · since 2021 · also known as PlanetScale Postgres, PlanetScale Vitess, PlanetScale Metal

Performance-focused managed MySQL (Vitess) and Postgres, with NVMe-backed Metal clusters and branching.

relationaldocumentvectormanaged serviceproprietarygrowing

Overview

PlanetScale is a managed database company built by core Vitess maintainers. It started with Vitess-based MySQL, adding schema branches and deploy requests for safe, non-blocking migrations, and in 2025 launched PlanetScale Postgres, followed by Neki, its own sharding layer for Postgres. Metal clusters run on local NVMe drives instead of network storage, trading elastic disks for much lower and steadier latency. The hobby free tier is gone; the entry point is now a $5 single-node Postgres, and production clusters are priced per primary-plus-two-replicas. Choose it when you care about tail latency, zero-downtime schema changes and a credible path to sharding, rather than scale-to-zero pricing.

Strengths & trade-offs

Strengths

  • +Metal clusters on local NVMe give low, predictable query latency
  • +Schema branches and deploy requests make migrations reviewable and non-blocking
  • +Battle-tested Vitess sharding for MySQL at very large scale
  • +Both MySQL and Postgres under one control plane
  • +Query Insights surfaces slow queries and index recommendations

Trade-offs

  • −No free tier since 2024; even hobby use is paid
  • −Vitess-based MySQL restricts some features (e.g. foreign keys were long unsupported)
  • −No scale-to-zero; you pay for provisioned clusters
  • −Postgres sharding (Neki) is new and less proven than Vitess

Great for

  • +High-traffic SaaS backends sensitive to tail latency
  • +Teams that want safe, reviewable schema changes in CI
  • +Outgrowing a single MySQL primary
  • +Migrating from RDS/Aurora to faster NVMe-backed Postgres

Think twice for

  • −Free hobby projects
  • −Spiky workloads that benefit from scale-to-zero
  • −Self-hosted or on-premises requirements

Capabilities

Native or official first-party support · 16 of 25 tracked

✓Transactions
✓Joins
✓Secondary indexes
✓Full-text search
✓Vector search
✓JSON
✓Change data capture
✓Triggers
✓Stored procedures
✓Materialized views
✓Durable persistence
✓Compression
✓Encryption at rest
✓Role-based access
✓Branching
✓Online schema changes
–Geospatial
–TTL / expiry
–Pub/Sub
–Columnar storage
–In-memory
–Time travel
–Streaming ingest
–Offline sync
–Runs in WebAssembly

Scale & consistency

Comfortable data size
Massive · Multi-PB
Horizontal scaling
Native
Multi-region
Read replicas
Transactions
Full ACID
Consistency
Strong, Eventual
Schema
Strict
Architecture
Primary replica, Distributed
Query languages
SQL, PL/pgSQL

Vitess databases shard horizontally today; Postgres scales vertically with replicas, with Neki providing sharding; cross-region read replicas available.

Deployment

Self-hosted Vendor-managed cloud Serverless Embedded Edge Kubernetes operator

available on · AWS · Google Cloud

Ecosystem

compatible withMySQL, PostgreSQL
apis & protocolsMySQL wire protocol, PostgreSQL wire protocol, HTTP serverless driver
client languagesJavaScript, Go, Python, Ruby, PHP, Java, Rust
used byIntercom, Cash App

Alternatives to PlanetScale

Compare all→
VitessRelational21.2

CNCF-graduated sharding and clustering layer that makes a fleet of MySQL servers look like one database.

planetscale vs vitess →
NeonRelational30.4

Serverless Postgres with copy-on-write branching and scale-to-zero, now part of Databricks.

planetscale vs neon →
SupabaseRelational54.3

Open-source Postgres backend platform: database, auth, storage, realtime and edge functions in one project.

planetscale vs supabase →
Amazon AuroraRelational24.9

AWS's MySQL- and PostgreSQL-compatible engine on a shared, six-way replicated storage layer.

planetscale vs amazon-aurora →
TiDBRelational35.9

MySQL-compatible distributed SQL with a row store for OLTP and a columnar replica for real-time analytics.

planetscale vs tidb →
Crunchy BridgeRelational0.2

Crunchy Data's developer-friendly managed Postgres across AWS, GCP and Azure, now owned by Snowflake.

planetscale vs crunchy-bridge →

PlanetScale FAQ

What is PlanetScale?

PlanetScale is a relational database by PlanetScale, Inc., first released in 2021. PlanetScale is a managed database company built by core Vitess maintainers. It started with Vitess-based MySQL, adding schema branches and deploy requests for safe, non-blocking migrations, and in 2025 launched PlanetScale Postgres, followed by Neki, its own sharding layer for Postgres. Metal clusters run on local NVMe drives instead of network storage, trading elastic disks for much lower and steadier latency. The hobby free tier is gone; the entry point is now a $5 single-node Postgres, and production clusters are priced per primary-plus-two-replicas. Choose it when you care about tail latency, zero-downtime schema changes and a credible path to sharding, rather than scale-to-zero pricing.

Is PlanetScale open source?

No. PlanetScale is proprietary, closed-source software.

Does PlanetScale support ACID transactions?

Yes. PlanetScale supports full ACID transactions, with strong, eventual consistency.

Does PlanetScale scale horizontally?

PlanetScale scales horizontally out of the box, with built-in sharding or partitioning. It is comfortable at massive scale (Multi-PB). It supports cross-region read replicas.

How can I run PlanetScale?

You can use the vendor's managed cloud. It is available on AWS and Google Cloud.

What is PlanetScale best for?

PlanetScale is a strong fit for high-traffic SaaS backends sensitive to tail latency; teams that want safe, reviewable schema changes in CI; and outgrowing a single MySQL primary. Think twice for free hobby projects.

What are the best alternatives to PlanetScale?

Common alternatives to PlanetScale include Vitess, Neon, Supabase, Amazon Aurora and TiDB. The right choice depends on your workload, scale and hosting; WhichDB's smart match ranks them against your requirements.

How popular is PlanetScale?

PlanetScale ranks #118 of 844 databases on the WhichDB Score (25.7/100), and #38 among relational databases. The score combines public adoption signals such as package downloads, GitHub activity, job posts and developer discussion.