Neon expands beyond Postgres as Supabase reworks its CLI core

Neon becomes a full-stack backend platform

The biggest story of the week came from Neon, which announced it is building a complete backend for apps and agents far beyond Postgres. Three new services are joining the platform alongside its branchable Postgres: Object Storage (S3-compatible and branches with your database), Compute (serverless compute deployed with your database), and an AI Gateway (model routing, logging, and cost controls). In a companion blog post, the company explained that the AI Gateway, powered by Databricks infrastructure, already handles over 125 trillion tokens monthly, and that the core Postgres team remains larger than ever with growth funded by expansion within Databricks.

The expansion didn't stop at announcements. The team also shared a architectural deep dive on resilience to cloud failures, detailing how agent workloads have strained control-plane operations and capacity, and what lessons are shaping the reliability roadmap. On the practical side, Neon published Neon Slop Fork, a fully functional dashboard rebuild created by a coding agent using only the public Neon API and TypeScript SDK — a demonstration of API-first design for agent accessibility. Schema Diff now supports schemas up to 20,000 lines (up from 8,000), and a new per-branch consumption metrics API lets you attribute usage to individual branches rather than rolling up to the project level.

Supabase CLI's TypeScript migration accelerates

Supabase shipped over a dozen CLI updates this week, with a clear pattern: the team is methodically porting command groups from Go to native TypeScript as it marches toward the v2.103.0-beta. This week's migrations covered snippets, organizations, SSO, branches, and vanity subdomains. The stable channel also saw the v2.102.0 release, which restored the completion subcommand tree in legacy shell and fixed identity stitch behavior in CI to stop ephemeral environment spam.

On the feature side, the CLI gained support for vector buckets in operations, and the team aligned legacy telemetry payloads with the Go CLI to ensure consistent data. The client SDK also saw a meaningful fix: a canary release now returns AuthInvalidJwtError from getClaims for expired JWTs, giving developers a structured error to catch rather than a silent failure, and another fix returns structured errors for non-JSON bodies on successful responses from PostgREST.

PlanetScale and Turso: deployment control and new partnerships

PlanetScale added a force cutover option for deploy requests when the cutover phase is delayed by long-running transactions — it aggressively stops those transactions to let the schema change proceed. For teams that regularly encounter this delay, an "aggressive cutover" database setting makes this the default behavior. The PlanetScale Go SDK v0.164.0 also gained a schema recommendation API alongside the async MoveTables cancel operation.

Turso announced a new Partner Program to expand its ecosystem, while the Turso CLI and libSQL library continued their pre-release churn with incremental updates across the week.