Also onPaydays(Pay schedule)
PlanetScale now supports authentication to its API using OpenID Connect (OIDC) from GitHub Actions and Depot CI. This allows workflows to use short-lived service tokens instead of long-lived credentials.
We've added emergency backups to Vitess databases. An emergency backup will copy data directly from your running database instead of starting from the previous backup. This ensures you can get a fresh backup right away, even when regular backups are failing. On production branches, you can choose to copy from the primary or from a replica.
PlanetScale now provides maintenance windows for Postgres databases, allowing users to schedule restarts for image updates and routine maintenance. Users can reschedule these windows via the dashboard or API.
PlanetScale now sends email notifications for Postgres and Neki databases when higher than usual public network egress is detected.
PlanetScale service tokens and audit logs now include the IP address, location, and network operator information for improved visibility.
PlanetScale has expanded its CLI and API to support additional Vitess operations, including Materialize and VDiff.
PlanetScale now displays Materialize workflows in the Vitess branch dashboard, allowing users to view stream states and replication lag.
Users can now view, cancel, or terminate live connections to Neki routers via the dashboard or CLI, allowing for better management of active queries and sessions.
We've updated the Heroku Migrator so Heroku Postgres migrations are faster and cover more databases. The initial copy will now drop secondary indexes on PlanetScale and rebuild them after the data lands. This keeps a single bad index from restarting a multi-hour copy.
We've added Metal sizes M-10 through M-160 for Neki on AWS. You can now run Neki on the same locally attached NVMe sizes already available for Postgres. On these sizes, you'll pick storage capacity separately from vCPU and memory. The capacity stays fixed after you select it. Read more
You can now enable huge pages for your Postgres and Neki databases on supported cluster sizes. Huge pages reduce the memory and CPU overhead of managing PostgreSQL's shared memory. Set huge_pages to on in the Parameters tab on the Clusters page for Postgres, or in a configuration profile's Parameters tab for Neki. Applying this change requires a restart.
The PlanetScale Terraform provider v1.13.0 adds parameter management to planetscale_neki_router . You can configure router settings in Terraform and read them through the router data source.
We've added Microsoft Azure as a cloud provider. You can now create PlanetScale Postgres and Neki databases in Azure regions, alongside the AWS and Google Cloud regions we already support. Vitess databases are not currently available on Azure. To get started, choose Azure as the cloud provider when creating a new database, then pick a region.
You can now opt a single deploy request into aggressive cutover from the CLI and API. pscale deploy-request create --aggressive-cutover pscale deploy-request update --aggressive-cutover pscale deploy-request update --aggressive-cutover=false You can change this any time before you deploy the schema change.
The PlanetScale MCP server can now check your database's metrics. planetscale_get_branch_metrics pulls CPU, memory, disk, replication lag, and connections into your AI assistant, so you can see those numbers without leaving your editor. It works for Vitess, Postgres, and Neki.
Organization administrators can now limit the database query access members grant to MCP clients. In organization settings, MCP query access can be set to no query access, read-only queries, or read and write queries. This applies the next time someone authorizes an MCP client.
PlanetScale Postgres now supports independently configurable dedicated read replicas. Create one or more dedicated read replicas in the primary region or another region from the same cloud provider. Configure the cluster size, replica count, storage, and supported Postgres parameters independently from the primary cluster.
We've added pscale keyspace parameters to the CLI. You can now view and change the VTTablet and MySQL parameters of a Vitess keyspace from your terminal. pscale keyspace parameters set mydb main mydb --org acme \ --parameters vttablet.vreplication-parallel-insert-workers=4 \ --parameters mysqld.wait_timeout=600 pscale keyspace parameters list shows each...
We've updated organization invitations so you can pick a member's role before you send the invite. New members will now join with the role you selected instead of defaulting to Organization Member. This means you no longer have to wait for them to accept and then change their role on the Members page. Learn more about access control
TIN 1.0.4 is now available for PlanetScale Postgres. Word stemming. Create a TIN index with WITH (stemmer = 'en') to match inflected words as the same term. A query for runs also matches run and running . Stemming is optional, per index, and supports 18 Snowball languages. See index options . Score tie-breaking.
You can now import an existing MySQL database into PlanetScale Vitess with no downtime from the pscale CLI. Connect your database to a production branch as an external keyspace , then move its tables into PlanetScale with a Vitess MoveTables workflow.
We've added two Prometheus metrics for container restarts and deprecated planetscale_pods_container_restarts_total . The old counter had a bug. Its planetscale_restart_reason label described only the container's most recent termination, not the restarts being counted.
You can now attach an existing MySQL database as an external keyspace on a Vitess production branch. PlanetScale runs an external tablet against that source so you can query it through Vitess without importing the data first.
We've just released a second full-text search extension for Postgres, called Lead . This one's open source, so you can run it in your CI, dev, and staging environments, even fully offline. It has the same features as TIN, the full-featured, highly performant full-text search extension we announced yesterday .
You can now control how many shards in a Vitess keyspace PlanetScale updates concurrently during a configuration rollout. Keyspaces use a default concurrency of 1. Set a value from 1 to 32 to shorten rollouts for keyspaces with many shards while choosing how many shards change at the same time.
You can now turn a Vitess keyspace's tablet throttler on or off, and set the replication lag threshold. When the throttler is enabled, schema migrations and VReplication workflows pause while replication lag is above the threshold. The setting applies across all shards in the keyspace.
Neki, our sharded Postgres product, is now available in platform preview. Neki is horizontally sharded Postgres built to solve the problems that come with large scale. Every shard is real Postgres, and Neki handles routing, resharding, online schema changes, and version upgrades, all with a single connection string.
PlanetScale Managed has been issued an updated PCI Attestation of Compliance (AoC) and Report on Compliance (RoC), re-certifying our compliance with the PCI Data Security Standard v4.0.1 as a Level 1 Service Provider . Enterprise customers may obtain the latest copies of our PCI attestation and other security documentation by visiting our trust center .
You can now set an Authorization header on webhooks. Pass the full value, scheme included, like Bearer . PlanetScale sends it unchanged with every delivery. Use it when the receiving service needs a token. That includes webhook-triggered Cursor and Devin automations. Set it in the dashboard or with --authorization-header on the CLI. Read more
Organization administrators can now enable and manage SSO from the CLI with pscale org sso . Read more
We've added backup.succeeded and backup.failed webhook events. You'll get notified when a backup finishes, whether it worked or not. These work for both Vitess and Postgres databases. View all webhook events
The PlanetScale MCP server can now read query tags from Insights, so you can ask which part of your application is behind your database load instead of only which query.
MySQL and Postgres databases on Vitess and Metal.
| Release-notes page | Site | Feed |
|---|---|---|
| Automating our changelog with Cursor commands planetscale.com | planetscale.com | None |
| Changelog planetscale.com | planetscale.com | None |
| Create and resize external Vitess keyspaces planetscale.com | planetscale.com | None |
Releasesby Glyph