[Just launched] Neon Snapshots let you save critical database states instantly—even for multi-TB datasets
Neon DocsAsk Neon AI
DiscordLog InSign Up

Changelog

The latest product updates from Neon

RSS feed

New default project setup

New Neon projects now start with a better out-of-the-box setup to support your dev workflow.

Instead of a single main branch, you'll now get:

  • A production branch (the default), designed for your production workload. It’s configured with a larger compute size (1–4 CU).
  • A development branch, created as a child of production, intended for local development. It uses a smaller compute size (0.25–1 CU).

new project production and development branches

This new project default aligns with typical usage scenarios, where your production branch will need more compute power (vCPU and RAM) than your less active development branches—but if you need something different, you can change your branch setup or compute sizes at any time.

To learn more about integrating branching into your dev workflow, read our Database branching workflow primer.

Neon MCP Server on Zed

You can now use the Neon MCP Server on Zed, a next-generation AI-powered code editor. For setup instructions, see Get started with Zed and Neon Postgres MCP Server.

MCP support in Zed is currently in preview. You can download the preview version of Zed from zed.dev/releases/preview.

Fixes & improvements

  • Neon MCP Server

    • The Neon MCP Server previously defaulted to the neondb_owner role when no Postgres role is provided, resulting in database access failures. It now uses the owner of the selected database instead. If a non-existent role is specified, the tool fails as expected.

      If no database name is provided, the server first looks for the Neon-created neondb database; if not found, it falls back to the first available database.

  • Neon Console

    • Updated plan descriptions on the Billing page to include root branch limits for each plan.
    • Added support for enabling HIPAA for existing Neon projects. Previously, HIPAA support could only be enabled for newly created Neon projects. Neon offers HIPAA compliance as part of our Business and Enterprise plans. For details, see HIPAA Compliance.
    • Added a warning to the Edit compute drawer in the Neon Console to inform users that changing compute size settings may briefly interrupt database connections.
    • The default AWS region for new projects created in the Neon Console is now AWS US East 1 (N. Virginia), instead of AWS US East 2 (Ohio).

  • Neon API

    • Added a new Create auth user API that lets users of Neon Auth add new users to the neon_auth.users_sync table. Newly created users are automatically propagated to your auth project, whether Neon-managed or provider-owned.

    • Changed the default AWS region for new Neon projects created via the Create project API. If no region_id is specified, the default is now aws-us-east-1 (N. Virginia), instead of aws-us-east-2 (Ohio).

    • The logical_size_bytes quota in the Create project and Update project APIs sets a storage limit for each branch. Previously, exceeding this limit prevented the branch's compute from starting. Now, computes can still start even when the quota is exceeded—only write operations are blocked. This allows users to delete data and bring usage back under the limit.

      The change applies automatically when setting a new logical_size_bytes value via the Update project API, or on the next compute restart for projects with a pre-existing quota.

  • Drizzle Studio update

  • Fixes

    • Fixed an issue in the Neon Console where branches created by a deleted user account couldn't be accessed. Attempting to open the branch returned a "Request failed" error.
    • Resolved an issue on the Project Dashboard where RAM usage was incorrectly shown in GiB instead of GB.
    • Resolved an issue in the Neon Postgres Previews Integration on Vercel where branches with child branches were incorrectly marked as obsolete. The automatic branch detection logic now checks for child branches.
    • Fixed an issue in the Native Vercel integration where the wrong password was set in Vercel preview environment variables if the default branch was defined as a protected branch.

Support for Azure Service Connector

If you're using Neon on Azure, you can now connect your applications using Azure Service Connector. It simplifies connectivity by handling credentials, networking, and configuration when linking Azure services—like App Service or Azure Functions—to your Neon Postgres database.

See our guide: Connect Azure services to Neon with Azure Service Connector.

Fixes & improvements

Neon Console

  • Fixed an issue where the IP allow form wasn't updating correctly when switching between projects.
  • Fixed a scaling issue with the database size chart on the Monitoring page. The chart now accurately reflects the full data range.
  • Improved the display of email addresses in the "Created by" field of the branch list. Email addresses are now shown in lowercase, while names are capitalized as usual.
  • Improved the reliability of the AI-generated query names in the SQL Editor by handling errors silently, preventing disruptions during use.

Neon MCP Server in the cloud

We’ve brought the Neon MCP Server to the cloud. Our hosted MCP server makes it easier to integrate AI workflows into clients like Cursor, Windsurf, and Claude Desktop—no API keys or local setup required.

You can start using it today by pointing your client to:

https://mcp.neon.tech

How to try it with Cursor:

  1. Open Cursor Settings

  2. Under MCP Servers, add:

    "Neon": {
  "command": "npx",
  "args": ["-y", "mcp-remote", "https://mcp.neon.tech/sse"]
}

That’s it—you’re connected to Neon’s remote MCP Server.

We’re releasing this in preview while the MCP OAuth spec continues to evolve. Things might change, and we’d love your feedback as we improve.

📖 Read the full announcement for more info and a demo video.

New safeguards for protected branches

We added a warning and confirmation modal to the SQL Editor when running queries on protected branches. This helps prevent accidental changes to production data. You'll see a clear notice and must confirm before proceeding.

SQL Editor warnings for protected branches

Create Neon projects directly from the Azure Portal

For users of Neon on Azure — you can now create Neon projects directly from the Azure Portal. Creating a project is part of Neon Serverless Postgres resource creation. You can also add Neon projects to an existing Neon resource from a new Projects page. All Neon plans, including the Free plan, support creating multiple Neon projects.

Azure project form

Fixes & improvements

  • Neon Console

    The Computes tab on individual branch pages in the Neon Console now shows Started and Suspended labels for the primary compute, indicating when the compute was last started or suspended.

    compute started label

  • Neon API

    We added a started_at attribute to the Retrieve compute endpoint details response. This timestamp shows when your Neon compute was last started.

  • Vercel Native Integration

    New Neon projects (referred to as Databases in Vercel) now use Postgres 17 by default. Previously, projects created through the Vercel Native Integration used Postgres 15.

  • Neon App for Slack

    We've added a new /neon disconnect command to the Neon App for Slack. This command lets you remove your Neon account connection and unsubscribe from all channels while keeping the app installed for future use. You can use it when you need to switch accounts or temporarily pause notifications.

    As a reminder, you can use /neon subscribe in any channel to start receiving notifications again. The bot will guide you through any necessary setup steps.

    To install the app or learn more about all available commands, see Neon App for Slack.

  • Fixes

    Fixed an issue that caused the Tables page in the Neon Console to reload when the browser page regained focus.

Was this page helpful?

Subscribe to our changelog.
No spam, guaranteed.