“A joy to work with. Branching, schema changes, and zero-downtime deploys make PlanetScale perfect for our evolving data models. Developer-friendly + production-safe = rare combo.”
DatabaseMaker says so +1 · source ↗
PlanetScale
Managed MySQL (Vitess) and Postgres built for scale, with branching and non-blocking schema changes.
29 makers' products we track use PlanetScale. For database it's 8th most chosen of 23 options: 29 of the 1,263 makers' products we know the database of (2%). Among the 397 launched in 2026, 3% chose it, against 3% of those launched in 2024 or earlier. 9 open-source projects also declare it in their code. What makers like most: Database branching, deploy requests and zero-downtime schema changes let teams change data models as fast as code. Their most common complaint: Newer features like Neki sharding and TIN search are proprietary and cloud-only, raising vendor lock-in worries. On GitHub, 0 public pull requests moved projects to PlanetScale from tools we list, and 7 moved them away.
Profile checked
Works with AI agents:llms.txtHow makers use PlanetScale
Makers' products we track use PlanetScale for database (29), most often alongside Vercel (59%), Next.js (41%), Resend (38%).
What PlanetScale is used for
PlanetScale vs the alternatives makers chose
For database, 29 of the 1,263 makers' products we know the choice of picked PlanetScale (2%), behind Supabase (45%). Among those launched in 2026 it's 3%.
| Option | Makers' products | 2026 launches | Free for | At 10,000 users | Open source | |
|---|---|---|---|---|---|---|
| 573 45% | 63% | ~500 users | $25/mo · Pro | Yes | Compare → | |
| 187 15% | 9% | ~2,000 users | $9.66/mo · Blaze (pay as you go) | No | ||
| 128 10% | 5% | ~500 users | $58/mo · Atlas Dedicated M10 | No | ||
| 98 8% | 1% | — | — | Yes | ||
| 96 8% | 11% | None | $22/mo · Launch | Yes | Compare → | |
| 50 4% | 7% | ~630 users | $29/mo · Professional | Yes | Compare → | |
| 29 2% | 3% | None | $7.40/mo · Postgres PS-5 (single node) | No |
For database: how many of the 1,263 makers' products we know the database of chose each option, and the share among the 397 launched in 2026, since a tool that came first has products from every year, and what each costs at 10,000 users.
Costs are the cheapest plan that fits, from each vendor's pricing page, at the usage our stack planner assumes for a product with that many users. Free for: the users its cheapest plan a business can use stays free for.
Often paired with
Share of the 29 makers' products on PlanetScale that show this choice.When to use PlanetScale, and when not
Something else fits better if
- You want the database, auth and file storage in one project, and plain SQL you can take elsewhere: Supabase.
- You're building a live, collaborative app entirely in TypeScript: Convex.
- Your traffic is bursty or you run many preview deploys, and idle hours shouldn't cost much: Neon.
- You already run your own server and want a flat monthly cost: PostgreSQL.
PlanetScale is a managed relational database service with three engines: Vitess (MySQL-compatible and horizontally sharded), plain Postgres, and Neki, its newer sharded Postgres. It is aimed at teams that want a production database with high availability and safe schema changes without running the clusters themselves.
More about PlanetScale
Every database is a set of branches. Production is a branch, and you create development branches to try schema changes. On Vitess, you open a "deploy request" that is checked for conflicts, reviewed like a pull request, applied as an online migration without locking tables, and can be reverted without losing writes made in the meantime. Each cluster has one primary and two replicas by default, with automatic failover and built-in connection pooling (PgBouncer on Postgres). You connect with standard MySQL or Postgres drivers, or with a serverless driver that runs over HTTP.
What matters for a small team: zero-downtime imports from an existing MySQL database, pg_dump or logical-replication paths from Postgres hosts such as RDS, Neon and Supabase, query insights, automatic backups, and an optional "Metal" tier on locally attached NVMe drives. Databases run in AWS and Google Cloud regions across North America, South America, Europe and Asia Pacific; there is no self-hosted edition.
Limits: the Vitess engine does not support stored procedures, triggers, events, LOCK TABLES or direct DDL on protected production branches, and it requires a unique key on every table. Deploy requests exist only on Vitess, and a branch's region cannot be changed after creation.
How PlanetScale itself is built
11 tools, from its own code, website and Product Hunt page.
PlanetScale pros and cons
What makers like most: Database branching, deploy requests and zero-downtime schema changes let teams change data models as fast as code. Their most common complaint: Newer features like Neki sharding and TIN search are proprietary and cloud-only, raising vendor lock-in worries.
Pros
- Database branching, deploy requests and zero-downtime schema changes let teams change data models as fast as code. PHHN
- It stays fast and reliable from launch to billions of rows, often with a single engineer running it. PHPH 2HN
- Vitess-based sharding gives battle-tested write scaling that the big clouds' managed databases do not offer in the same package. HNHN 2HN 3
- Support is prompt, sometimes straight from the founder. PH
Cons and watch-outs
- Newer features like Neki sharding and TIN search are proprietary and cloud-only, raising vendor lock-in worries. HNHN 2HN 3HN 4
- Dropping the free tier forced hobby projects to move elsewhere and cost it goodwill with indie developers. HNHN 2
- Postgres databases cannot yet get in-place major version upgrades. HN
Themes that recur in makers' words and Hacker News comments, each linked to what it summarises, with how Product Hunt tags its reviews.
4.8★ from 28 reviews on Product Hunt ↗What Hacker News says about PlanetScale
On Hacker News, 32% of comments about PlanetScale recommend it and 12% criticize it: net praise +20%, 4th best liked of 16 tools HN discusses for database.
By year
| Year | Comments choosing it, per month | Net praise |
|---|---|---|
| 2023 | 1.3 | +37% |
| 2024 | 0.3 | −7% |
| 2025 | 1.0 | +17% |
| 2026 (8 mo) | 0.5 | +18% |
In their words
- “I love the work planetscale does on keeping this type of content accurate yet accessible.” HN, Feb 2026
- “Moving to PlanetScale added a 9 to our uptime.” HN, Sep 2025
- “The work needed to switch from PlanetScale ultimately meant I just canned the project.” HN, Oct 2025
Hacker News comments January 2023 to August 2026 that name PlanetScale in a sentence like "I use" or "we moved to", Claude read a sample of 77 and the counts scale it to all of them; net praise is comments recommending it minus comments criticizing it, as a share of all comments about it. How it's counted, and how HN compares with makers.
Reliability and open issues
PlanetScale's status page posted 5 incidents in the last 90 days, 4 major.
Incidents on its status page
5 in the last 90 days, 4 major · 25+ in the last year- major AWS us-east-1 connectivity failures Oct 2026
- minor Branch creation delays in GCP europe-west-1 Sep 2026
- major Connectivity issues with Vitess databases in GCP Sep 2026
Who switches
More projects move away from PlanetScale: 0 pull requests in, 7 out; the most leave for Neon.
PlanetScale → Neon4 PRs
- Migrate from PlanetScale MySQL to Neon Postgresuptonm/budget · 2026-07-18
- Migration db - from planetscale to neon and changing the orm to drizzle instead of using prismagudbhav/emoji-community-chat · 2026-05-30
- Migrate infra database provisioning from PlanetScale to Neoncill-i-am/ceird · 2026-05-16
- Finalise Planetscale to Neon DB Migrationarvindravi/arvind · 2024-11-25
PlanetScale → PostgreSQL3 PRs
- db: migrate from MySQL/PlanetScale-serverless to Postgresaryan-shubh/siliconworm · 2026-06-03
- Migrate database integration from PlanetScale to Postgresebanux/dub · 2025-11-12
- fix(planetscale): add default successor to postgres rolesalchemy-run/alchemy-async · 2025-10-30
Public pull requests on GitHub since Oct 2024 whose title says "X to Y" — real code changes moving a project from one tool to another, by developers in general.
Who uses it
29 makers' products, each linked to the source that shows it, and 9 open-source projects that declare it in their code. The best known on Product Hunt: Graphy (2,389 followers), OpenSEO (1,649 followers), papermark (1,541 followers), Stackfix (1,394 followers), Campsite (1,156 followers). 1 of the makers' products is gone now (domain lapsed, up for sale or taken down); it chose PlanetScale while live.
“We run on PlanetScale and they're simply the best database provider out there. 0 to billions of devices with a single engineer and only a few bumps along the way!”
DatabaseMaker says so +1 · source ↗“If you want really fast and reliable database technology this is the way to go. Not only does it allow us to have super fast performance of our service, their analytics help us make it even better.”
DatabaseMaker says so +1 · source ↗“Super easy to setup! Really appreciate it”
DatabaseMaker says so · source ↗“Absolutely GOATED database provider. Massively improved our performance just by migrating last year.”
DatabaseMaker says so · source ↗“Planetscale has help us scale our database to over a billion rows! We love tier amazing support.”
DatabaseMaker says so · source ↗“PlanetScale has completely transformed how we manage our database. Its scalable, serverless architecture makes it easy to handle large volumes of data without the hassle of manual scaling or infrastructure management. We can deploy changes seamlessly, and its compatibility with MySQL makes it familiar yet incredibly powerful. PlanetScale’s branching and data versioning features make managing database schema changes painless and safe. With its high availability and fast performance, we can focus on building features instead of worrying about database management.”
DatabaseMaker says so · source ↗“We use PlanetScale as our primary database because of their brilliant reliability and speed.”
DatabaseMaker says so · source ↗“Thanks to PlanetScale for powering our databases! Their MySQL platform has simplified scaling.”
DatabaseMaker says so · source ↗“PlanetScale help us focus on building a great product and not worry about the database. Super reliable and easy to use.”
DatabaseMaker says so · source ↗“I've spent way too much time relying on bad / extortionate DB providers that go down far too often. PlanetScale has been the exact opposite experience. Transparent and clear pricing, super fricking fast, and dead simple to setup. Few cases where I've had questions founder has personally responded on X. No complaints, will be my DB provider of choice going forward.”
DatabaseMaker says so · source ↗“Helps us scale to handle large amounts of data and concurrent users.”
DatabaseMaker says so · source ↗“PlanetScale has allowed us to scale our database usage to hundreds of thousands of daily requests.”
DatabaseMaker says so · source ↗“Branching workflows for the database and zero-downtime schema changes let us move as fast on data as we do on code. Rock-solid as we scale.”
DatabaseMaker says so · source ↗“PlanetScale's incredibly intuitive MySQL experience has made launching new features seamless.”
DatabaseMaker says so · source ↗“PlanetScale is an amazing DB and we recommend it over alternatives like Supabase.”
DatabaseMaker says so · source ↗“They do great engineering + the integration with Cloudflare is great.”
DatabaseMaker says so · source ↗“PlanetScale gives Banger reliable, scalable database infrastructure, so we can focus on building the customer email workflows our users need.”
DatabaseMaker says so · source ↗“Balance uses PlanetScale to securely store user's financial data. Battle tested at companies like YouTube, Gusto, and Slack, I'm confident that our users' most sensitive information is in the best possible hands.”
DatabaseMaker says so · source ↗“As a NextJS and Rails app, Planetscale is the backbone of Campsite. Our database is incredibly fast, secure, and easy to manage. Deploy Requests are GOATed.”
DatabaseMaker says so · source ↗“Planetscale offers highly available database that natively integrates with Cloudflare and an affordable default.”
DatabaseMaker says so · source ↗“PlanetScale is the most developer-friendly database we’ve used. Its serverless architecture means you get scalability without the headaches. PlanetScale’s customer support has also helped us out a few times; they’ve been helpful and prompt.”
DatabaseMaker says so · source ↗“The valv platform is powered by planetscale as the best database provider on the market”
DatabaseMaker says so · source ↗None of these in makers' own words.
Open source: a project that declares PlanetScale as a dependency in its public code — verifiable, but not necessarily a live product.
Alternatives to PlanetScale
All alternatives by situation →Further reading
Questions makers ask about PlanetScale
Is PlanetScale good for production?
29 makers' products we track run on it, and 1 of them have since gone (the product, not necessarily because of PlanetScale). Its own status page posted 5 incidents in the last 90 days, 4 of them major; vendors decide what they post there, so this doesn't compare across tools. On GitHub, 0 public pull requests moved projects to PlanetScale from tools we list, and 7 moved them away. The watch-out makers raise most: Newer features like Neki sharding and TIN search are proprietary and cloud-only, raising vendor lock-in worries.
What is PlanetScale used for?
Managed MySQL (Vitess) and Postgres built for scale, with branching and non-blocking schema changes. Makers' products we track use it for database (29).
What are the pros and cons of PlanetScale?
Pros makers name: Database branching, deploy requests and zero-downtime schema changes let teams change data models as fast as code. It stays fast and reliable from launch to billions of rows, often with a single engineer running it. Vitess-based sharding gives battle-tested write scaling that the big clouds' managed databases do not offer in the same package. Cons: Newer features like Neki sharding and TIN search are proprietary and cloud-only, raising vendor lock-in worries. Dropping the free tier forced hobby projects to move elsewhere and cost it goodwill with indie developers. Postgres databases cannot yet get in-place major version upgrades.
What are the alternatives to PlanetScale?
For database, the other options makers' products we track chose most are Supabase (573), Firebase (187), MongoDB (128), PostgreSQL (98), Neon (96), Convex (50). Open source or self-hostable among them: Supabase, MongoDB, PostgreSQL, Neon, Convex. Each alternative, with the situation it fits, is on the PlanetScale alternatives page.
Is PlanetScale still popular with new products?
About as much as before: among the 397 makers' products launched in 2026 that made the database choice, 3% chose PlanetScale, against 3% of the 335 launched in 2024 or earlier.
How much does PlanetScale cost per month?
At 10,000 users, PlanetScale costs $7.40 a month on the cheapest plan that fits (Postgres PS-5 (single node)), from its pricing page.
Do developers switch to or away from PlanetScale?
On GitHub, 0 public pull requests moved projects to PlanetScale from tools we list; 7 moved them away, most to Neon (4), PostgreSQL (3).
Should I choose Vitess, Postgres or Neki?
PlanetScale suggests going by your experience; Vitess if you use MySQL or need horizontal sharding, Postgres if you use PostgreSQL and fit in a single cluster, and Neki for Postgres workloads that need sharding or online schema changes. Only Vitess has deploy requests, and Postgres is fully PostgreSQL compatible. source ↗
Which MySQL features are not supported?
PlanetScale's Vitess databases run MySQL 8 but do not support stored procedures, functions, triggers or events, LOCK TABLES, LOAD DATA INFILE, or CREATE DATABASE. Only InnoDB is supported, every table needs a unique non-null key, and binlog replication to external databases is not available. source ↗
Can I import an existing MySQL database without downtime?
Yes. Using the pscale CLI, you can import an internet-accessible MySQL 5.6, 5.7 or 8.0 database into Vitess with no downtime; the source needs binlog settings and a user with replication privileges. source ↗
How do I move from RDS, Neon or Supabase to PlanetScale Postgres?
Options include pg_dump and pg_restore for smaller databases that can accept downtime, WAL-based logical replication for minimal downtime, and published migration scripts. A migration assessment tool flags likely blockers first. source ↗
Is PlanetScale SOC 2 and HIPAA compliant?
On every plan, PlanetScale reports against SOC 1 Type 2 and SOC 2 Type 2 combined with the HIPAA Security Rule, signs BAAs with qualifying customers, encrypts data at rest and in transit, and covers all plans with a GDPR Data Processing Addendum. SSO is an add-on on the base plan. source ↗
Which regions can I deploy to?
Twelve AWS regions and seven Google Cloud regions across the Americas, Europe and Asia Pacific. A branch's region is fixed once created, so moving requires creating a new database or branch and migrating. source ↗
How do schema changes reach production on Vitess?
You make changes on a development branch and open a deploy request. PlanetScale checks it for problems such as missing unique keys or conflicts, teammates can approve it, and it then deploys without blocking traffic and can be reverted without losing data written since. source ↗
Is PlanetScale free?
No permanent free tier; paid use starts at $5/mo. source ↗
Is PlanetScale open source or self-hostable?
Not open source, and hosted only.
Can AI coding agents work with PlanetScale?
It serves an llms.txt docs index.
Who uses PlanetScale?
29 makers' products we track, each with a source, and 9 open-source projects declare it in their code. The best known of them on Product Hunt: Graphy (2,389 followers), OpenSEO (1,649 followers), papermark (1,541 followers), Stackfix (1,394 followers), Campsite (1,156 followers). source ↗