Neon

Recently shipped per-project permissions, Object Storage beta details, and a Castform post-training story.

Backend stack is now in beta. Object Storage, Functions, and AI Gateway are available to all users in AWS US East (Ohio). Declare your entire backend in one neon.ts file — it branches with your database.

Object Storage branches with your data. The S3-compatible store, free during beta, inherits buckets and objects into child branches at their creation point, alongside the database copy.

Access is now scoped per project. Four org roles — Admin, Editor, Viewer, Collaborator — set a baseline; individual projects can then grant Viewer, Editor, or Admin to people and agents. Agents receive scoped per-project credentials instead of org-wide keys. The model is live for new organizations and rolling out to existing ones.

CLI and SDK gained several new capabilities.

• The CLI renamed to neon (Node.js 20.19+). neon api calls any API route from the terminal; neon inspect db runs read-only Postgres diagnostics.
• @neon/sdk replaces the old API client with a createAndConnect method.
• Passkey authentication, Git-style CLI diffs, and Cmd+K in the Console shipped.

Stripe's stripe projects build command scaffolds a Neon database alongside other providers, joining the existing Vercel integration. Both give agents instant database access without manual setup.

Castform post-training pairs with Neon-backed retrieval. A 4B open-source model post-trained with Castform matched GPT-5.6 Sol on retrieval accuracy at roughly 100x lower cost — and one builder used the backend suite to assemble a working Git host during a GitHub outage.