Data and AI releases

2,023 this month · 171 companies

More Vitess operations in the CLI and API

UpdateNot yet verified

PlanetScale has expanded its CLI and API to support additional Vitess operations, including Materialize and VDiff.

Developer tools

Read on planetscale.com

Also shipped Oct 24, 2026PlanetScale in October 2026 →

Qwen Code Release v0.26.1

This release adds opt-in daemon token persistence, manual context compression for managed sessions, and improved status line configuration. It also aligns OpenTUI input behavior and adds file recording reminders for the model.

Update
Source ↗

More from PlanetScaleEvery PlanetScale release →

Live connections for Neki

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.

Update
Source ↗

Postgres logical replication slots no longer need registration

We've removed the patroni.slots cluster parameter for Postgres logical replication. PlanetScale will now detect logical slots automatically, so you no longer need to add each slot name to your cluster configuration. Keep failover support enabled on your slots to preserve them during switchovers and failovers. Read more

Update
Source ↗

Configure disk scaling for Vitess keyspaces

You can now control how disks in a Vitess keyspace are sized, from the dashboard, the API, or the pscale CLI. Let disks grow automatically up to a storage limit, turn growth off, or shrink disks with more capacity than you need.

Update
Source ↗

Read-only replicas for Neki

We've added read-only replicas for Neki. You can now attach extra instances that copy from the primary and serve reads, without using the replicas that take over during failover. This keeps long-running work like analytics, reports, and exports off the instances that handle live traffic and failover.

Update
Source ↗

Metal M-10 to M-160 sizes for Neki

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

Update
Source ↗