PlanetScale

Parameter listings now display required updates.

Parameter listings now include a Requires update column for Postgres branches and for Neki configuration profiles, admins, and sidecars, with JSON output adding a requires_update field so scripts can detect the requirement. Maintenance must be run on the branch or Neki configuration profile before changing such a parameter.

Parameter listings now include a Requires update column for Postgres branches and for Neki configuration profiles, admins, and sidecars, and JSON output includes a requires_update field so scripts can detect the requirement. When an update is required, maintenance must be run on the branch or profile before the parameter can be changed.

Terraform provider v1.13.0 adds parameter management to planetscale_neki_router, configurable in Terraform and readable through the router data source; configuring parameters resets omitted customer-configurable parameters to defaults. The planetscale_databases data source now filters by kind, and drift from locked Neki parameters is fixed.

The planetscale_neki_router resource now accepts a parameters block, though configuring it resets omitted customer-configurable parameters to their defaults, and the planetscale_databases data source supports filtering by kind. Postgres bouncer managers should upgrade before PgBouncer timeout parameters report their type as time instead of seconds, since earlier provider versions will fail to read bouncers; the release also stops persistent drift from locked Neki parameters.

Microsoft Azure is now available as a cloud provider, letting users create PlanetScale Postgres and Neki databases in Azure regions with the same features as other clouds, including high availability, branching, Query Insights, automated backups, and Metal clusters. Vitess databases are not currently available on Azure.

Deploy requests can now opt into Vitess aggressive cutover individually via the CLI and API using the --aggressive-cutover flag, changeable any time before the schema change is deployed. pscale deploy-request show and queue now display an aggressive cutover column.

Added per-deploy-request aggressive cutover. The refresh-schema command now waits for the schema snapshot and returns poll failures instead of a refresh timeout.

The PlanetScale MCP server can now check database metrics via the planetscale_get_branch_metrics tool, pulling CPU, memory, disk, replication lag, and connections into your AI assistant for Vitess, Postgres, and Neki branches. The default summary covers the last hour, with memory utilization including page cache reported alongside RSS and cache.

The CLI now supports Postgres extension toggle commands and VTGate parameter commands, and deploy requests can be retried for failed operations. Keyspace --max-storage and --storage accept human-readable sizes, and auth login messaging now describes expired and denied device logins in plain terms.

Vitess deploy requests now offer a retry option for partially failed migrations: instead of restarting the entire deploy, retry restarts the migration for only the failed tables while tables that already completed keep their existing progress. Available from the deploy request page and via pscale deploy-request retry .

Organization administrators can set MCP query access in organization settings to no query access, read-only, or read and write. The limit applies the next time someone authorizes an MCP client, and already-authorized clients keep their existing access.

PlanetScale Postgres now supports independently configurable dedicated read replicas, created in the primary region or another region from the same cloud provider with their own cluster size, replica count, storage, and Postgres parameters. They can be managed from the dashboard, API, CLI, or Terraform.

The new pscale keyspace parameters command lets you view and change VTTablet and MySQL parameters of a Vitess keyspace from the terminal. pscale keyspace parameters list shows current and default values, pscale keyspace parameters changes list tracks each change as it rolls out, and --reset restores a parameter to its default.

Two new Prometheus metrics track planned and emergency reparents, split by planetscale_reparent_result and planetscale_component labels. The planetscale_vtorc_recovery_type metric now holds recovery names like RecoverDeadPrimary instead of the previously documented planned and unplanned values, so existing queries filtering on those need updating; on Vitess 23 and later, failed and successful recovery counters carry keyspace and shard labels.

Organization invitations now let you choose a member's role before sending, so new members join with the selected role instead of defaulting to Organization Member.

branch.schema_recommendation webhooks now fire for Postgres databases when PlanetScale creates a new schema recommendation. A custom Authorization header, sent as the HTTP Authorization header on every delivery, can automatically start Cursor or Devin agents.

Databases now have a configurable limit on development branches, set from the database Settings page, defaulting to 100 and adjustable between 1 and 5,000. Creating past the cap requires deleting unused branches or raising the limit.