Insights graph update
PlanetScale Insights graphs just got an update! You can now zoom in on graphs for a more detailed look at branch metrics during a selected period.
For more information about Insights, see our Insights documentation.
The latest PlanetScale features and product launches.
PlanetScale Insights graphs just got an update! You can now zoom in on graphs for a more detailed look at branch metrics during a selected period.
For more information about Insights, see our Insights documentation.
Starting today, you can add an extra layer of security in connecting to your database by defining which IP addresses can connect to each database branch. Giving your organization the tools you need to operate your databases securely is a top priority, and IP restrictions, launching today in beta, are one additional way to provide an extra layer of security.
You can now view the details of your database’s passwords on a new page, including renaming a password, setting IP ranges that can connect to the database with the IP restrictions feature, copying and pasting pre-generated code, and more.
Find the page in your database’s “Settings” tab > “Passwords” section > select the password you want to see the details for.
Google Cloud Platform (GCP) regions in PlanetScale are now generally available in select regions, and read-only regions are now available in all supported GCP regions. As of today, there are 15 different regions across AWS and GCP where you can deploy your PlanetScale database.
For supported regions, see our regions documentation and see our read-only regions documentation to learn more about read-only regions in PlanetScale.
PlanetScale's latest SOC 2 Type II report covering the period of June 16, 2022 to June 15, 2023 is now available to customers. In addition to coverage over existing trust services criteria, the latest report includes additional controls mapped to the HIPAA Security Rule requirements.
To receive a copy of the report, please contact Support or visit our Trust Portal.
PlanetScale Boost is now available to all PlanetScale users in a public beta. PlanetScale Boost is a built-in database caching engine that requires no additional infrastructure, no cache invalidation, and up to 1000x better query performance for your boosted queries.
If you are a current PlanetScale user, check your email for a “Welcome to PlanetScale Boost” email with a special coupon code to try out Boost today for free for a limited time.
We’re replacing our ‘Teams’ plan with a new ‘Scaler Pro’ offering that combines the best of our current plans and enterprise offerings for companies of all sizes. These plans allow customers to select exactly the resources they need for their workloads. Don't worry; our existing Hobby, Scaler, and Enterprise plans aren't changing or increasing in price.
Scaler Pro databases are priced on a combination of resources (CPU and memory) and disk storage. Every database has a ‘cluster size’ encompassing the components that make up a PlanetScale database.
We just released an update to the PlanetScale UI database overview page. You now get a much more transparent view of what's happening under the hood with your PlanetScale database. This update surfaces important information about your database, such as:
For more information, see our Pulling back the curtain: the new database overview page blog post.
We have added a new Amazon Web Services (AWS) region. Now you can deploy databases on AWS in us-east-2 (Ohio).
For more information about our supported regions, see our documentation.
We have added a new Google Cloud Platform (GCP) region (in beta). Now you can deploy databases on GCP in Seoul, South Korea (gcp-asia-northeast3
)
For more information about limitations and supported regions, see our GCP documentation.
PlanetScale Insights now shows time-series metrics on a per-query pattern basis to help developers identify and troubleshoot problematic queries.
Read how the PlanetScale Engineering team used this feature to troubleshoot a query in our primary production database.
We’ve updated our status page to a new provider, enabling a streamlined incident workflow.
Historical availability events have been populated and the page is available at https://www.planetscalestatus.com.
We just released a new update to our workflow: safe migrations. Safe migrations protect your production database from direct DDL. As of today you can now disable this protection on any production branch.
Previously, protection from direct DDL was enabled by default on all production branches with no option to disable it. With this change, when you promote a branch to production, you will now see a toggle that asks if you want to enable safe migrations.
Read more about why we introduced safe migrations in our latest blog post, “An update to our workflow: safe migrations”.
We have added two new Google Cloud Platform (GCP) regions (in beta). Now you can deploy databases on GCP in Ashburn, Virginia (gcp-us-east4
) and Montréal, Québec, Canada (gcp-northamerica-northeast1
).
For more information about limitations and supported regions, see our GCP documentation.
Today, we are releasing a new way to manage your PlanetScale databases programmatically: The PlanetScale API.
The PlanetScale API (beta) opens up new ways to interact with PlanetScale through automation and other developer tools, like CI/CD, infrastructure as code, deployment tools, and application platforms.
In addition to the API, we are also launching OAuth applications in limited beta. OAuth applications alongside the PlanetScale API enable your users to interact with their PlanetScale databases from your application.
We are excited to announce that PlanetScale can now enter into Business Associate Agreements (BAAs) with customers deployed in the Single Tenant environment.
Contact us for more information about the PlanetScale Single-tenant offering and how to enter into a BAA with PlanetScale.
Please refer to the Security and compliance documentation for more details about PlanetScale and HIPAA.
Today, we’re releasing the PlanetScale Boost limited beta. PlanetScale Boost is a real-time query cache that automatically handles cache invalidation for you, without requiring substantial changes to your application code.
This feature is in limited beta. We will begin sending invites out soon.
Reserve your spot now by joining the PlanetScale Boost limited beta waitlist.
Today, we’re launching a checklist of commonly performed activities right after restoring a backup. Branches restored from a backup now come with a helpful guide on how to replace your existing default branch with the new branch.
We just introduced Google Cloud Provider (GCP) support for select GCP regions. GCP support is currently in beta, so some PlanetScale features are limited on branches and databases created in GCP regions.
For more information about limitations and supported regions, see our GCP documentation.
We’ve introduced a new addition to Insights, our in-dashboard query monitoring tool. You can now enable complete query collection, which allows you to see the raw query data in query deep dives and EXPLAIN
statements.
To enable complete query collection, an Organization Administrator must opt in on your database settings page.
We just released Gated Deployments, which gives you more control over your schema change deployments. Instead of automatically applying schema changes after you deploy, you can now choose to hold off on cutting over until you're ready.
To learn more, check out our Gated Deployments documentation or the Gated Deployments: Addressing the complexity of schema deployments at scale blog post.
Today, we’re launching a new view for managing backups for PlanetScale databases. Backups can now be viewed across all Production and Development databases on a single page.
We’ve added a new region: AWS eu-west-2 (London). You can now create databases and branches in this region in the dashboard using the region selector or with the PlanetScale CLI with region slug aws-eu-west-2
.
We just released the new PlanetScale serverless driver for JavaScript.
This Fetch API-compatible driver allows you to use PlanetScale with serverless and edge compute platforms that require HTTP connections, such as Cloudflare Workers, Vercel Edge Functions, and Netlify Edge Functions.
To use this driver, you must opt-in and accept beta terms to access the required PlanetScale connection strings. You can enroll your database by selecting the database in the PlanetScale dashboard, clicking "Settings", "Beta features", and clicking "Enroll" next to "PlanetScale serverless driver for JavaScript".
You can now easily manage database administrator access to one or multiple databases with Teams. Head to your Organization Settings page, click "Teams", and start adding members and databases.
Teams is available on all plans.
Today, we’re launching password roles for PlanetScale Databases. PlanetScale passwords can now be created with more granular control over which operations they can perform.
Today, we’re launching the Datadog integration. PlanetScale can push now metrics to Datadog to assist your team with understanding your database usage and performance.
Today, we’re introducing the next iteration of our Query Statistics tool: PlanetScale Insights.
Insights brings a new interactive graphical interface that charts query performance along side your Deploy Requests.
We’ve also added a new section that surfaces all queries run against your database in the last 24 hours. Each query includes metrics such as rows read, rows returned, time per query, and more.
Insights is currently in beta. You can try it out for yourself by clicking the “Insights” tab on your database page in the PlanetScale dashboard.
We’ve introduced a new feature called PlanetScale Connect that makes it easier to safely extract, load, and transform your data.
For this release, we’ve implemented an Airbyte connector as the pipeline between your PlanetScale data and the desired destination.
Connect is currently in beta. You can opt-in on your Organization Settings page under “Beta features”.
Today, we’re introducing PlanetScale Portals. With Portals, you can add read-only regions to your production database in any available region.
Portals is available on our Scaler, Teams, and Enterprise plans and will be billed based on storage and rows read. For more information, check out our Read-only regions documentation.
Portals is currently in beta. You can add a read-only region and try it out on any production branch in your organization.
Today, we’re introducing the Teams plan to better accomodate teams that require more resources and higher performance than the Scaler plan.
The new Teams plan includes:
We’ve also made some updates to existing plans. Our free Developer plan is now called Hobby and comes with 5 GB storage, 1 production branch, and 1 development branch.
Our Scaler plan has been updated to include SSO as an add-on option, 10 GB storage, 2 production branches, and 5 development branches.
We have added three more regions across the globe. Now you can deploy databases on AWS in Frankfurt (eu-central-1
), Sydney (ap-southeast-2
), and São Paulo (sa-east-1
).
We’ve introduced a new feature that allows you to revert a schema change with no data loss.
If you create and deploy a deploy request with a schema change that breaks your application, you can instantly revert the deployment with the click of a button. Additionally, you’ll retain any data that was added to your production database during the time between deployment and reverting.
This feature is in limited beta and you must accept beta terms and enroll your database to use it. For more information, see the Revert a schema change section of our Deploy requests documentation.
We’ve updated our Developer and Scaler plans to better accomodate user needs.
The free Developer plan remains at 10 GB of storage and 10 million writes, but now includes 1 billion reads.
The Scaler plan remains $29 per month per database with 25 GB of storage and 50 million writes, but now includes 100 billion reads. Additional storage and usage for the Scaler plan will be charged at $2.50 per additional GB, $1 per additional 1 billion rows read, and $1.50 per additional 1 million rows written.
We’ve made an update that may affect databases on the free Developer plan. Inactive databases may be put into sleep mode after 30 days of inactivity. All data will be backed up and stored, but you will not be able to connect to the database.
The following criteria is used to determine when a database is eligible to sleep:
Once all criteria is met, the database will enter sleep mode. You can wake a sleeping database at any time from the PlanetScale dashboard.
PlanetScale and Prisma have partnered to allow developers to create PlanetScale databases in the new Prisma Data Platform. You can have a starter database schema and a live PlanetScale database ready to accept thousands of new database connections with a few clicks.
The Prisma Data Platform provides you with application templates with Prisma data schemas, so you don’t even have to think about a data model to get started. Once set up, you can deploy to Vercel immediately or use the Prisma Data Explorer and Query Builder to explore your PlanetScale database.
The new PlanetScale Database Import feature makes it easy and painless to migrate your data from an existing internet accessible MySQL database into a PlanetScale database. With just a connection to your database, you can try out PlanetScale in front of your existing database and then import your data into PlanetScale. When you’re ready, switch traffic to your PlanetScale database without any downtime. Note: this feature is in limited beta.
Check out our latest blog post to learn more about how to import your data.
PlanetScale is now GA and ready for your production workloads. We launched our beta in May, and since then we’ve been hard at work to ensure that we offer the security, performance, and reliability you expect from a database platform. Read more about our journey to GA.
We’ve launched PlanetScale Managed Cloud, our enterprise offering for customers who need to host their data. We offer a unique managed experience — we deploy PlanetScale in our customer’s AWS account and manage it directly using a sub-account. This provides the full managed experience to our customers, while meeting their strict compliance requirements. Read more about PlanetScale Managed Cloud in this blog post.
To make it easier to fine-tune access control in your PlanetScale organization, we’ve added a new role: Database Administrator
.
The permissions for the Database Administrator
role are granted at the database level. With this role, you can give a member of your organization full access to a specific database (or several databases) without making them an Organization Administrator
.
We’ve updated our Scaler plan to make it a better option for our users. As a part of these changes, we’ll be including 500 million rows read, 50 million rows written, and 25 GB of storage in the plan and charging a monthly fee of $29. For usage and storage above the included amounts, we’ll be charging $1.50 per 10 million row reads, $1.50 per 1 million row writes, and $1.25 per GB of storage.
For larger organizations, we now offer a customizable, resource-based Enterprise plan that includes features like Single sign-on, unlimited database branches, premium support, and more.
To ensure we can provide the best quality service for our free Developer plan databases, we will be limiting the number of Developer plan databases to one per organization.
We’ve made a few changes to how branches work in PlanetScale. Now whenever you create a database, your main
branch will be a development branch by default, allowing you to start making changes to the schema instantaneously, without needing to use deploy requests. When you're done hacking around and ready to make your database production-ready, you can promote your branch to production, which enables high-availability and direct DDL protection (sorry Little Bobby Tables). Additionally, you can promote multiple branches if you so desire, so if you want to have a staging
database branch that’s also protected, we can do that for you!
Lastly, we’ve introduced the concept of a default branch. Before, main
was the default branch and that wasn’t able to be changed. But now, you can select whatever you want as the default branch. One thing to note, the first branch that gets promoted to production will become the default branch.
We’ve made it easier to manage your PlanetScale organizations by allowing users to set a default organization. Once set, users will land in the default organization every time they sign in.
To set a default organization, head over to your user settings and select your default organization from the drop down.
We’ve added a web console to make working with your PlanetScale database even easier. You can now run through the database branch lifecycle using just the website, no need to switch between apps to connect to your database branch and run commands.
The PlanetScale web console is an interactive interface for running MySQL queries and DDL (Create, Alter, & Delete) against your PlanetScale database branches.
We have added three new regions in Asia Pacific to PlanetScale. Now you can deploy databases in Mumbai, Tokyo, and Singapore.
Starting today, all PlanetScale database branches now track statistics about each SQL query that has executed against it without any overhead. This allows users to identify queries that are running too frequently, returning too large of a result set, or require an index to return results more quickly. You can read about how we’re using this feature to optimize queries in our latest blog post.
We’ve made it even easier to use a PlanetScale database with the framework of your choice. Now, you can automatically persist schema changes in your framework’s migration table.
Set up automatic migrations with your first deploy request by selecting the framework of your choice. If the framework you’re using isn’t listed, select “Other” and enter the name of the migration tracking table.
Once set up, you’ll never have to worry about keeping the framework’s migration table up to date. It will happen automatically.
We are excited to announce that we have achieved SOC 2 type II compliance. We take security very seriously at PlanetScale, and this is just one of the many measures we are taking to ensure the continuous security and integrity of data stored on our platform.
You can now use the tools you're familiar with to connect to PlanetScale databases, whether that’s with Rails, Python, Prisma, Laravel, or any other MySQL client. Connection strings are built for serverless scale and enable you to connect to other serverless computing platforms like AWS Lambda or Vercel.
Within PlanetScale, you can generate a new password and automatically get client code for many popular frameworks and languages for you to connect your PlanetScale database.
PlanetScale connection strings are built with security as a priority, so you can spend less time worrying if your database connections are secure. This includes strong passwords that are never stored in plain text, GitHub Secret Scanning, and native MySQL authentication support.
We’ve added two new regions US West (Oregon) and EU West (Dublin, Ireland), and we’ll be adding more regions in the future.
We have also added the ability to deploy branches near where you develop. Deploy your production branch near your users and develop on a branch in your region to avoid unnecessary latency.
Administrators now have access to an organization level Audit Log which tracks all user actions and events providing insight, transparency, and security for your databases.
Single Sign-On (SSO) is now available for Enterprise plans and as an add-on to the Scaler plan. SSO provides additional account security by allowing company administrators to require the use of an identity provider when logging into PlanetScale. Users only need to sign in once with a single set of credentials (i.e. password and email) to access all of their tools and applications.
Multi-Factor Authentication (MFA) prevents unauthorized access to your user account. MFA strengthens security by requiring two or more methods (i.e. authentication factors) to verify your identity. We strongly recommend enabling MFA for your account.
If you're authenticating via GitHub OAuth or SSO, MFA settings will not be displayed