Query performance analysis with Insights
You can now use Insights to view time-series performance data on a per-query pattern basis.
Safely making database schema changes
How to prevent schema changes from being scary with database best practices and PlanetScale.
An update to our workflow: safe migrations
Learn about our latest update, safe migrations, and how it affects our branching workflow.
Announcing the PlanetScale GitHub Actions
Easily integrate common PlanetScale operations directly into your GitHub Actions Workflows.
Improvements to database branch pages
Learn about some of the latest enhancements we made to the Branching page in the PlanetScale dashboard.
Introducing the PlanetScale API and OAuth applications
Manage your databases programmatically with the PlanetScale API.
All of the tech PlanetScale replaces
PlanetScale is more than just a drop-in replacement for MySQL. Learn about everything PlanetScale can do for you.
Introducing PlanetScale Boost
Up to 1,000× faster queries in just a few clicks with our groundbreaking caching technology.
Debugging database errors with Insights
Learn about the new PlanetScale Insights database errors feature.
Gated Deployments: addressing the complexity of schema deployments at scale
We just introduced a new feature, Gated Deployments, that gives you more control over when your schema changes deploy.
You can now use PlanetScale in HTTP-only environments, like Cloudflare Workers, Vercel Edge Functions, and Netlify Edge Functions
How PlanetScale prevents MySQL downtime
Learn how PlanetScale protects against downtime due to human error, system immaturity, and app issues.
Safely dropping MySQL tables
Learn about how we’re making it safer to drop tables and easier to detect if they’re still in use.
Announcing Teams: An easier way to manage database administrator access
Learn how you can manage database access with Teams and Directory Sync
We now display PlanetScale system status directly in your dashboard
Learn about how we built the new in-app system status using Vercel edge functions and StatusPage
Getting started with the PlanetScale CLI
Learn how to quickly get up and running with the PlanetScale CLI.
Deploy requests now alert on potential unwanted changes
We’ve updated our Deploy Request UI to alert when a schema change could produce unintended changes
Introducing PlanetScale Insights: Advanced query monitoring
Insights gives you a faster way to debug and monitor your PlanetScale database queries
Extract, load, and transform your data with PlanetScale Connect
Use PlanetScale connect to easily perform ELT (Extract, Load, Transform) actions on your data to fulfill your application needs.
Introducing PlanetScale Portals: Read-only regions
Put your data where your users and applications are.
Revert a migration without losing data
Learn how PlanetScale lets you revert changes to your database after a migration with no downtime and zero data loss.
Bring your data to PlanetScale
PlanetScale now supports zero downtime data migrations from your existing MySQL Database
Introducing PlanetScale Managed Cloud
Deploy our database platform in your AWS account
Comparing AWS’s RDS and PlanetScale
PlanetScale draws customers from RDS due to better scalability and superior developer workflow
Optimizing SQL with Query Statistics
Check the performance of your SQL queries in real-time.
Automatically copy migration data in PlanetScale branches
Use PlanetScale branching with the database schema migration tools of your choice
Connect any MySQL client to PlanetScale using Connection Strings
Connect PlanetScale to any MySQL client with Connection Strings for a true serverless database experience.
PlanetScale on Vitess
At PlanetScale, our vision is to build a database developers love that can scale indefinitely. To do this, we knew we needed a database with a history of powering companies that deal with humongous amounts of data and traffic. That’s why we chose Vitess.
Non-Blocking Schema Changes
Non-blocking schema changes let you push updates to your database without fear of blocking your databases, locking individual tables, or slowing down production during schema migrations.