Changelog

Give your computes a custom name

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:

• Neon Joins TanStack
• Neon Launchpad: A Tool For Instant Postgres, No Login Needed
• Neon Launchpad Docs

OAuth provider management for Neon Auth

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:

• Add an OAuth provider
• List OAuth providers
• Update an OAuth provider
• Delete an OAuth provider

To learn more, see the Neon Auth documentation.

One-click install: Neon MCP Server in Cursor

You can now add the Neon MCP Server to Cursor with a single click. Look for the Add to Cursor button in our MCP Server docs and in the GitHub repo, or try it here:

Enhanced connection security with channel binding

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:

postgresql://alex:AbC123dEf@ep-cool-darkness-a1b2c3d4-pooler.us-east-2.aws.neon.tech/dbname?sslmode=require&channel_binding=require

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.

Learn more in our blog post: Why Postgres needs better connection security defaults.

Simplified Neon RLS setup for Neon Auth projects

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:

1. Copy the JWKS URL from the Configuration tab of your Auth page.
2. Paste it into the RLS authentication provider setup on the Settings > RLS for your project.
3. Follow our UI to get RLS set up for your tables.

See Neon RLS for more info.

New NAT gateway IP addresses

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.

New IP addresses

AWS US East (N. Virginia) – aws-us-east-1

• 13.219.161.141
• 34.235.208.71
• 34.239.66.10

AWS US East (Ohio) – aws-us-east-2

• 3.16.227.37
• 3.128.6.252
• 52.15.165.218

AWS US West (Oregon) – aws-us-west-2

• 35.83.202.11
• 35.164.221.218
• 44.236.56.140

See our Regions documentation for the full list of NAT gateway IPs.

Support for Postgres Event Triggers

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.

For more about event triggers, see PostgreSQL Event Trigger.

Neon Launchpad now supports database seeding

Neon Launchpad enables instant provisioning of a Postgres database without configuration or account creation. If you're not familiar, you can learn more here: Neon Launchpad: A Tool For Instant Postgres, No Login Needed

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.

To try it from your terminal:

npx neondb --seed /path/to/file.sql

For more details, see:

• Neondb CLI Changelog
• Vite Plugin Changelog

Scheduled maintenance for Business plans

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.

To apply updates ahead of schedule, see Applying updates ahead of schedule.

Need help? Reach out to Neon Support.

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.

Learn more in our getting started guide. Or try this tutorial walkthrough of our demo note-taking app.

Check out the live demo to see it in action.

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.

{
  "mcpServers": {
    "Neon": {
      "url": "https://mcp.neon.tech/mcp",
      "headers": {
        "Authorization": "Bearer <$NEON_API_KEY>"
      }
    }
  }
}

For Neon MCP Server setup instructions, see our guide.