Changelog

Neon Auth is here! Get authentication in a couple of clicks

After a successful Early Access period, Neon Auth is now available in Beta to all users! Set up authentication for your application without writing integration code — Neon Auth automatically syncs user profiles from your auth provider straight to your Neon database.

What you get:

• Query user profiles directly from your database using the neon_auth.users_sync table
• Use our complete API to create integrations automatically, add users, and transfer ownership
• Get up and running with a pre-configured Stack Auth project that Neon manages, with the option to transfer it to your Stack Auth account later

Get started:

• Set up your auth integration in the Neon Console with our Quick Start or connect your existing Stack Auth project
• Explore our sample Todo app showing Neon Auth with Drizzle ORM
• Check out the documentation for full details

Currently supporting Stack Auth, with more providers planned.

Private Networking is generally available

Neon's Private Networking feature, which enables secure database connections via AWS PrivateLink, is now generally available and self-serve. This feature keeps traffic between your client application and Neon database within AWS's private network, bypassing the public internet.

This feature is available on our Business and Enterprise plans, but if you're on our Launch or Scale plan and want to try it out, you can request a trial from your Neon organization Settings page.

The GA release includes Neon API and CLI support for self-serve setup and management of Private Networking. See our Neon Private Networking guide for details.

Database Branching for Vercel Preview Environments

For users who come to Neon through Vercel — the Neon Postgres Native Integration, available from the Vercel Marketplace, now supports database branching for preview environments. You can now configure your integration to automatically create a dedicated database branch for each Vercel preview deployment. This lets you preview your application and database changes together without touching your production database or setting up a separate development database. To get started, see Vercel Native Integration Previews.

Active Queries and Query History views open to all

The Active Queries and Query History views in the Neon Console are now out of Early Access and available to all users. You can find them on the Monitoring page in your Neon project.

• The Active Queries view displays up to 100 currently running queries for the selected Branch, Compute, and Database.
• The Query History view shows the top 100 previously run queries for the selected Branch, Compute, and Database. Queries can be sorted by Frequency or Average time.

For more about these views, see Monitor active queries and Monitor query history.

Scheduled updates for Launch, Scale, and Business plans

A few weeks ago, we announced scheduled updates for Neon, which include Postgres version upgrades, security patches, and Neon feature enhancements.

Updates, which take only a few seconds, are applied at the scheduled time or the next time your compute restarts.

Updates for Launch and Scale Plan users will start rolling out next week. You can check for updates notices and choose a preferred update window — learn how.

Business plan users can expect update notices to start appearing next week on the Updates page shown above. We aim to provide 7 days' notice for updates on paid plans. Please select a preferred update window — learn how.

We also support checking for update notices and setting update windows programmatically using the Neon API.

For more information about updates, see our Updates documentation. If you have questions, please reach out to us on Discord or contact Neon Support.

Manage your database from Cursor or Claude Desktop

You can now manage your Neon database directly from Cursor or Claude Desktop using natural language, made possible by the Neon Model Context Protocol (MCP) Server.

Learn how in these new guides:

• AI-assisted database migrations with Cursor and Neon Postgres MCP Server
• Getting started with Neon Postgres MCP server with Claude Desktop

Chat with Neon AI while you code

In case you missed it, Neon now offers Copilot Chat extensions for GitHub and VS Code.

Install them now:

• GitHub
• VS Code.

Currently, the extensions support chatting with the Neon documentation. Support for operations like creating branches, creating databases, and running migrations is coming soon.

Fixes & improvements

• Neon Console

  • Replaced the Project creation page in the Neon Console with a simplified project creation modal.
  • Added placeholder support to the Projects page in the Neon Console to indicate when projects are still loading into the list view.
  • The Tables page in the Neon Console is powered by a Drizzle Studio integration. You can now check the Drizzle Studio integration version in your browser by inspecting the Tables page. For example, in Chrome, right-click, select Inspect, and go to the Console tab to view the current Tables version. You can cross-reference this version with the Neon Drizzle Studio Integration Changelog to track enhancements and fixes.

• Go SDK

  • A new version of the community-developed Neon Go SDK (v0.13.0) has been released. Thank you @kislerdm.

• Neon Postgres Previews Integration for Vercel

  • Addressed an issue where Vercel preview deployments would be canceled if environment variables in Vercel were already set with the correct values.

• Fixes

  • Fixed an issue on the Integrations page in the Neon Console where checkboxes on the Settings tab in the Vercel integration drawer did not update when toggled.

London AWS region now generally available 🇬🇧 ❤️

Neon is now generally available in AWS's London region (eu-west-2). Create projects in the London region for lower latency access from the UK and to keep your data within the United Kingdom.

See all our supported Regions.

Datadog integration now generally available 🎉

Our Datadog integration has graduated from beta and is now generally available for Scale and Business plan users. The integration lets you monitor your Neon database performance, resource utilization, and system health directly from Datadog's observability platform.

Learn more about setting up the integration and available metrics in our Datadog integration guide.

Inbound Logical Replication is also GA 🔄

Inbound logical replication (replicating data to Neon), where Neon is configured as a subscriber in a Postgres logical replication setup, is now GA. This feature lets you perform live data migrations to Neon from external Postgres sources such as AWS RDS, Aurora, Google Cloud SQL — or any other platform running Postgres. To try it out, get started with one of our Logical Replication Guides.

MAX connection limit added to Connections graph

We've enhanced the Connections count graph in the Monitoring page to display your compute's maximum connection limit. This makes it easier to visualize how many connections you're using relative to your compute's capacity.

The new MAX line shows your connection ceiling based on your compute size, helping you:

• Monitor connection usage relative to your limit
• Make informed decisions about implementing connection pooling

For more details about monitoring connections, see Monitoring.

Neon Auth improvements for Early Access users

We've made several enhancements to Neon Auth during the Early Access period:

• Neon-managed Stack Auth: You can now automatically provision a pre-configured Stack Auth project with recommended security settings
• Post-setup guidance: Added real-world examples showing how to relate user data with the rest of your application
• Schema improvements: Updated the users_sync table schema to include an updated_at field for better tracking of synchronization status
• Transfer ownership: For Neon-managed Stack Auth projects created using the Quickstart option, you can later decide to transfer ownership to your own Stack Auth account, at any time.

For Early Access users already using Neon Auth, these improvements make it easier to get started. Join our Early Access Program to try Neon Auth, or read the docs to learn more.

Scheduled updates for Launch & Scale accounts

A few weeks ago, we announced scheduled updates for Neon, including Postgres version upgrades, security patches, and Neon feature enhancements.

Updates, which take only a few seconds, are applied at the scheduled time or the next time your compute restarts.

Launch and Scale Plan users will start seeing update notices early next week. We aim to provide 7 days' notice for updates on paid plans. You can choose a preferred update window — learn how.

We also support checking for scheduled updates and configuring update windows programmatically using the Neon API.

We plan to introduce scheduled updates for Business and Enterprise accounts toward the end of this month.

For more information about scheduled updates, see our Updates documentation. If you have questions, please reach out to us on Discord or contact Neon Support.

Fixes & improvements

• Neon Console

  • Improved the restore branch dialog by adding text wrapping for long branch names to avoid horizontal scrolling
  • Fixed an issue where the Metrics tab in the Monitoring section would remain in a perpetual loading state

Monitor queries in the Neon Console

Currently available to members in our Early Access Program, you can now monitor your active queries and query history from the Monitoring page in your Neon project.

• The Active Queries view displays up to 100 currently running queries for the selected Branch, Compute, and Database.
• The Query History view shows the top 100 previously run queries for the selected Branch, Compute, and Database. Queries can be sorted by Frequency or Average time.

For more about these new monitoring options, see Monitor active queries and Monitor query history.

Save your connection details to 1Password

If you've got the 1Password browser extension, you can now save your database connection details to 1Password directly from the Neon Console. In your Project Dashboard, click Connect, then click Save in 1Password.

Renamed Neon Authorize to Neon RLS Authorize

We've renamed our JWT-based authorization feature to Neon RLS Authorize to better reflect its core value: connecting your authentication provider's JWTs with Postgres Row-Level Security (RLS) policies. You can now find this feature under Settings > RLS Authorization in the Neon Console.

Learn more about Neon RLS Authorize or try our tutorial.

Renamed Neon Identity to Neon Auth

We've also renamed our Early Access auth integration feature to Neon Auth. Neon Auth lets you automatically sync user profiles from your authentication provider to your database. Learn more about it in Neon Auth.

Or sign up to the Early Access Program to try it out.

Scheduled updates on Free & coming soon to Launch and Scale

Two weeks ago, we announced scheduled updates for Neon, including Postgres version upgrades, security patches, and Neon feature enhancements.

This week, we introduced the Updates page in your Project Settings. Free Plan users get update notices 24 hours in advance. Updates, which take only a few seconds, are applied at the scheduled time or the next time your compute restarts.

Launch and Scale Plan users will start seeing update notices in another week or so. We aim to provide 7 days' notice for updates on paid plans. Paid users can also choose a preferred update window — you can do that now, well ahead of any planned updates.

We also support checking for scheduled updates using the Neon API.

For more information about scheduled updates, see our Updates documentation. If you have questions, please reach out to us on Discord or contact Neon Support.

Fixes & improvements

• Postgres extension updates

  We updated the pg_mooncake extension version to 0.1.1.

  If you installed this extension previously and want to upgrade to the latest version, please refer to Update an extension version for instructions.

• Time Travel connections

  Ephemeral computes, used for Time Travel connections, now use a compute size of 0.50 CU (0.50 vCPU, 2 GB RAM). This is up from the 0.25 CU size used previously. For more, see Time Travel — Billing considerations.

• Console updates

  • We've updated the Usage section on the Billing page to make it easier to track your plan allowances, extras, and total usage.
  • The Schema-only branch option on the Create new branch modal is now disabled when you reach the root branch limit for your project. For details, see Schema-only branches allowances.

• Support for CREATE ROLE ... NOLOGIN

  Neon now supports creating Postgres roles with the NOLOGIN attribute. This allows you to define roles that cannot authenticate but can be granted privileges.

  CREATE ROLE my_role NOLOGIN;

  Roles with NOLOGIN are commonly used for permission management.

  Support for NOLOGIN was also extended to the Neon API and CLI:

  • The Neon API Create role endpoint now has a no_login attribute.
  • The Neon CLI neon roles create command now supports a --no-login option.

• CLI support for schema-only branches

  We added CLI support for our recently introduced schema-only branches feature. You can now create a schema-only branch from the CLI using the --schema-only option with the neon branches create command.

  neon branches create --schema-only

• Branch archiving

  Neon now limits each project to 100 unarchived branches. Branches older than 14 days and inactive for more than 24 hours are automatically archived to cost-efficient storage. No action is needed to unarchive a branch—it happens automatically when accessed, usually without noticeable performance impact. If you exceed the 100-unarchived branch limit, Neon will archive branches more quickly to stay within the limit. To learn more, see Branch archiving.

• Vercel Native Integration

  Fixed an authentication issue that prevented creating another user from a Vercel team in Neon.

• Vercel Previews Integration

  • The Neon Vercel Previews Integration now supports deployments to Vercel custom environments. However, automated branch deletion does not remove environment variables created by the Neon integration in custom environments. These variables must be deleted manually in the Vercel dashboard.
  • Fixed an issue where preview deployments in Vercel custom environments were incorrectly recreated in the preview environment instead of the intended custom environment. Additionally, addressed a problem where preview deployments triggered via the Vercel CLI failed to be recreated due to missing Git information in the Get Deployment API response. Deployments now correctly redeploy when Git information is unavailable.
  • For Neon branches created for Vercel preview deployments, we now show the Vercel preview deployment URL and the associated GitHub pull request on the Branches page in the Neon Console.

• Fixes

  • Resolved an issue where the System operations tab on the Monitoring page could display system operations from more than one project when switching between projects.
  • Resolved an issue where the branches list in the Neon Console did not immediately update after restoring a branch.
  • Fixed a time format issue on the project settings Updates page where displayed time values were inconsistent, with one shown in UTC and another in local time.
  • Fixed an issue related to resetting account passwords and changing account emails.
  • Fixed a concurrency issue where two branches created from the same parent in close succession collided. Previously, the operations on the parent did not complete fast enough for both create branch operations to work.
  • Fixed an email validation issue on the Feedback form in the Neon Console.
  • Fixed an issue in the Neon SQL Editor where the compute status in the compute drop-down menu remained Idle after running a query.

The Neon Slack App is available for early access

The Neon Slack App helps you stay connected to your Neon Serverless Postgres databases. Here's what you can do with it:

• 📈 Track compute and storage usage in real time
• 🔔 Get alerts when your database approaches its performance limits
• 🟢 Quickly check the Neon platform's status

We’d love to hear your feedback. Use the /neon feedback command in Slack to share your thoughts and feature requests.

👉 See the documentation for setup instructions.

Scheduled updates on the Free Plan starting soon

Last week, we announced that Neon is introducing scheduled updates, starting with Free Plan accounts. These updates include Postgres version upgrades, security patches, and Neon feature enhancements. Your project's computes will be updated automatically at a scheduled date and time. While updates need a compute restart, it only takes a few seconds to complete.

Free Plan accounts will start seeing update notices in their projects' settings on a new Updates page in early February, at least 24 hours before any scheduled update.

Update notices for Neon's paid plans will start rolling out in the second week of February, with at least 7 days' notice before a planned update.

Stay tuned for more details.

Protect sensitive data with schema-only branches

You can now create schema-only branches that copy just the database schema from a source branch — without any data. This is ideal for working with confidential information. Instead of copying sensitive data, create a branch with just the database structure and add your own randomized or anonymized test data. It's a secure and compliant way for your team to develop and test using Neon branches.

To learn more, see Schema-only branches.

Schema-only branches are currently available through our Early Access Program. Learn how to join.

Project-scoped API keys from the Console

Recently, we added support for project-scoped API keys for your Neon Organization. These keys provide member-level authorization, scoped to a particular project. First available only via API, you can now create them from the Neon Console as well, for better visibility and management.

Learn more about creating project-scoped API keys.

Support for the postgres_fdw extension

Neon now supports the postgres_fdw (foreign data wrapper) extension. This extension lets you integrate with remote Postgres databases by defining foreign tables that map to tables in external databases. You can then query remote data as if it were stored locally. Check out our guide to learn more.

pg_cron is now available for all users

The pg_cron extension is now available to everyone using Neon. Before, you needed a paid plan and help from Neon Support to use it. See Enable the pg_cron extension to get started.

Fixes & improvements

• Drizzle Studio update

  We updated the Drizzle Studio integration that powers the Tables page in the Neon Console to version 1.0.12. For the latest improvements and fixes, see the Neon Drizzle Studio Integration Changelog.

• Console updates

  Added a clear banner in the SQL Editor's results pane when running Time Travel queries to show that you're viewing historical data.

  

• Postgres extension updates

  • Neon now lets you install the previous version of pgvector, which is one version behind the latest supported version.

    For example, if Neon’s latest supported pgvector version is 0.8.0, you can install the prior version, 0.7.4, by specifying the version number:

    CREATE EXTENSION vector VERSION '0.7.4';

    For more, see Use a previous version of pgvector.

  • The pgx_ulid extension (0.2.0) is now available for Postgres 17. To install it, run:

    CREATE EXTENSION pgx_ulid;`

• Neon API

  Newly created Neon API keys are now prefixed with napi_. This change improves security by making it possible to use secret scanning mechanisms that rely on identifiable markers.

  Existing API keys remain valid. If you want to use the new format, you can generate a new API key. For instructions, see API keys.

• Fixes

  • Fixed a bug where you might see an empty error screen when changing your email or resetting your password.
  • Fixed an issue where the SQL Editor sometimes ran queries on the main branch instead of your selected branch.

Neon Chat for Visual Studio Code

The Neon Chat for Visual Studio Code extension is now available in the GitHub Marketplace. This AI-powered assistant lets you chat with the latest Neon documentation without leaving your IDE.

Get answers to common questions like:

• How to create a project?
• How can I get started with the Neon API?
• How do I create a branch using the Neon CLI?

Scheduled updates coming soon 📅

Neon is introducing scheduled updates, starting with Free Plan accounts and later expanding to Paid Plans. These updates will cover Postgres updates, security patches, and Neon feature enhancements, automatically applied to your project's computes. Here's what to expect:

• Updates aren’t new, but now they’ll be scheduled so you’ll know when they’re coming and won't fall behind on important maintenance.
• Updates require a compute restart, but restarts are quick and automatic — taking just a few seconds.
• If your computes scale to zero & restart regularly, available updates will be applied on compute restart, removing the need for "scheduled" updates.
• You’ll be able to track scheduled updates in your project settings.
• Free Plan accounts will have updates scheduled in advance for a specific day and time, while Paid Plan accounts will be able to choose a preferred update window.

Stay tuned for specific details about when scheduled updates will roll out. Free Plan users can expect to see scheduled updates first, starting in early February. Scheduled updates on Paid Plans will roll out later, with updates for large compute sizes (> 8 CU) rolling out last.

Connect to external Postgres databases with the dblink extension

Neon now supports accessing external Postgres databases using the dblink extension. dblink lets you easily connect to other Postgres databases and run queries on them. It's a good choice for quick, one-off queries or situations where you need data from a remote database but don’t want to configure a foreign data wrapper.

Support for the pg_repack extension

The Postgres pg_repack extension is now available on paid Neon plans upon request. This extension helps you remove bloat from tables and indexes while optionally restoring the physical order of clustered indexes — all without requiring an exclusive lock during processing. This extension is currently available only on paid Neon plans. To enable pg_repack, open a support ticket and include your endpoint ID and the database name where you'd like the extension enabled.

Meet "Instagres": No signup, instant Postgres ✨

Neon's architecture lets us do some pretty interesting things, like creating a Postgres database in less than a second (AI agents loves this, btw). To showcase this ability, we've built "Instagres," an app that lets you generate a Postgres database URL almost instantly — no sign up required. If you'd like to keep the database for more than an hour, you can transfer it to your Neon account.

Give it a try at https://www.instagres.com/ or by running npx instagres in your terminal.

The "Instagres" app is powered by Cloudflare, React Router, and DrizzleORM.

If you like this feature or see different use cases for it, please let us know via the Feedback form in the Neon Console or our feedback channel on Discord.

To learn more, read the blog post.

Pooled connection strings are now default in the Neon Console

Pooled connection strings are now the default in the Connection Details widget in the Neon Console. Pooled connection strings include a -pooler option, which directs connections to a pooled connection port powered by PgBouncer. With support for up to 10,000 concurrent connections, connection pooling improves performance, reduces latency, and makes resource management more efficient for most applications. For specific tasks like pg_dump and other session-dependent operations like schema migrations, you can still get direct connection string at any time by disabling the connection pooling toggle in the Connection Details widget or by removing -pooler from your connection string manually.

A new version of the Neon Python SDK

Neon's Python SDK, which is a wrapper for the Neon API, has been updated to a new version (0.3.0). This new version updates the Python data types from Neon's API schema.

This SDK simplifies integration of Python applications with Neon by providing methods to programmatically manage Neon API keys, projects, branches, databases, endpoints, roles, and operations.

Fixes & improvements

• Drizzle Studio update

  The Drizzle Studio integration that powers the Tables page in the Neon Console has been updated to version 1.0.11. For the latest improvements and fixes, see the Neon Drizzle Studio Integration Changelog.

• Console updates

  Increased concurrency limits. Last week we announced increased Neon API operation concurrency limits on Neon's Free, Launch, and Scale plans. This enhancement is now supported on all Neon plans.

  As noted in last week's changelog: Previously, concurrent API operations within a Neon project — such as operations on different branches — could trigger a "project already has running operations" error, where one branch operation would block others. This improvement reduces the need to work around strict concurrency limits. However, we still recommend adding retry functionality to handle rare cases where an API operation fails due to ongoing operations.

  This change applies only to the Neon API. In the Neon Console, controls such as buttons that initiate new operations are still briefly disabled until ongoing operations are complete. Concurrency improvements will be reflected in the UI in a future release.

• Fixes

  Fixed an issue with the Create branch button in the Neon Console. Previously, the button became disabled for unfinished project operations, including those that failed due to an error. Now, the button is disabled only for project operations in the canceling, running, or scheduling state.