You can now assign custom names to your branch’s computes. In the Neon Console, go to the Branches page, select a branch, and open the Compute tab. Click the edit icon next to a compute to rename it.
You can also set a name when adding a new compute.
This enhancement is supported for both primary (read-write) and read replica computes.
TanStack integration & new open-source tools for JavaScript developers
We're excited to announce that Neon is now the official database partner of TanStack, and that we’ve released new open-source tools to simplify Postgres integration across the TanStack and Vite ecosystems:
Create TanStack Add-on
Instantly set up a fullstack application with a Neon Postgres database with one simple command:
pnpm create tanstack --add-on neon
Neon Launchpad
Instantly spin up a Postgres database with Neon Launchpad — no signup required. Perfect for workshops and rapid prototyping. Try it at neon.new. To learn more, see our Neon Launchpad docs.
NeonDB (CLI + SDK)
Bootstrap Neon Postgres database with the neondb CLI: npx neondb --yes
Or integrate programmatically via instantNeon().
Vite Plugin for Neon
Use Neon Launchpad to spin up a Postgres database with any Vite app: npm add -D @neondatabase/vite-plugin-postgres
These open-source tools are designed to streamline fullstack development with TanStack, Vite, and Postgres. Learn more:
You can now manage your project's OAuth providers (Google, GitHub, Microsoft) directly in the Neon Auth config tab—enable or disable providers, and choose between using shared Neon Auth credentials or setting up your own custom client credentials.
New API endpoints also let you manage providers programmatically:
The CLI now automatically detects invalid credentials (401 responses), deletes them, and prompts for re-authentication instead of failing immediately
🚀 If you're not using the Neon CLI yet, get set up in just a few steps with the Neon CLI Quickstart.
Fixes
Addressed an issue where projects created via Netlify DB and claimed into Vercel-managed org accounts could lose certain project configuration settings. To avoid this issue, transfers of projects created via Netlify DB to Vercel-managed org accounts are currently not supported.
Connection strings and snippets in the Neon Console now include channel_binding=require by default, providing stronger protection against man-in-the-middle (MITM) attacks for psql and other libpq-based clients:
Channel binding works alongside sslmode=require to cryptographically link your TLS connection and authentication credentials, making it nearly impossible for attackers to intercept or impersonate your database connections, strengthening security without required client-side root certificate setup.
Most libpq-based clients support this option transparently. For others (e.g., Go's pgdriver), compatibility may vary.
We recommend updating your connection strings to include channel_binding=require if you're using a libpq-based client.
We've made it easier for you to set up Neon RLS (Row Level Security) for your Neon Auth projects. The Auth page now displays your Stack Auth project details, including the JWKS URL needed for RLS setup.
To get started adding RLS to your Neon Auth project:
Copy the JWKS URL from the Configuration tab of your Auth page.
Paste it into the RLS authentication provider setup on the Settings > RLS for your project.
We've added new NAT gateway IP addresses in three AWS regions to expand infrastructure capacity. If you have external IP allowlists that enable connections from external services into Neon, update those allowlists soon to include the new addresses to avoid connectivity issues.
The neon_superuser role now supports Postgres Event Triggers. Unlike regular triggers, which are attached to a single table and capture only DML events, event triggers are global to a particular database and are capable of capturing DDL events.
Event trigger support enables various tools and platforms that utilize this functionality, including pgroll, Zero, and Readyset, among others.
Neon Launchpad now supports database seeding, allowing developers to automatically populate databases with SQL scripts during database initialization. This feature streamlines the development workflow by enabling instant database setup with sample data. The seeding capability is also available through the Vite plugin integration, making it accessible in Vite-based projects.
As announced earlier, we're rolling out scheduled updates that include Postgres version upgrades, security patches, and Neon feature improvements.
These updates are applied during your project's maintenance window or the next time the compute restarts. Most updates take only a few seconds.
Updates for Business plan projects will begin rolling out on July 9, 2025 — you'll receive an email notice in advance. You can also check for update notices and configure your preferred update window in the Neon Console — learn how.
Computes larger than 8 CU or those configured to autoscale beyond 8 CU are not updated automatically. You must restart these computes manually. See Updating large computes.
Improved API documentation for project management endpoints to clarify organization and org_id parameter requirements. See Personal vs organization API keys for details.
Fixes
PgBouncer connections from the Neon proxy were not immediately closed when a compute was suspended. This left connections open until the TCP timeout expired, causing connection issues. Connections are now cleanly terminated when a compute suspends.
OpenTelemetry integration
Neon now supports OpenTelemetry! You can send metrics and Postgres logs from Neon to any OpenTelemetry-compatible backend. You can enable the integration from the Integrations page in the Neon Console. For setup instructions, refer to our OpenTelemetry docs, with example configuration for New Relic.
Data API now available in beta for all Neon users
The Neon Data API is now in open beta for all users. Instantly turn your Neon Postgres database into a REST API. No backend required. Query tables, views, and functions right from your client app using standard HTTP verbs (GET, POST, PATCH, DELETE), powered by PostgREST.
We've improved our onboarding to make it easier to get Neon Auth and RLS set up as needed to safely use the Data API in your app.
API key-based authentication for the Neon MCP Server
The Neon MCP Server now supports API key-based authentication for remote access, in addition to OAuth. This allows for simpler authentication using your Neon API key (personal or organization) for programmatic access.
To improve ease-of-use, we've added a time selection option to date-time selectors in the Neon Console.
Drizzle Studio update
Drizzle Studio, which powers the Tables page in the Neon Console, has been updated to version 1.0.22. For details about the latest updates, see the Neon Drizzle Studio Changelog.