PlanetScale
@planetscale
The database platform built for scale. Postgres and Vitess/MySQL. Discord: Status:
You've probably never heard of sub-linear scaling. But if your Postgres database keeps taking on more traffic, you're headed there. You can scale by throwing bigger servers at it. But eventually, you need to scale beyond one machine. Neki gives you sharded Postgres from the team behind Vitess.
Mixedbread moved their control plane to PlanetScale and eliminated a significant amount of operational work: Their hottest control-plane queries now execute with sub-millisecond latency. Read more: https://www.mixedbread.com/blog/planetscale-case-study
Unlimited IOPS helped Sazabi cut a 5 figure bill to $500 on PlanetScale Metal. Sazabi is an AI native observability platform powering companies like Mastra, Weave, and Sandstone. Here's Sherwood Callaway telling @samlambert.com his migration story.
You can't manage what you can't measure. View detailed graphs for any available query metric in Insights: CPU time, blocks read/written, cache hit ratio, and more.
Sharding is how you scale relational databases. Bottlenecks like server write limits, data size, and slow backups mean eventually, your data should live on multiple servers. Learn how we do this at PlanetScale with Neki and Vitess in our latest blog.
At scale, you can only put off sharding for so long. YouTube scaled MySQL with Vitess, and now we're building the same for Postgres.
If you’re not careful, ingress (free) can become egress (not free). Double-check your agents work, they could quietly be costing you money.
82,000x database performance improvement? A single index can do that, and PlanetScale Insights can tell you where.
It's easy to introduce slow queries into your workload. Tracking them down should be easy too. PlanetScale Insights shows you which queries are slow and why. Combined with our MCP server, you can automate fixing them.
Most database benchmarks are bad. The problems are often subtle. Mismatched instances, cold caches, and coordinated omission all produce misleading results. Today, we’re publishing guidance on how to do it right, and updating our acceptable use policy to allow benchmarking.
pgvectorscale augments pgvector with StreamingDiskANN, making larger-than-RAM vector indexes achievable in Postgres. It also adds statistical binary quantization for improved search recall over regular quantization. PlanetScale supports both. Try them today.
Postgres RLS sounds great in theory: embedded access control right in the database. In practice, there's complexity in policy configuration, managing your attack surface, and performance implications. Our latest article takes a deep dive into RLS.
Postgres has three ways to isolate tenants: - Logical databases - Per-tenant schemas - Tenant ID in a shared schema Counterintuitively, the last is the best way to scale. Read about why in our latest article.
Sharding is the best way to scale a database. But how does it work? And what's the best way to ensure data and queries are evenly distributed? Our interactive article on database sharding teaches you how.
pgcopydb is the best way to migrate to PlanetScale Postgres. We've used it to move multi-TB databases at speeds over 2 TB/hr. PlanetScale's custom fork adds PG 17/18 support, better CDC, and resilient retry.
Postgres wasn't designed as a job queue, but many apps use it as one right alongside analytics, OLTP, and everything else. Our latest blog goes deep on what to be aware of when doing this and how the situation has improved for Postgres over time.
Traffic Control lets you limit how much of your Postgres compute resources any one workload can consume. You can warn, block, or do a mixture of both when queries exceed these limits.
🧢 Stop by the PlanetScale booth if you're at SREcon for PlanetScale credits, hats, stickers, and great conversations about databases.
Query Insights just got way more powerful. We now track tag metadata at the per-query level. This allows you to filter queries by tag, see per-tag performance breakdowns, and set resource budgets with Traffic Control.
Postgres has a problem: connections. PgBouncer is the solution, but it's not so simple. We've got the guide for how to optimize your connections for any database size.
The PlanetScale plugin for Cursor is a huge unlock for database productivity. Discover and apply schema recommendations, improve query performance, and work with your data in natural language.
PlanetScale is now in the Cursor plugin marketplace. Get our MCP + skills with just a few clicks.
The PlanetScale MCP server is now available as a Claude Connector. Add now to Claude Desktop or Claude Web to query your database, get performance insights, and generate organizational reports.
Quality of life improvement: new database list view in your dashboard.
Need Postgres connection pooling? PlanetScale has three PgBouncer options: - Local: co-located with the primary Postgres instance - Dedicated primary: runs on separate infrastructure, good for pooling + HA - Dedicated replica: pooling for your replica queries
Trillions of Postgres and MySQL transactions execute every day. They're at the heart of why relational databases are relied upon by the world's largest applications. Learn all about how they work in our latest article.
"Systems were going down every day." Intercom's Ryan Sherlock walks through their entire database journey: MySQL, Aurora, ProxySQL, and why they ultimately chose PlanetScale.
PlanetScale Postgres + @drizzle.team ORM 🤝 New connection guide is live orm.drizzle.team/docs/connect...
Looking for last minute gift ideas for $50 or less? Give the gift of blazing fast NVMe drives. It's been a busy week of shipping ⬇️