Neon Release Notes

Neon backend in Europe, plus new AI Gateway models

The Neon backend is now available in AWS Europe (Frankfurt) (aws-eu-central-1), alongside AWS US East (Ohio) (aws-us-east-2). If you build in Europe, you can now run these services closer to your users and data.

The AI Gateway catalog also gains new models, callable through the same API and key as the rest of the catalog:

• Fable 5.1
• GLM 5.3 Flash
• Grok 4.6
• OpenAI GPT-6 Astra (landing soon)

Try the Neon backend, free during the beta

Object Storage, Functions, and AI Gateway are in beta in AWS US East (Ohio) and AWS Europe (Frankfurt), and branch with your Postgres database, so your whole stack forks together.

Neon is now available in Grok Bot

Neon is now available as a plugin in Grok Bot. Connect your Neon account once, then ask a Grok bot to work with your database:

• Create a project and get a connection string for your app
• Spin up an isolated branch before testing a migration
• List projects and spot databases you no longer need
• Run SQL against your database
• Set up routines that summarize database usage

The plugin pairs Neon agent skills with the Neon MCP server, so Grok Bot has both the context and the authenticated tools to act on your account.

To install, open the Neon plugin in Grok Bot and authorize Neon in the browser. You can also open Grok Bot's Plugins directory and search for Neon, or ask Grok to connect the Neon plugin. Read more in the blog post.

Neon CLI updates

Two updates to the Neon CLI for setting up and connecting your projects:

• A leaner neon init: it now does one focused job based on where you run it: in an empty directory it scaffolds a template and installs agent tooling (like neon bootstrap); in an existing app it installs a plugin (or skills and MCP), links your project, and writes a neon.ts config. Run it with npx, and pass -y and --agent for unattended runs:
  npx neon@latest init
• neon env pull writes Neon Function invocation URLs: each function's public URL is written as NEON_FUNCTION__BASE_URL, so one function can reach another from the environment. See Environment variables.

Original source

Neon backend in Europe, plus new AI Gateway models

The Neon backend is now available in AWS Europe (Frankfurt) (aws-eu-central-1), alongside AWS US East (Ohio) (aws-us-east-2). If you build in Europe, you can now run these services closer to your users and data.

The AI Gateway catalog also gains new models, callable through the same API and key as the rest of the catalog:

• Fable 5.1
• GLM 5.3 Flash
• Grok 4.6
• OpenAI GPT-6 Astra (landing soon)

Try the Neon backend, free during the beta

Object Storage, Functions, and AI Gateway are in beta in AWS US East (Ohio) and AWS Europe (Frankfurt), and branch with your Postgres database, so your whole stack forks together.

Neon is now available in Grok Bot

Neon is now available as a plugin in Grok Bot. Connect your Neon account once, then ask a Grok bot to work with your database:

• Create a project and get a connection string for your app
• Spin up an isolated branch before testing a migration
• List projects and spot databases you no longer need
• Run SQL against your database
• Set up routines that summarize database usage

The plugin pairs Neon's agent skills with the Neon MCP server, so Grok Bot has both the context and the authenticated tools to act on your account.

To install, open the Neon plugin in Grok Bot and authorize Neon in the browser. You can also open Grok Bot's Plugins directory and search for Neon, or ask Grok to connect the Neon plugin. Read more in the blog post.

Neon CLI updates

Two updates to the Neon CLI for setting up and connecting your projects:

• A leaner neon init: it now does one focused job based on where you run it: in an empty directory it scaffolds a template and installs agent tooling (like neon bootstrap); in an existing app it installs a plugin (or skills and MCP), links your project, and writes a neon.ts config. Run it with npx, and pass -y and --agent for unattended runs:

npx neon@latest init

• neon env pull writes Neon Function invocation URLs: each function's public URL is written as NEON_FUNCTION__BASE_URL, so one function can reach another from the environment. See Environment variables.

HAVE AN IDEA FOR THE CLI OR AGENT TOOLS?

We'd love to hear it. Let us know via the Feedback form in the Neon Console or our feedback channel on Discord.

Postgres minor version rollout history now in the docs

Our Postgres version support policy docs now include a rollout history for recent minor releases. For each release, you can see the date PostgreSQL published it, the versions it included, when it became available on Neon, and how long that took. For example:

Postgres release date | Versions in the release | First available on Neon | Time to availability
2026-08-13 | 18.6, 17.11, 16.15, 15.19, 14.24 | 2026-08-18 | 5 days

Each version in the table links to its PostgreSQL release notes, so you can see exactly which bug fixes and CVE patches that minor release contains.

INFO

Run SELECT version(); to see which version you're on. Minor version updates are rolled out the next time your compute restarts. To update now, restart your compute yourself, or wait for your compute's next scheduled update. See Updates for details.

Get started building on the Neon backend

Two new guides show what you can build with the Neon backend, where Object Storage, Functions, and the AI Gateway sit next to your database:

• Build an image processing API with Neon Functions, Sharp, and Neon AI Gateway: resize, crop, optimize, analyze, and AI-caption images on Neon Functions, then store the results in your branch's Object Storage bucket.
• Clean up orphaned S3 objects with Neon Object Storage branching: run a real storage-cleanup job on a branch first, where buckets branch with your database, then promote it to production once you've verified it.

Try the Neon backend, free during the beta

Object Storage, Functions, and AI Gateway are in beta in AWS US East (Ohio) and branch with your Postgres database, so your whole stack forks together.

Connect fx to Neon's MCP server

fx is a small, fast coding agent and CLI from Vercel Labs, built to embed in larger systems. You can now connect it to Neon's remote MCP server, using either OAuth or a Neon API key, so the agent can work with your Neon projects directly.

For example, add the server with OAuth:

npx add-mcp https://mcp.neon.tech/mcp -a fx

Then authorize from the fx shell:

/mcp auth neon --open

For the API key option and more detail, see Connect MCP clients to Neon.

Fixes & improvements

• Neon MCP server updates
• New NAT gateway IPs and Private Networking endpoints in us-east-2

Original source

Add Neon to your coding agent

Three new Neon CLI commands set up Neon in coding agents like Cursor and Claude Code, without manual config steps. Each runs an interactive walkthrough, or takes flags so you can script it.

neon mcp

Installs the Neon MCP Server into your agents by writing their MCP config for you. It points each agent at the hosted server, sets up authentication, and can limit which tools the agent sees. By default, it mints a Neon API key and writes it into the config. Alternativevly, pass --oauth to skip API-key creation and have the agent sign in to Neon on first use instead.

For example, install into Cursor and Claude Code with read-only tools:

neon mcp --agent cursor --agent claude-code --read-only

neon skills

Installs Neon's agent skills so tools like Cursor and Claude Code know how to work with Neon's Postgres, AI Gateway, Object Storage, and Functions. Skills install into the current directory by default, so they travel with the repository, and neon skills update refreshes them to their latest versions later.

For example, install the core Postgres and AI Gateway skills into Cursor:

neon skills -s neon -s neon-ai-gateway --agent cursor

neon plugins

Installs the neon-postgres plugin into agents that support plugin marketplaces, such as Claude Code, Cursor, and Codex. The plugin bundles Neon's agent skills and MCP access in one package, so a single install gives the agent both.

For example, install into Claude Code without prompts:

neon plugins --agent claude-code -y

The Neon CLI has seen many new additions over the past several weeks. For a tour of other recent additions, from the branch-first workflow to built-in Postgres diagnostics, see Just landed in the Neon CLI.

HAVE AN IDEA FOR THE CLI OR AGENT TOOLS?

We'd love to hear it. Let us know via the Feedback form in the Neon Console or our feedback channel on Discord.

Postgres minor version rollout history now in the docs

Our Postgres version support policy docs now include a rollout history for recent minor releases. For each release, you can see the date PostgreSQL published it, the versions it included, when it became available on Neon, and how long that took. For example:

Postgres release date Versions in the release First available on Neon Time to availability 2026-08-13 18.6, 17.11, 16.15, 15.19, 14.24 2026-08-18 5 days

Each version in the table links to its PostgreSQL release notes, so you can see exactly which bug fixes and CVE patches that minor release contains.

INFO

Run SELECT version(); to see which version you're on. Minor version updates are rolled out the next time your compute restarts. To update now, restart your compute yourself, or wait for your compute's next scheduled update. See Updates for details.

Get started building on the Neon backend

Two new guides show what you can build with the Neon backend, where Object Storage, Functions, and the AI Gateway sit next to your database:

• Build an image processing API with Neon Functions, Sharp, and Neon AI Gateway: resize, crop, optimize, analyze, and AI-caption images on Neon Functions, then store the results in your branch's Object Storage bucket.
• Clean up orphaned S3 objects with Neon Object Storage branching: run a real storage-cleanup job on a branch first, where buckets branch with your database, then promote it to production once you've verified it.

Try the Neon backend, free during the beta

Object Storage, Functions, and AI Gateway are in beta in AWS US East (Ohio) and branch with your Postgres database, so your whole stack forks together.

Connect fx to Neon's MCP server

fx is a small, fast coding agent and CLI from Vercel Labs, built to embed in larger systems. You can now connect it to Neon's remote MCP server, using either OAuth or a Neon API key, so the agent can work with your Neon projects directly.

For example, add the server with OAuth:

npx add-mcp https://mcp.neon.tech/mcp -a fx

Then authorize from the fx shell:

/mcp auth neon --open

For the API key option and more detail, see Connect MCP clients to Neon.

Fixes & improvements

Neon MCP server updates

New NAT gateway IPs and Private Networking endpoints in us-east-2

Original source

Add Neon to your coding agent

Three new Neon CLI commands set up Neon in coding agents like Cursor and Claude Code, without manual config steps. Each runs an interactive walkthrough, or takes flags so you can script it.

neon mcp

Installs the Neon MCP Server into your agents by writing their MCP config for you. It points each agent at the hosted server, sets up authentication, and can limit which tools the agent sees. By default, it mints a Neon API key and writes it into the config. Alternativevly, pass --oauth to skip API-key creation and have the agent sign in to Neon on first use instead.

For example, install into Cursor and Claude Code with read-only tools:

neon mcp --agent cursor --agent claude-code --read-only

neon skills

Installs Neon's agent skills so tools like Cursor and Claude Code know how to work with Neon's Postgres, AI Gateway, Object Storage, and Functions. Skills install into the current directory by default, so they travel with the repository, and neon skills update refreshes them to their latest versions later.

For example, install the core Postgres and AI Gateway skills into Cursor:

neon skills -s neon -s neon-ai-gateway --agent cursor

neon plugins

Installs the neon-postgres plugin into agents that support plugin marketplaces, such as Claude Code, Cursor, and Codex. The plugin bundles Neon's agent skills and MCP access in one package, so a single install gives the agent both.

For example, install into Claude Code without prompts:

neon plugins --agent claude-code -y

The Neon CLI has seen many new additions over the past several weeks. For a tour of other recent additions, from the branch-first workflow to built-in Postgres diagnostics, see Just landed in the Neon CLI.

HAVE AN IDEA FOR THE CLI OR AGENT TOOLS?

We'd love to hear it. Let us know via the Feedback form in the Neon Console or our feedback channel on Discord.

Postgres minor version rollout history now in the docs

Our Postgres version support policy docs now include a rollout history for recent minor releases. For each release, you can see the date PostgreSQL published it, the versions it included, when it became available on Neon, and how long that took. For example:

Postgres release date Versions in the release First available on Neon Time to availability 2026-08-13 18.6, 17.11, 16.15, 15.19, 14.24 2026-08-18 5 days

Each version in the table links to its PostgreSQL release notes, so you can see exactly which bug fixes and CVE patches that minor release contains.

INFO

Run SELECT version(); to see which version you're on. Minor version updates are rolled out the next time your compute restarts. To update now, restart your compute yourself, or wait for your compute's next scheduled update. See Updates for details.

Original source

Faster Lakebase Search setup

Lakebase Search is now easier to install. You can install both Lakebase Search extensions (lakebase_vector and lakebase_text) directly with the following CREATE EXTENSION statements from your SQL client or the Neon SQL Editor :

CREATE EXTENSION IF NOT EXISTS lakebase_vector CASCADE;
CREATE EXTENSION IF NOT EXISTS lakebase_text CASCADE;

Previously, you had to run an SQL statement first to load the supporting libraries.

We also updated both extensions to newer versions (lakebase_vector 1.0.1 and lakebase_text 0.1.1). If you already have them installed, see Update an extension to get the latest version.

GET STARTED WITH LAKEBASE SEARCH

Lakebase Search is a pgvector-compatible alternative for vector, keyword, and hybrid search that scales past a billion vectors, builds indexes 50–100x faster than HNSW, and stays ready after a scale-to-zero cold start. Follow the getting started guide to enable the extensions, load sample data, and run your first vector and keyword searches.

Postgres minor version updates

We updated supported Postgres versions to 14.24, 15.19, 16.15, 17.11, and 18.6. Minor releases bring you the latest upstream Postgres fixes and security patches.

When a new minor version is available, Neon applies it the next time your compute restarts. For more about how we handle PostgreSQL minor version updates, refer to our Postgres version support policy.

Neon CLI updates

Store credentials in your OS keyring.

You can now keep a profile's credential in your operating system's keyring instead of a file. Pass --keyring to neon auth or neon profile create :

neon auth --keyring

The secret is stored in the macOS Keychain, Windows Credential Manager, or Linux Secret Service.

Inspect every database at once.

neon inspect db now inspects every database on the branch when you omit the database name, adding a database column to the output. Pass the database name to inspect a single database, which also scopes locks and long-running-queries so their names resolve correctly.

NOTE

This change is also available in the Neon MCP server's inspect_database tool.

Neon MCP server now an official Claude connector

The Neon MCP server is now listed in Claude's connectors. You can manage Neon from Claude: create projects and branches, run SQL, change schemas, and diagnose a slow query.

In Claude.ai or Claude Desktop, go to Settings > Connectors, click Browse connectors, add Neon, and authorize access to your Neon account.

Install Neon Agent Skills with Pi

You can now install Neon Agent Skills with Pi, straight from the repository:

pi install git:github.com/neondatabase/agent-skills

Pi reads the skills directly, so there's no separate sync step. This joins the existing install channels, including npx skills, the Cursor, Claude Code, Codex, and Kimi Code plugins, and neon init.

New Neon Functions guides

Two new guides show what you can build on Neon Functions, which run alongside your database as part of the Neon backend :

• Automate Neon Functions deployments with GitHub Actions: set up CI/CD to deploy to production on merge and create preview functions for pull requests.
• Monitor Neon Functions with Sentry: add error tracking, structured logs, and request tracing.

Try the Neon backend

Object Storage, Functions, and AI Gateway branch with your Postgres database, so your whole stack forks together.

Get started

Original source

Faster Lakebase Search setup

Lakebase Search is now easier to install. You can install both Lakebase Search extensions (lakebase_vector and lakebase_text) directly with the following CREATE EXTENSION statements from your SQL client or the Neon SQL Editor :

CREATE EXTENSION IF NOT EXISTS lakebase_vector CASCADE;
CREATE EXTENSION IF NOT EXISTS lakebase_text CASCADE;

Previously, you had to run an SQL statement first to load the supporting libraries.

We also updated both extensions to newer versions (lakebase_vector 1.0.1 and lakebase_text 0.1.1). If you already have them installed, see Update an extension to get the latest version.

GET STARTED WITH LAKEBASE SEARCH

Lakebase Search is a pgvector-compatible alternative for vector, keyword, and hybrid search that scales past a billion vectors, builds indexes 50–100x faster than HNSW, and stays ready after a scale-to-zero cold start. Follow the getting started guide to enable the extensions, load sample data, and run your first vector and keyword searches.

Postgres minor version updates

We updated supported Postgres versions to 14.24, 15.19, 16.15, 17.11, and 18.6. Minor releases bring you the latest upstream Postgres fixes and security patches.

When a new minor version is available, Neon applies it the next time your compute restarts. For more about how we handle PostgreSQL minor version updates, refer to our Postgres version support policy.

Neon CLI updates

Store credentials in your OS keyring.

You can now keep a profile's credential in your operating system's keyring instead of a file. Pass --keyring to neon auth or neon profile create :

neon auth --keyring

The secret is stored in the macOS Keychain, Windows Credential Manager, or Linux Secret Service.

Inspect every database at once.

neon inspect db now inspects every database on the branch when you omit the database name, adding a database column to the output. Pass the database name to inspect a single database, which also scopes locks and long-running-queries so their names resolve correctly.

NOTE

This change is also available in the Neon MCP server's inspect_database tool.

Neon MCP server now an official Claude connector

The Neon MCP server is now listed in Claude's connectors. You can manage Neon from Claude: create projects and branches, run SQL, change schemas, and diagnose a slow query.

In Claude.ai or Claude Desktop, go to Settings > Connectors, click Browse connectors, add Neon, and authorize access to your Neon account.

Install Neon Agent Skills with Pi

You can now install Neon Agent Skills with Pi , straight from the repository:

pi install git:github.com/neondatabase/agent-skills

Pi reads the skills directly, so there's no separate sync step. This joins the existing install channels, including npx skills , the Cursor, Claude Code, Codex, and Kimi Code plugins, and neon init .

New Neon Functions guides

Two new guides show what you can build on Neon Functions , which run alongside your database as part of the Neon backend :

• Automate Neon Functions deployments with GitHub Actions: set up CI/CD to deploy to production on merge and create preview functions for pull requests.
• Monitor Neon Functions with Sentry: add error tracking, structured logs, and request tracing.

Try the Neon backend

Object Storage, Functions, and AI Gateway branch with your Postgres database, so your whole stack forks together.

Get started

Original source

Electric joins Neon

Electric, the team behind the Electric sync engine and PGlite, is joining Neon. The sync engine keeps data continuously synchronized between a central Postgres database and connected clients such as browser tabs, mobile apps, and agents, so you can build real-time, collaborative, and agentic apps without hand-rolling websockets, caching, and a sync layer.

Real-time sync is hard to get right on your own: conflict resolution, partial replication, and reconnection logic are difficult to build from scratch. Electric turns it into a reusable primitive that handles the hard parts, so agents can add live, collaborative features by default instead of wiring up sync themselves.

Electric is coming to the Neon platform alongside Neon's other backend services (Lakebase Postgres, Auth, Storage, Functions, and the AI Gateway), with deeper integration already underway. To get familiar now, our guide to Electric on Neon walks through real-time sync with Shapes and a React app.

Read the full announcement: Electric is joining team Neon at Databricks.

Neon AI Gateway is now a Vercel AI SDK provider

The Neon AI Gateway gives you one API and one credential for 42+ frontier and open-source models (OpenAI, Anthropic, Google, and more), built into your Neon branch. It's now a community provider for the Vercel AI SDK: point the SDK at your branch and swap models without per-provider SDKs or keys.

import { neon } from '@neon/ai-sdk-provider';
import { generateText } from 'ai';
const { text } = await generateText({ model: neon('gpt-5-mini'), prompt: 'What is serverless Postgres?', });

Set NEON_AI_GATEWAY_BASE_URL and NEON_AI_GATEWAY_TOKEN from your branch, or pull them with neon env pull.

FREE AI GATEWAY CREDITS ON PAID PLANS

While in beta, Neon paid-plan users get free AI Gateway credits. To try it out, see Get started with Neon AI Gateway.

Neon's skills and MCP install in any agent

Support for Agent Plugins 1.0.0

Neon's agent skills and MCP server now ship as an Agent Plugins package, an open standard for extending agents with skills and MCP. Point any conforming client, such as Cursor, Codex, GitHub Copilot, Kiro, or VS Code, at the repo to load them straight from source.

All existing native plugins remain available:

Claude Code: /plugin marketplace add neondatabase/agent-skills, then /plugin install neon-postgres@neon
Cursor: /add-plugin neon-postgres
Kimi Code: /plugins install https://github.com/neondatabase/agent-skills

Neon CLI updates

The CLI keeps growing. Recent additions include a branch-first workflow (neon link, neon checkout, neon psql, neon data-api) and commands for the new backend services (neon functions, neon buckets); see the CLI reference for the full set. Two of the latest:

neon env pull gained a --service flag to pull credentials for only the services you name, repeatable for more than one:

neon env pull --service ai-gateway --service postgres

neon open (neonctl 3.2.0) opens your linked project's dashboard in the Neon Console, straight from the terminal:

neon open

Inspect a database from the Neon MCP server

We first shipped these diagnostics as the neon inspect db CLI command. The same checks are now built into the Neon MCP server as the inspect_database tool. It runs the same 14 read-only diagnostics: table and index sizes, unused indexes, sequential scans, long-running queries and locks, heavy and frequent statements, cache hit rate and working set, autovacuum and bloat, and replication state. Ask your assistant why a branch is slow or large without writing catalog SQL by hand.

Don't have the MCP server set up yet? Install it with neon init:

npx neon@latest init

Neon for Herdr

Neon for Herdr puts a live Neon pane in your Herdr terminal workspace. Browse projects, create and reset branches, start or suspend compute, and copy connection strings without leaving your editor.

Read the post: Neon for Herdr: a Neon pane in your Herdr workspace.

New NAT gateway IPs and VPC endpoint services in US West (Oregon) and Asia Pacific (Singapore)

Original source

Electric joins Neon

Electric, the team behind PGlite and its Postgres sync engine, is joining Neon. Together they push Postgres all the way to the client and keep it live, so you can build real-time, collaborative, local-first, and agentic apps without hand-rolling a websocket, caching, and sync layer.

PGlite is a full Postgres that runs in a browser tab, a sandbox, or a serverless function, and the sync engine keeps it continuously in sync with your central Lakebase Postgres database. For AI agents, that makes real-time sync a built-in primitive, so they can add live, collaborative features without wiring up sync themselves.

Both PGlite and the sync engine are coming to the Neon platform alongside Neon's other backend services (Lakebase Postgres, Auth, Storage, Functions, and the AI Gateway), with deeper integration already underway. To get familiar now, our guide to Electric on Neon walks through real-time sync with Shapes and a React app.

Read the full announcement: Electric is joining team Neon at Databricks.

Neon AI Gateway is now a Vercel AI SDK provider

The Neon AI Gateway gives you one API and one credential for 42+ frontier and open-source models (OpenAI, Anthropic, Google, and more), built into your Neon branch. It's now a community provider for the Vercel AI SDK: point the SDK at your branch and swap models without per-provider SDKs or keys.

Code example:

import { neon } from '@neon/ai-sdk-provider';
import { generateText } from 'ai';
const { text } = await generateText({ model: neon('gpt-5-mini'), prompt: 'What is serverless Postgres?' });

Set NEON_AI_GATEWAY_BASE_URL and NEON_AI_GATEWAY_TOKEN from your branch, or pull them with neon env pull.

FREE AI GATEWAY CREDITS ON PAID PLANS

While in beta, Neon paid-plan users get free AI Gateway credits. To try it out, see Get started with Neon AI Gateway.

Neon's skills and MCP install in any agent

Neon's agent skills and MCP server now ship as an Agent Plugins package, an open standard for extending agents with skills and MCP. Point any conforming client, such as Cursor, Codex, GitHub Copilot, Kiro, or VS Code, at the repo to load them straight from source.

All existing native plugins remain available:

• Claude Code: /plugin marketplace add neondatabase/agent-skills, then /plugin install neon-postgres@neon
• Cursor: /add-plugin neon-postgres
• Kimi Code: /plugins install https://github.com/neondatabase/agent-skills

Neon CLI updates

The CLI keeps growing. Recent additions include a branch-first workflow (neon link, neon checkout, neon psql, neon data-api) and commands for the new backend services (neon functions, neon buckets); see the CLI reference for the full set. Two of the latest:

• neon env pull gained a --service flag to pull credentials for only the services you name, repeatable for more than one:
  neon env pull --service ai-gateway --service postgres
• neon open (neonctl 3.2.0) opens your linked project's dashboard in the Neon Console, straight from the terminal:
  neon open

Inspect a database from the Neon MCP server

We first shipped these diagnostics as the neon inspect db CLI command. The same checks are now built into the Neon MCP server as the inspect_database tool. It runs the same 14 read-only diagnostics: table and index sizes, unused indexes, sequential scans, long-running queries and locks, heavy and frequent statements, cache hit rate and working set, autovacuum and bloat, and replication state. Ask your assistant why a branch is slow or large without writing catalog SQL by hand.

Don't have the MCP server set up yet? Install it with neon init:

npx neon@latest init

Neon for Herdr

Neon for Herdr puts a live Neon pane in your Herdr terminal workspace. Browse projects, create and reset branches, start or suspend compute, and copy connection strings without leaving your editor.

Commands:

herdr plugin install neon-solutions/neon-herdr
herdr plugin action invoke neon.herdr.dashboard

Read the post: Neon for Herdr: a Neon pane in your Herdr workspace.

New NAT gateway IPs and VPC endpoint services in US West (Oregon) and Asia Pacific (Singapore)

Original source

A new Console layout for the Neon backend

The Console sidebar has a new shape. Every branch-level Neon backend service now sits at the same level.

Postgres database is everything that was in the sidebar before: Tables, SQL Editor, Backup & Restore, Computes, Data API, Roles, and Databases, now under one collapsible item.

Auth, Object storage, Functions, and AI Gateway backend services sit alongside it as siblings.

Above that section, the sidebar separates what belongs to project (Dashboard, Branches, Integrations, Settings) from what belongs to the branch (Overview, Credentials, Monitoring, Child branches). The branch picker sits between them, so it's clear which branch you're looking at when you open a service.

Overview is now a summary of the branch you have selected. It lists each backend service with its status, so you can see what the branch actually has enabled without opening each one:

Each service shows whether it's enabled on the branch, so the page doubles as a list of what you can still add.

MORE REGIONS FOR BACKEND SERVICES COMING SOON

Object Storage, Functions, and the AI Gateway services are available only in AWS US East (Ohio) (aws-us-east-2). More regions are coming soon.

More models on the AI Gateway

We've expanded the models available through the Neon AI Gateway, including Kimi K3, GLM-5.2, Inkling, and new additions to the Gemini and GPT families.

The catalog now spans frontier and open-weight models from OpenAI, Anthropic, Google, Meta, Moonshot AI, Alibaba, Zhipu AI, and Thinking Machines. One credential and one base URL reach all of them, so trying a different model means changing a string rather than signing up with another provider:

curl -X POST "$NEON_AI_GATEWAY_BASE_URL/v1/chat/completions" \
  -H "Authorization: Bearer $NEON_AI_GATEWAY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"model": "kimi-k3", "messages": [{"role": "user", "content": "What is Neon?"}]}'

Browse the full catalog in the model reference, where you can filter by provider or open weights and open any model for a copy-paste quickstart. To see what your own project can reach right now, call GET /v1/models.

SET UP THE NEON BACKEND WITH YOUR AI AGENT

To build with the beta services including AI Gateway, install the Neon agent skills so your assistant knows how to provision and wire them up:

npx neon@latest init

Then ask your assistant to get started with Neon. See the backend beta guide for access and setup, or How a Neon backend fits together for a tour of all five capabilities.

Project-level permissions for all orgs

Last week we introduced project-level permissions to newly created organizations. Existing organizations are now supported, so every team on Neon has the four organization roles (Admin, Editor, Viewer, and Collaborator) and per-project permissions.

See Neon now has per-project permissions for the annoucement, and User permissions for the complete documentation.

GET STARTED WITH PROJECT PERMISSIONS

Go from everyone-sees-everything to scoped access in about five minutes. Read the guide.

API keys and multiple accounts in the Neon CLI

There are two new additions to the Neon CLI that go together: api-keys mints credentials, and profile stores them and switches between them. Together they let you give an agent a credential that reaches exactly one project, or work across a personal account and a work organization without juggling config directories.

NEW TO THE NEON CLI?

Install it with npm install -g neon, then authenticate with neon auth. See the install guide and CLI quickstart to get going.

Manage API keys with neon api-keys

Manage API keys with neon api-keys

Minting a key used to mean opening the Console or hand-rolling a neon api request. neon api-keys now covers listing, creating, and revoking keys at every scope:

neon api-keys create --name ci # account key
neon api-keys create --name ci --org-id org-example-12345678 # organization key
neon api-keys create --name agent --project-id green-breeze-12345678 # one project only

Project-scoped keys are the reason this matters. A key created with --project-id can't create projects, can't mint more keys, and can't see any other project, which makes it safe to hand to an agent or a CI job instead of sharing your account.

See the neon api-keys reference neon api-keys reference and Manage API keys for key types and permissions.

Use more than one account with neon profile

Use more than one account with neon profile

The CLI could only hold one account at a time, so anyone working across two built their own workaround out of --config-dir and shell aliases. A profile is a name pointing at a credentials file, selected per invocation with --profile or NEON_PROFILE :

neon auth --profile work # create or re-authenticate
neon deploy --profile work # use it
neon profile create ci --mint --project-id green-breeze-12345678 # or hold a scoped key, no browser

A profile can hold a browser sign-in or an API key, which is where it meets the scoped keys above. --mint signs in once, keeps only the minted key, and signs the session back out, so afterwards nothing about the profile can open a browser.

The CLI also now stores its configuration in $XDG_CONFIG_HOME/neon , or ~/.config/neon if that isn't set. A pre-existing neonctl directory is still read in place, so there's no migration step.

See the neon profile reference neon profile reference for the full command set and for how --profile resolves against NEON_API_KEY .

New NAT gateway IPs and VPC endpoint services in Europe (Frankfurt)

We've expanded infrastructure capacity in the AWS Europe (Frankfurt) region (eu-central-1) with new NAT gateway IP addresses and new VPC endpoint service addresses for Private Networking.

UPDATE YOUR IP ALLOWLISTS

If you have IP allowlists on external systems that Neon connects to, update those allowlists to include the new NAT gateway addresses. Connections may be affected intermittently if traffic routes through non-allowlisted NAT gateways.

If you use Private Networking in eu-central-1 , you can now use the additional VPC endpoint service addresses for enhanced capacity and reliability. See the Regions documentation for the complete list of NAT gateway IPs and the Private Networking guide for VPC endpoint service addresses by region.

Original source

A new Console layout for the Neon backend

The Console sidebar has a new shape. Every branch-level Neon backend service now sits at the same level.

• Postgres database is everything that was in the sidebar before: Tables, SQL Editor, Backup & Restore, Computes, Data API, Roles, and Databases, now under one collapsible item.
• Auth, Object storage, Functions, and AI Gateway backend services sit alongside it as siblings.

Above that section, the sidebar separates what belongs to project (Dashboard, Branches, Integrations, Settings) from what belongs to the branch (Overview, Credentials, Monitoring, Child branches). The branch picker sits between them, so it's clear which branch you're looking at when you open a service.

Overview is now a summary of the branch you have selected. It lists each backend service with its status, so you can see what the branch actually has enabled without opening each one:

Each service shows whether it's enabled on the branch, so the page doubles as a list of what you can still add.

MORE REGIONS FOR BACKEND SERVICES COMING SOON

Object Storage, Functions, and the AI Gateway services are available only in AWS US East (Ohio) (aws-us-east-2). More regions are coming soon.

More models on the AI Gateway

We've expanded the models available through the Neon AI Gateway, including Kimi K3, GLM-5.2, Inkling, and new additions to the Gemini and GPT families.

The catalog now spans frontier and open-weight models from OpenAI, Anthropic, Google, Meta, Moonshot AI, Alibaba, Zhipu AI, and Thinking Machines. One credential and one base URL reach all of them, so trying a different model means changing a string rather than signing up with another provider:

curl -X POST "$NEON_AI_GATEWAY_BASE_URL/v1/chat/completions" \
-H "Authorization: Bearer $NEON_AI_GATEWAY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"model": "kimi-k3", "messages": [{"role": "user", "content": "What is Neon?"}]}'

Browse the full catalog in the model reference, where you can filter by provider or open weights and open any model for a copy-paste quickstart. To see what your own project can reach right now, call GET /v1/models.

SET UP THE NEON BACKEND WITH YOUR AI AGENT

To build with the beta services including AI Gateway, install the Neon agent skills so your assistant knows how to provision and wire them up:

npx neon@latest init

Then ask your assistant to get started with Neon. See the backend beta guide for access and setup, or How a Neon backend fits together for a tour of all five capabilities.

Project-level permissions for all orgs

Last week we introduced project-level permissions to newly created organizations. Existing organizations are now supported, so every team on Neon has the four organization roles (Admin, Editor, Viewer, and Collaborator) and per-project permissions.

See Neon now has per-project permissions for the annoucement, and User permissions for the complete documentation.

GET STARTED WITH PROJECT PERMISSIONS

Go from everyone-sees-everything to scoped access in about five minutes. Read the guide.

API keys and multiple accounts in the Neon CLI

There are two new additions to the Neon CLI that go together: api-keys mints credentials, and profile stores them and switches between them. Together they let you give an agent a credential that reaches exactly one project, or work across a personal account and a work organization without juggling config directories.

NEW TO THE NEON CLI?

Install it with npm install -g neon, then authenticate with neon auth. See the install guide and CLI quickstart to get going.

Manage API keys with neon api-keys

Minting a key used to mean opening the Console or hand-rolling a neon api request. neon api-keys now covers listing, creating, and revoking keys at every scope:

neon api-keys create --name ci # account key
neon api-keys create --name ci --org-id org-example-12345678 # organization key
neon api-keys create --name agent --project-id green-breeze-12345678 # one project only

Project-scoped keys are the reason this matters. A key created with --project-id can't create projects, can't mint more keys, and can't see any other project, which makes it safe to hand to an agent or a CI job instead of sharing your account.

See the neon api-keys reference and Manage API keys for key types and permissions.

Use more than one account with neon profile

The CLI could only hold one account at a time, so anyone working across two built their own workaround out of --config-dir and shell aliases. A profile is a name pointing at a credentials file, selected per invocation with --profile or NEON_PROFILE:

neon auth --profile work # create or re-authenticate
neon deploy --profile work # use it
neon profile create ci --mint --project-id green-breeze-12345678 # or hold a scoped key, no browser

A profile can hold a browser sign-in or an API key, which is where it meets the scoped keys above. --mint signs in once, keeps only the minted key, and signs the session back out, so afterwards nothing about the profile can open a browser.

The CLI also now stores its configuration in $XDG_CONFIG_HOME/neon, or ~/.config/neon if that isn't set. A pre-existing neonctl directory is still read in place, so there's no migration step.

See the neon profile reference for the full command set and for how --profile resolves against NEON_API_KEY.

New NAT gateway IPs and VPC endpoint services in Europe (Frankfurt)

We've expanded infrastructure capacity in the AWS Europe (Frankfurt) region (eu-central-1) with new NAT gateway IP addresses and new VPC endpoint service addresses for Private Networking.

UPDATE YOUR IP ALLOWLISTS

If you have IP allowlists on external systems that Neon connects to, update those allowlists to include the new NAT gateway addresses. Connections may be affected intermittently if traffic routes through non-allowlisted NAT gateways.

If you use Private Networking in eu-central-1, you can now use the additional VPC endpoint service addresses for enhanced capacity and reliability. See the Regions documentation for the complete list of NAT gateway IPs and the Private Networking guide for VPC endpoint service addresses by region.

Original source

Project-level permissions

A feature you've been asking for is finally here. Until now, a person's access applied across your entire organization. We're excited to bring project-level permissions to Neon, so you can now grant people and agents access on individual projects, giving them only what they need where they need it. On any project, you can make someone a Viewer to see its resources, an Editor to change them, or an Admin to manage access and the project itself.

AVAILABILITY

The new model is available now for newly created organizations and will roll out to existing organizations soon.

Access works in two layers. When both apply, a user keeps the higher level of access:

• Organization roles set a baseline across every project. There are now four: Admin (full control), Editor (work in every project, but can't delete or transfer them), Viewer (read-only), and Collaborator (no access until granted specific projects).
• Per-project permissions raise that baseline on specific projects. Grant a member Viewer (read-only), Editor (connect, query, and edit resources), or Admin (manage access, settings, and the project lifecycle) on any project from Settings → Project permissions.

For example, give a contractor the Collaborator role, which grants nothing by default, then Editor on just the two projects they work on. Or give a teammate Viewer across the organization and Admin on the one project they own.

You can manage the same access through the Neon API, so an orchestrator can provision a project and grant a worker agent scoped access to it:

curl --request PUT \
--url 'https://console.neon.tech/api/v2/projects/{project_id}/members/{member_id}/role' \
--header 'authorization: Bearer $ORG_API_KEY' \
--header 'content-type: application/json' \
--data '{"role": "editor"}'

The CLI doesn't have a dedicated command yet, but you can call the same route with the neon api passthrough.

What changes for existing organizations

When your organization is migrated, it moves to the new model automatically, and everyone keeps the access they have today. No action is required:

• Admins stay Admins.
• Members become Editors, with the same access under the new name.
• Project creators become Admin on the projects they created.
• People with project-share access become Editor on the projects shared with them.

The older project collaboration feature is being replaced by the new Collaborator role plus per-project permissions.

See User permissions for roles, per-project levels, and how the two layers combine.

New guides for building on the Neon backend

Two new guides show how to combine the Neon backend services, from long-running compute to LLM access, all in a single project that branches with your data:

• Build durable background workflows with Inngest and Neon Functions: run a multi-step lead-enrichment pipeline on Neon Functions, with each step checkpointed so a failure retries just that step, and an executive summary generated through the Neon AI Gateway.
• Build an LLM proxy with Neon Functions, Neon AI Gateway, and Managed Better Auth: host a secure proxy on Neon Functions that keeps your LLM keys off the browser, authenticates users with Managed Better Auth, enforces per-user rate limits in Postgres, and streams responses from the AI Gateway.

SET UP THE NEON BACKEND WITH YOUR AI AGENT

The backend services (Object Storage, Functions, and AI Gateway) are in beta in AWS us-east-2. To build with them, install the Neon agent skills so your assistant knows how to provision and wire them up:

npx neon@latest init

Then ask your assistant to get started with Neon. See the backend beta guide for access and setup.

More with Lakebase Search

Lakebase Search adds scalable vector, keyword, and hybrid search to Postgres through the lakebase_vector and lakebase_text extensions. This week, two new resources show it in action:

• Case study: CommSync runs text, vector, and hybrid search on Postgres with Lakebase Search. See how a unified business inbox powers its main inbox (BM25 text search), AI assistant (semantic search), and command palette (hybrid search with Reciprocal Rank Fusion) from a single database, cutting query latency from 19.5 seconds to 18.6 milliseconds.
• Guide: Build image search over CLIP embeddings with Lakebase Search. Search a Flickr30k corpus by text, by image, and by caption from one vector(512) column, using the lakebase_ann index (IVF + RaBitQ) that builds 50 to 100 times faster than HNSW.

To get started, load the Lakebase Search preload libraries, then create the extensions:

CREATE EXTENSION IF NOT EXISTS lakebase_vector CASCADE;
CREATE EXTENSION IF NOT EXISTS lakebase_text CASCADE;

Fixes & improvements

Spending notifications

Neon MCP Server

Drizzle Studio

Original source

Project-level permissions

A feature you've been asking for is finally here. Until now, a person's access applied across your entire organization. We're excited to bring project-level permissions to Neon, so you can now grant people and agents access on individual projects, giving them only what they need where they need it. On any project, you can make someone a Viewer to see its resources, an Editor to change them, or an Admin to manage access and the project itself.

AVAILABILITY

The new model is available now for newly created organizations and will roll out to existing organizations soon.

Access works in two layers. When both apply, a user keeps the higher level of access:

• Organization roles set a baseline across every project. There are now four: Admin (full control), Editor (work in every project, but can't delete or transfer them), Viewer (read-only), and Collaborator (no access until granted specific projects).
• Per-project permissions raise that baseline on specific projects. Grant a member Viewer (read-only), Editor (connect, query, and edit resources), or Admin (manage access, settings, and the project lifecycle) on any project from Settings → Project permissions.

For example, give a contractor the Collaborator role, which grants nothing by default, then Editor on just the two projects they work on. Or give a teammate Viewer across the organization and Admin on the one project they own.

You can manage the same access through the Neon API, so an orchestrator can provision a project and grant a worker agent scoped access to it:

curl --request PUT \
  --url 'https://console.neon.tech/api/v2/projects/{project_id}/members/{member_id}/role' \
  --header 'authorization: Bearer $ORG_API_KEY' \
  --header 'content-type: application/json' \
  --data '{"role": "editor"}'

The CLI doesn't have a dedicated command yet, but you can call the same route with the neon api passthrough.

What changes for existing organizations

When your organization is migrated, it moves to the new model automatically, and everyone keeps the access they have today. No action is required:

• Admins stay Admins.
• Members become Editors, with the same access under the new name.
• Project creators become Admin on the projects they created.
• People with project-share access become Editor on the projects shared with them.

The older project collaboration feature is being replaced by the new Collaborator role plus per-project permissions.

See User permissions for roles, per-project levels, and how the two layers combine.

New guides for building on the Neon backend

Two new guides show how to combine the Neon backend services, from long-running compute to LLM access, all in a single project that branches with your data:

• Build durable background workflows with Inngest and Neon Functions: run a multi-step lead-enrichment pipeline on Neon Functions, with each step checkpointed so a failure retries just that step, and an executive summary generated through the Neon AI Gateway.
• Build an LLM proxy with Neon Functions, Neon AI Gateway, and Managed Better Auth: host a secure proxy on Neon Functions that keeps your LLM keys off the browser, authenticates users with Managed Better Auth, enforces per-user rate limits in Postgres, and streams responses from the AI Gateway.

SET UP THE NEON BACKEND WITH YOUR AI AGENT

The backend services (Object Storage, Functions, and AI Gateway) are in beta in AWS us-east-2. To build with them, install the Neon agent skills so your assistant knows how to provision and wire them up:

npx neon@latest init

Then ask your assistant to get started with Neon. See the backend beta guide for access and setup.

More with Lakebase Search

Lakebase Search adds scalable vector, keyword, and hybrid search to Postgres through the lakebase_vector and lakebase_text extensions. This week, two new resources show it in action:

• Case study: CommSync runs text, vector, and hybrid search on Postgres with Lakebase Search. See how a unified business inbox powers its main inbox (BM25 text search), AI assistant (semantic search), and command palette (hybrid search with Reciprocal Rank Fusion) from a single database, cutting query latency from 19.5 seconds to 18.6 milliseconds.
• Guide: Build image search over CLIP embeddings with Lakebase Search. Search a Flickr30k corpus by text, by image, and by caption from one vector(512) column, using the lakebase_ann index (IVF + RaBitQ) that builds 50 to 100 times faster than HNSW.

To get started, load the Lakebase Search preload libraries, then create the extensions:

CREATE EXTENSION IF NOT EXISTS lakebase_vector CASCADE;
CREATE EXTENSION IF NOT EXISTS lakebase_text CASCADE;

Fixes & improvements

Spending notifications

Neon MCP Server

Drizzle Studio

Original source

Debug Postgres from the terminal with neon inspect db

You can now run read-only Postgres diagnostics straight from the Neon CLI with neon inspect db. Each subcommand runs a single, known-good query against Postgres' own statistics and catalog views, then prints a clean table (or JSON/YAML for scripting).

The diagnostics cover table and index sizes, unused indexes, sequential scans, long-running queries and locks, heavy and frequent statements, cache hit rate and working set, autovacuum and bloat, and replication state.

This helps you understand why a branch is slow or large without writing catalog SQL by hand.

See the documentation for neon inspect db for details and examples.

Original source

Debug Postgres from the terminal with neon inspect db

You can now run read-only Postgres diagnostics straight from the Neon CLI with neon inspect db. Each subcommand runs a single, known-good query against Postgres' own statistics and catalog views, then prints a clean table (or JSON/YAML for scripting). There's no connection string to assemble and no catalog view to recall: the CLI resolves the endpoint, role, password, and database through the same Neon API the SDK uses, so you name a diagnostic and go.

NEW TO THE NEON CLI?

Install it with npm install -g neon, then authenticate with neon auth. See the install guide and CLI quickstart to get going.

Fourteen subcommands cover the questions you actually ask when something is slow, grouped by what you're chasing:

• Size and storage: table-sizes, index-sizes, bloat
• Indexes and scans: unused-indexes, seq-scans
• Live activity and contention: long-running-queries, locks
• Query workload: outliers, calls (from pg_stat_statements)
• Maintenance: vacuum-stats
• Replication: replication-slots, subscriptions
• Neon cache debugging: lfc-hit-rate, working-set

Every command is read-only, scoped to the columns that answer the question, and capped where results can get large. That makes it as safe to hand to an agent as it is to run yourself. Point it at a linked project, or at any Postgres database with --db-url:

neon link # or: neon set-context --project-id <project-id>
neon inspect db bloat

neon inspect db outliers --db-url postgres://<user>:<password>@<host>:5432/<dbname>

See the neon inspect reference for the full command reference, and read the deep dive on our blog.

Manage snapshots from the Neon CLI

The Neon CLI now has a first-class neon snapshots command group. Snapshots are point-in-time backups of a branch, and they were previously only available in the Console and REST API. You can manage the full lifecycle from your terminal:

• neon snapshots list and neon snapshots get to see your snapshots.
• neon snapshots create to snapshot a branch, optionally at a point in time with --timestamp or --lsn.
• neon snapshots update and neon snapshots delete to rename, re-expire, or remove a snapshot.
• neon snapshots restore to restore a snapshot into a branch, with a preview step so you can inspect the result before running neon snapshots finalize to commit it.

For example, snapshot a branch before a risky migration, then restore it into a new branch if you need to roll back:

neon snapshots create --branch main --name pre-migration
neon snapshots list
neon snapshots restore pre-migration --name recovered

You can also view and set a branch's automatic backup schedule with neon snapshots schedule get and neon snapshots schedule set. Automated backup schedules are available on paid plans, except for the Agent plan. See the neon snapshots reference for the full list of subcommands.

Create projects with more control from the CLI

neon projects create now accepts flags to configure a project up front: choose the PostgreSQL version, create protected branches, and enable logical replication.

neon projects create --name my-app --pg-version 17
neon branches create --project-id <project-id> --name production --protected
neon projects update <project-id> --enable-logical-replication --yes

See the neon projects reference for the full list of flags.

Query Functions and Storage logs from the Neon MCP server

Functions and Object Storage are core pieces of the Neon backend: serverless compute and S3-compatible storage that branch with your database in the same project. You can now query logs from both services directly through the Neon MCP server, so your AI assistant can investigate a failure without leaving your editor. Three new read-only tools make up the observability category:

• query_logs: filter logs by source, service, severity, or a text match over a time window (or drop down to raw LogQL for full control).
• list_log_fields: discover the fields you can filter on.
• list_log_field_values: list the values a field takes, to ground your filters.

Once the MCP server is connected, ask your assistant in plain language:

Why did my function error in the last hour? Check the logs.

The same logs are documented under Neon Functions logs and object storage logs.

New guides for building on the Neon backend

Two new guides show how to build on the Neon backend, from declaring your services to shipping a real app:

• Manage Neon projects with neon.ts: use Neon's native TypeScript configuration to provision Postgres, Managed Better Auth, and the Data API, manage branch compute, and generate type-safe environment variables, all from one file that branches with your data.
• Build a Discord bot with Neon Functions and Neon AI Gateway: put Functions and the AI Gateway to work in a single project, with AI chat and image generation hosted next to your database.

SET UP THE NEON BACKEND WITH YOUR AI AGENT

The backend services (Object Storage, Functions, and AI Gateway) are in beta in AWS us-east-2. To build with them, install the Neon agent skills so your assistant knows how to provision and wire them up:

npx neon@latest init

Then ask your assistant to get started with Neon. See the backend beta guide for access and setup.

Original source

Neon backend for apps and agents is now in beta

Neon Object Storage, Functions, and AI Gateway have graduated from private preview to beta. Everyone can start building a complete backend on new or existing projects in AWS US East (Ohio) today.

Declare your whole backend in one neon.ts file, and it branches with your data. Fork a branch and you get an isolated copy of your database, files, functions, and gateway.

Object Storage

S3-compatible object storage that branches with your database.

Functions

Long-running serverless compute that runs alongside your database.

AI Gateway

One API for frontier and open-source models, built into your project.

New to the Neon backend? Start with the beta guide, see how the pieces fit together, or build one end to end with the full backend quickstart. For the vision behind the platform, read the announcement blog post.

ONE-SHOT YOUR BACKEND WITH AN AI AGENT

Install the beta agent skills:

npx neon@latest init --preview

Then build your backend from a single prompt:

Set up a Neon backend for my app with Postgres, object storage, functions, and AI gateway

Your agent provisions the services, declares them in neon.ts, and wires them into your app.

New TypeScript SDK for the Neon API

We're introducing @neon/sdk 1.1, the best way to work with the Neon API from TypeScript. It's fetch-based, zero-dependency, and generated from our OpenAPI spec, with an ergonomic layer on top. It covers the whole Neon Platform API: projects, branches, databases, and our new backend services (Object Storage, Functions, and AI Gateway). It replaces @neondatabase/api-client as the recommended client, though the legacy package still works.

The ergonomic layer matters most for the multi-step provisioning workflows that might take you or your agent a few attempts to get right (for example, create a project, wait for it to be ready, then create a branch and hand back a connection string).

createNeonClient({ apiKey }) gives you namespaced methods (neon.projects, neon.storage, neon.functions, neon.aiGateway, and more), typed { data, error } results, and workflow helpers like createAndConnect. Any method takes { waitForReadiness: true } to block until provisioning finishes, and a raw layer exposes every endpoint.

Read the announcement blog post for the full story, or see the TypeScript SDK documentation and migration guide for setup, API reference, and moving from @neondatabase/api-client.

Passkey support

You can now sign in to Neon with a passkey instead of a 2FA code. Add a passkey from Account settings and use your device's built-in biometrics, like Touch ID or Windows Hello, or a security key to verify it's you. Passkeys satisfy organization-level 2FA requirements, so admins can let members enroll in either 2FA or a passkey to comply. See Manage your Neon account for setup steps.

Git-style diffs in the Neon CLI

New neon diff command

We've added a top-level diff command to the Neon CLI, letting you (and your agents) quickly see schema changes between your current branch and any other branch you specify. It fits into a branch-first development workflow alongside neon link, neon checkout, neon status, and neon deploy.

1. neon link: link to a Neon project
2. neon checkout dev-1: create/checkout a dev branch
3. Do the dev work
4. neon diff main: sanity check the schema changes made against main

Want your agents to use neon diff? Install the Neon agent skills so your assistant has current knowledge of the CLI and reaches for the command on its own:

npx neon@latest init

Config commands now show the same diff

neon.ts is the TypeScript config file that declares your Neon backend: which services are on (Postgres, Auth, Data API, Object Storage, Functions) and your branch settings (compute size, TTL, protected). The config commands reconcile that file with what's actually live:
neon config plan previews the changes,
neon config apply makes them, and
neon deploy applies and provisions in one step.

These commands now report their changes as a git diff instead of tables so you can see exactly what will change before you confirm:

If apply finds a setting that already differs on the branch, it shows the current value too and stops without changing anything until you re-run with --update-existing.

New NAT gateway IPs and VPC endpoint services in US East (Ohio), Europe (London), and Asia Pacific (Singapore)

We've expanded infrastructure capacity in the AWS US East (Ohio) (us-east-2), Europe (London) (eu-west-2), and Asia Pacific (Singapore) (ap-southeast-1) regions with new NAT gateway IP addresses and new VPC endpoint service addresses for Private Networking.

UPDATE YOUR IP ALLOWLISTS

If you have IP allowlists on external systems that Neon connects to, update those allowlists to include the new NAT gateway addresses. Connections may be affected intermittently if traffic routes through non-allowlisted NAT gateways.

If you use Private Networking in these regions, you can now use the additional VPC endpoint service addresses for enhanced capacity and reliability. See the Regions documentation for the complete list of NAT gateway IPs and the Private Networking guide for VPC endpoint service addresses by region.

Original source