São Paulo AWS region now generally available 🇧🇷

Neon is now generally available in AWS's São Paulo region (sa-east-1). Create projects in the São Paulo region for lower latency access from South America and to keep your data within Brazil.

See all our supported Regions.

Transfer projects between organizations 🔄

You can now transfer projects from one organization to another directly from the Neon Console. Organization admins can move projects to any organization they're a member of, making it easier to manage projects across different organizations.

Transfer between organizations

See Transfer projects to an organization to learn more.

Create users directly from Neon Auth

Following last week's Neon Auth Beta release, we've now added the ability to create new users directly from the Neon Console. Add test users to your project without leaving your database environment — get started trying out Neon Auth with users right away.

Create user in Neon Auth

See About Neon Auth to learn more.

Manage your database from Cline or Windsurf

Following last week's guides for Cursor and 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.

Neon MCP server on cursor

Learn how in these new guides:

Scheduled updates for Business plan accounts

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

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

Updates for Business plan accounts will start rolling out next week. You can check for updates notices and choose a preferred update window — learn how.

Paid plan updates UI

Computes larger than 8 CU or configured to scale beyond 8 CU are not updated automatically.

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

Early Access Program now available for organizations 🔓

Organization admins can now enable Early Access for their entire organization. Once enabled, all organization members can preview upcoming Neon features across their organization's projects.

Early Access settings for organizations

Read more about the Early Access Program.

Postgres version updates

We updated supported Postgres versions to 14.17, 15.12, 16.8, and 17.4, respectively.

When a new minor version is available on Neon, it is applied the next time your compute restarts (for any reason). For more about how we handle Postgres version upgrades, refer to our Postgres version support policy.

Fixes & improvements

  • Neon Console

    • Improved concurrent operations in Console

      Recent improvements to concurrency handling in the API are now reflected in the Console. Buttons and controls are only disabled when strictly necessary, making it easier to work with multiple branches and endpoints simultaneously.

    • Restricted Neon Auth installation and removal to organization admins only

  • Drizzle Studio update

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

  • API Updates

    Updated the @neondatabase/api-client package to include Neon Auth API endpoints

  • Neon serverless driver

    Updated dependencies in the Neon serverless driver to address security advisories. If you use the driver in your applications, we recommend updating it to the latest version.

  • Fixes

    • Fixed performance issues with database and role operations by preventing duplicate API requests
    • Improved the Restore UI to preserve your selections when switching between restore options
    • Fixed an issue where connection strings could show the postgres role instead of Neon's neondb_owner when working with migrated databases
    • Fixed inconsistent storage usage reporting for free tier accounts, ensuring the Billing page now correctly shows total storage usage instead of GB-months