Managed Postgres with scale-to-zero and branching for modern stacks.
This week: Object storage gets branch-aware semantics →
PlanetScale's CLI gained broad Postgres administration capabilities, including dedicated PgBouncer pooler management, IP restrictions, backup policies, and database settings updates, while Supabase's SDK improved trace propagation.
The new pscale pgbouncer command lets you create, list, resize, and delete dedicated PgBouncers for Postgres branches. Includes commands for resizing to a target (with size options like PGB_10 and PGB_20) and tracking, canceling, or completing resize operations.
The PlanetScale CLI now supports managing Postgres IP restrictions via pscale database ip-restriction, with list, create, show, update, and delete subcommands to control which CIDR ranges can reach a database.
New pscale backup policy commands let you create, list, show, update, and delete scheduled backup policies from the CLI, controlling backup frequency, schedule time, and retention.
The new pscale database update command lets you change database settings from the CLI, including name, default branch, and region restrictions.
The PlanetScale CLI added Postgres IP-restriction and backup-policy commands, while the Supabase CLI continued porting platform commands to native TypeScript and retried local database connections.
The pscale CLI now exports reports of Postgres authentication attempts, including client IP (captured even through poolers), credential used, database and branch, outcome, and failure details. Filter by IP/CIDR, branch, username, startup database, outcome, failure reason, and connection path, and export as CSV, JSON Lines, or Parquet with a manifest; Organization Administrator access is required.
The Supabase CLI moved shell completion and the local db reset recreate command to native TypeScript for better reliability, while also accepting offset timestamps in API requests.
Supabase's monthly update introduced Pipelines for streaming Postgres changes to BigQuery, ChatGPT sign-in, and Unified Logs, while PlanetScale added parallel schema deploys and Prisma opened its v8 release-candidate line.
Two deploy requests can run concurrently as long as they touch different tables, with dashboard and --strategy parallel CLI support. Watch for increased database load when running resource-intensive deploys; throttler settings adjust per request.
Neon unveiled branch-aware S3-compatible Object Storage, while Supabase's CLI and JS client shipped several fixes for realtime channels and local development lifecycle.
Neon2The Console sidebar now groups all branch-level backend services at the same level, with project-level items separated from branch-level items; branch Overview lists service status. AI Gateway adds Kimi K3, GLM-5.2, Inkling, and new Gemini/GPT models. Project-level permissions now support existing orgs, and the CLI adds api-keys and profile commands for scoped credentials and multi-account switching.
Neon Object Storage is now in beta, bringing S3-compatible object storage with branch-style semantics: buckets and objects inherit and fork alongside Postgres branches, with copy-on-write isolation and lineage-based versioning. Access works via standard S3 tools with Neon credentials, and neon.ts can provision buckets alongside the database.
PlanetScale CLI shipped region-scoped passwords, read-only dumps, and VTGate management on Vitess branches, while Supabase CLI fixed a path traversal issue and deprecated its pg-schema diff flag.
Case study on how CTO.new uses Turso with a database-per-project architecture to coordinate tens of thousands of AI agents.
The pscale CLI now lists Vitess read-only regions, creates passwords that always connect to a specific read-only region, and dumps from a chosen region instead of the primary. The new --read-only-region flag cannot be combined with --replica (or --rdonly on dumps); use --replica for traffic routed to the nearest replica across regions.
The pscale CLI now supports viewing and resizing VTGates on Vitess production branches, with show, resize, status, and cancel subcommands covering size, count, autoscaling, and CPU utilization target settings.