Neon's scheduled functions and Supabase's one-command local setup lead a busy serverless Postgres week

Workflow automation moves into the database platform

Neon spent the week turning Functions into a place to run background work rather than just request handlers. Function Triggers let a branch-scoped cron schedule invoke a deployed Function, with the timer living outside the Postgres compute so a database that scales to zero still fires on time — the thing pg_cron can't do. The triggers run JavaScript or TypeScript with access to HTTP, Object Storage, and the AI Gateway, and child branches inherit their parent's triggers in a disabled state until you turn them on. A sibling addition covers the event-driven half: a storage_object_created trigger invokes a Function whenever an object lands in a bucket, passing the bucket name and object key and optionally scoping to a key prefix, and these long-running Functions also stay compatible with scale to zero.

Functions also became easier to expose. Custom domains reached GA, so a branded hostname registered from the Console, CLI, SDK, or API replaces the generated invocation URL, with TLS provisioned automatically through Let's Encrypt. Domains attach to one Function on one branch, so each environment can carry its own. And branch hygiene caught up with the new storage surface: a branch reset from parent now rolls back Object Storage alongside Postgres data, reverting uploads, overwrites, and deletes to the parent's current state in the Ohio and Frankfurt regions. Meanwhile Neon sketched what's next, outlining plans to build realtime and sync natively into Neon and Lakebase around scale-to-zero and branching.

Supabase makes local-first the default

The Supabase CLI's headline feature is supabase pull, which orchestrates a complete local setup from a remote project in one step. The same release added experimental stack management commands for starting, stopping, listing, logging, preparing, and restarting local stacks, plus native type generation without Docker. Stability work covers the failure modes that made local development flaky: macOS hangs while publishing state, a Docker daemon stall that blocked db start, and large SQL blocks stalling db reset. Storage rm now demands explicit confirmation before deleting. On the JS side, the Client SDK enabled the passkey API by default, retiring the experimental opt-in and forwarding mediation options through to the credential request, and then fixed a cross-tab token refresh race that could drop the losing tab into a logged-out state — a fix that also appeared in a canary build. A later patch resolved instantiation depth errors for queries with large PostgREST relationship unions. Config handling picked up exclude patterns for compute build contexts.

Forcing functions and breaking changes

PlanetScale's database-js drew the sharpest line of the week: the driver removed parameter interpolation and moved its required Node version to 22, a breaking major that anyone still passing interpolated values to the client will have to address. The preceding patch had already been hardening the driver's edges, tightening placeholder parsing while clearing audit warnings and cleaning up CI.

The PlanetScale CLI, meanwhile, added start and stop commands for vtctld move-tables so long-running table migrations can be paused and resumed, and cleaned up D1 import SSL defaults and a false-positive verify mismatch on UUID column casing. Elsewhere, Prisma's next major continued to take shape with Postgres full-text search, prepared ORM reads, and multi-file schemas, alongside a stricter schema syntax that requires // use prisma-8 headers and exact table naming.