Learn how Neon compares to Aurora Serverless v2 - TL;DR: faster cold starts, responsive autoscaling, 80% lower costs

Changelog

The latest product updates from Neon

RSS feed

Neon is Now Available as an Azure Native Integration

If your company uses Azure, getting started with Neon is now easier than ever. This week, we launched Neon as an Azure Native Integration, enabling developers to deploy Neon Postgres databases directly from the Azure portal.

With this new integration, you can:

  • Provision and manage Neon organizations directly within Azure, using the Azure portal, CLI, or SDK.
  • Access Neon with your Microsoft credentials for simplified security and compliance.
  • Include Neon charges in your Azure bill.

For more, read the announcement.

New Azure regions

We’ve added support for two new Azure regions:

  • Azure Germany West Central (Frankfurt) — azure-gwc
  • Azure West US 3 (Arizona) — azure-westus3

For a full list of regions supported by Neon, see Regions.

Support for database schema management in the Neon Console

Drizzle Studio Schema Management UI

The Tables page in the Neon Console, powered by Drizzle Studio, received a major update this week. In addition to managing your data, you can now manage your database schema directly from the Tables page. New schema management options include:

  • Creating, altering, and dropping schemas
  • Creating and altering tables
  • Creating and altering views
  • Creating enums
  • Refreshing the database schema

We’d love to hear your thoughts on these new capabilities! Share your feedback through the Feedback form in the Neon Console or join the conversation on Discord.

Stay updated on Drizzle Studio improvements and fixes by following the Neon Drizzle Studio Integration Changelog.

A Model Context Protocol (MCP) server for Neon

We’ve released an open-source Model Context Protocol (MCP) server for Neon, enabling any MCP Client such as Claude Desktop to interact with Neon’s API using natural language. AI agents can use our MCP server to perform actions such as creating databases, running SQL queries, and managing database migrations. For more, read the announcement and try it out on GitHub.

Archive storage on paid plans

A few weeks ago, we announced branch archiving on the Free Plan, which automatically stores inactive branches in cost-efficient archive storage. This feature is now available on our paid plans: Launch, Scale, and Business. Here’s what this means for you:

  • More storage and reduced storage costs: Branches older than 14 days and not accessed for 24 hours are automatically archived in cost-efficient archive storage.
  • New archive storage allowances by plan:
    • Launch: 50 GB
    • Scale: 250 GB
    • Business: 2500 GB
  • Billing for extra archive storage: Extra storage beyond your plan’s allowance is billed at $0.10 per GB-month. Inactive branches meeting the thresholds above will now cost less.
  • Monitoring archive storage usage: A new archive storage metric is available on the Billing page in the Neon Console.
  • Archived branch details and identification: Archived branches are marked with an archive icon in the console. The Branches page shows additional details, including the date and time a branch was archived.
  • Automatic archiving and unarchiving: No action is needed to archive or unarchive branches. Unarchiving happens automatically when you access a branch.
  • Performance considerations: You should notice little to no performance difference when connecting to or querying an archived branch, except for branches with large amounts of data where initial access may take a little longer until the branch is fully unarchived.

For more details, see Branch archiving and Archive storage.

Simplified "extra storage"

We reduced the cost of temporarily using more storage than is in your plan's monthly allowance. Previously, if you exceeded your storage allowance, you were allocated (and billed for) an extra storage unit at a prorated price for the rest of the month, even if the overage was brief. Now, you’re billed only for the storage you use for the length of time that you use it. This will be measured per GB-month.

Fixes & improvements
  • Console updates

    • The Monitoring page graphs now display data in the local timezone instead of UTC.
    • We added sorting for columns in the branches table on the Branches page. In addition, default and protected branches are always listed first, and the table now supports full keyboard navigation, allowing users to tab through table cells and rows. New Branches Table
  • Neon Authorize

    Neon Authorize now supports verifying an aud (audience) claim in JWTs to limit access to specific applications or services. For providers like Firebase Auth and GCP Cloud Identity, which use the same JWKS URL across all projects, defining an intended audience is required.

    Configure the audience via the Neon Authorize UI or the Neon Authorize API. This enhancement adds support for Firebase Auth and GCP Cloud Identity. See Supported providers for the full list.

  • Neon API updates

  • Vercel Native Integration

    History retention and logical replication settings are now configurable in Neon projects created in Vercel-created organizations. Previously, these settings could not be modified in Neon or Vercel.

  • Vercel Previews Integration

    • Enhanced the Vercel Previews Integration drawer to make it easier to connect Neon projects to Vercel projects.
    • Updated the Vercel Previews Integration drawer to display connected Vercel projects in a more compact table view when more than three projects are connected.
  • Fixes

    • Resolved an issue that blocked Schema Diff operations when other project operations were in progress. Schema Diff operations are now serialized to prevent concurrency errors.
    • Improved the error message in the Neon SQL Editor’s text-to-SQL AI feature when it fails to fetch the database schema.
    • Fixed inconsistencies in usage metrics and project allowances displayed on the Billing page in the Neon Console.
    • Fixed an issue that allowed selecting a future date when setting a custom period on the Monitoring page.

Neon Organizations are GA! 🎉

We're happy to announce that Neon Organizations is now generally available for everyone looking to move their teams to Neon.

get started with your new org

Create a new organization, transfer over your projects, invite your team members and get started collaborating. The Organizations feature lets you manage all of your team's projects under a single account — with billing, role management, and project transfer capabilities in one accessible location.

See Neon Organizations to get started. Organizations is a paid account feature.

Organization API keys

Along with GA for Organizations, we're also announcing support for Organization API Keys. As an admin of an organization, you control your organization's API keys. These keys provide admin-level access to all organization resources, including projects, members, and billing information.

You can access your organization's API keys from your organization settings.

Organization API keys control

Schema Diff GitHub Action

We're also introducing our Schema Diff GitHub Action to automatically compare database schemas in your pull requests. The action posts schema differences as PR comments, making it easy to review schema changes during development. It's smart about updates, maintaining a single, updated comment as you push new commits and staying quiet when there are no differences to report. See Schema Diff GitHub Action for more details.

Index: neondb-schema.sql
===================================================================
--- neondb-schema.sql	Branch main
+++ neondb-schema.sql	Branch preview/pr-9-feat/add-soft-delete
@@ -111,9 +111,10 @@
     title text NOT NULL,
     content text NOT NULL,
     user_id integer NOT NULL,
     created_at timestamp without time zone DEFAULT now() NOT NULL,
-    updated_at timestamp without time zone DEFAULT now() NOT NULL
+    updated_at timestamp without time zone DEFAULT now() NOT NULL,
+    deleted_at timestamp without time zone
 );


 ALTER TABLE public.posts OWNER TO neondb_owner;
@@ -180,5 +181,5 @@
 --
 -- Name: __drizzle_migrations id; Type: DEFAULT; Schema: drizzle; Owner: neondb_owner
 --

-ALTER TABLE ONLY drizzle.__drizzle_migrations ALTER COLUMN id SET DEFAULT nextval('drizzle.__drizzle_m
\ No newline at end of file
+ALTER TABLE ONLY drizzle.__drizzle_migrations ALTER COLUMN
\ No newline at end of file

Postgres version updates

The PostgreSQL Global Development Group has released an out-of-cycle minor version update to address regressions introduced in the previous minor version update. While Neon was unaffected by these regressions, we prioritize staying up to date with the latest version. As a result, we have updated our supported PostgreSQL versions to 14.15, 15.10, 16.6, and 17.2.

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

Neon Private Networking (Public Beta)

Neon now offers Private Networking, enabling secure database connections via AWS PrivateLink. This feature keeps all traffic between your client application and Neon database within AWS's private network, bypassing the public internet.

For details, see our guide: Neon Private Networking.

Any member of an Org account can apply to participate in this Public Beta by requesting access via the Organization Settings page in the Console.

And don't forget to check out this week's fixes and improvements:

Fixes & improvements
  • Logical Replication

    Neon now automatically removes inactive replication slots (if other active slots exist) after approximately 40 hours, up from the previous 75 minutes. This change reduces the risk of unexpected slot removal. If you've implemented measures to prevent slots from becoming inactive, you can now relax those measures accordingly.

  • Neon Serverless Driver

    • Fixed an issue with insertion of Buffer and ArrayBuffer values for BYTEA fields over HTTP. Thanks to @andyjy for the fix.
    • Fixed an authentication error that occurred when passing the authToken property only on the sql function.

    For the latest improvements and fixes for the Neon Serverless Driver, refer to the Neon Serverless Driver Changelog.

  • .NET support

    We've added .NET to the list of supported connection strings for various languages and frameworks in the Dashboard. You can now find connection details for .NET in both the connection widget and the Quickstart.

    For more information on connecting to Neon with .NET, see Connect a .NET (C#) application to Neon.

  • Console updates

    • We've added a Monitor button to each listed endpoint on your Branch details page. Click the button to open the Monitoring page, displaying metrics for this endpoint.

      monitor button on endpoint item

    • Added quick compute size editing directly from the Branches page — just click the size link in the primary branch column to adjust your settings.

      branches table compute drawer

  • Fixes

    • Improved validation of API key names and Organization names: added a 64-character length limit for API key names and Org names to the API specification and improved whitespace handling in the UI.
    • The Create Organization modal now correctly displays your Personal account plan when creating a new organization. Previously, it sometimes showed the plan from an existing organization instead.
    • When transferring a project to an organization, collaborators who are organization members are automatically removed from the project's collaborator list, as they already have access through their organization membership.
    • Fixed billing page display issues with project limits and usage tracking during plan changes. Previously, some organizations saw incorrect counts and misaligned indicators.
    • Added length validation for Organization member email addresses to prevent submission of invalid values.

A new Python SDK for the Neon API

Neon has a new Python SDK, which is a wrapper for the Neon API. 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.

It's easy to install with pip:

$ pip install neon-api

Then, from Python:

from neon_api import NeonAPI

# Initialize the client.
neon = NeonAPI.from_environ() or NeonAPI(api_key='your_api_key')

# Get the current user
user = neon.me()
print(user)

For more, see Python SDK for the Neon API.

Did you know?

In addition to the new Python SDK, Neon offers a TypeScript SDK for the Neon API. There are also community-maintained SDKs available for Go and Node.js. Learn more.

A Migration Assistant to help move your data

When you're ready to move your data to Neon, our new Migration Assistant can help. All you need to get started is a connection string for your existing database.

Enter your current database connection string, and the Assistant will:

  1. Run some preliminary checks on your database.
  2. Create a Neon project that best matches your current environment.
  3. Provide pg_dump and pg_restore commands to transfer your data, pre-populated with the correct connection strings.

For more, see Neon Migration Assistant.

Neon Migration Assistant interface

note

This feature is currently in Beta. If you have feedback, we'd love to hear it. Let us know via the Feedback form in the Neon Console or our feedback channel on Discord.

Organization account support for Vercel and GitHub integrations

Our Vercel Previews and GitHub integrations are now supported on Organization accounts. In case you're not familiar:

  • The Vercel Previews Integration connects your Vercel project to a Neon database and creates a database branch with each Vercel preview deployment.
  • The GitHub Integration connects your Neon projects to corresponding GitHub repositories, letting you bring your database to your DevOps workflow.

You can now make both integrations available to your Neon organization.

timescaledb extension support for Postgres 17

We added support for the timescaledb extension, version 2.17.1, to Postgres 17.

For a complete list of Postgres extensions supported by Neon, see Postgres extensions.

And don't forget to check out this week's fixes and improvements:

Fixes & improvements
  • IP Allow

    We addressed an issue for IP Allow users connecting over VPN where an Access Denied modal appeared repeatedly on the SQL Editor and Tables pages in the Neon Console. To prevent this, we added a "Do not ask again" checkbox to allow users to silence the modal.

  • Neon API updates

    We added two new endpoints for managing Neon Organizations members:

  • Time Travel Assist

    Ephemeral compute suspend timeouts for Time Travel Assist have been increased from 10 to 30 seconds. Time Travel Assist enables querying any point in your history using temporary branches and computes, which are automatically cleaned up after use. After 30 seconds of inactivity, the branch is deleted, and the endpoint is removed.

Branch archiving on the Free Plan

On the Free plan, Neon now automatically archives any branch that is older than 14 days and has not been accessed for 24 hours.

example of an archived branch on the branches page

No action is required to unarchive a branch. It happens automatically as soon as you access the branch. This change reduces storage costs and enables us to grow our Free plan even further.

To learn more, see Branch archiving.

Postgres version updates

We updated supported Postgres versions to 14.14, 15.9, 16.5, and 17.1, 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.

And don't forget to check out this week's fixes and improvements:

Fixes & improvements
  • Collation support

    By default, Neon now uses the C.UTF-8 collation, which supports the full range of UTF-8 encoded characters. Previously, Neon used the C collation provided by libc by default. For more about collation support in Neon, see Collation support.

  • Neon API updates

  • Neon CLI enhancements

    The Neon CLI was updated to version 2.4.0. For upgrade instructions, see Upgrading the Neon CLI.

    The branches list command now shows a branch's Current State. Branch states include:

    • init - the branch is being created but is not yet available for querying.

    • ready - the branch is fully operational and ready for querying. Expect normal query response times.

    • archived - the branch is stored in cost-effective archive storage. Expect slow query response times.

      neon branches list --project-id green-hat-46829796
      ┌───────────────────────────┬──────┬─────────┬───────────────┬──────────────────────┐
       Id Name Default Current State Created At
      ├───────────────────────────┼──────┼─────────┼───────────────┼──────────────────────┤
       br-muddy-firefly-a7kzf0d4 main true ready 2024-10-30T14:59:57Z
      └───────────────────────────┴──────┴─────────┴───────────────┴──────────────────────┘

    The Updated At value was removed from the branches list command output. This value reflected internal metadata changes only and provided limited value.

  • Drizzle Studio update

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

  • Fixes

    • Fixed an issue where users who were removed from an organization got an error page when logging in to Neon. The console was incorrectly redirecting them to the organization page, which they can no longer access. Users are now directed to their personal account Projects page instead.
    • When you make changes to your first or last name in Account Settings, those changes are now immediately reflected. Previously, old values could sometimes persist until the page was reloaded.

At a glance usage metrics for paid plan users

A few weeks ago, we added at-a-glance usage metrics on the Free Plan to help users track account-level usage. This widget is now available on all Neon plans. You can find it on your Projects page in the Neon Console.

account metrics widget on all projects page

And we've added a project-level usage widget on the Project Dashboard as well, letting you know your current usage levels for the month for each individual project.

project metrics on individual project page

Postgres extension updates

Now available on Postgres 17:

ExtensionVersion
pg_jsonschema0.3.3
pg_graphql1.5.9
rum1.3.1
pg_tiktoken0.0.1

In addition, we updated the following extension versions on Postgres 14, 15, and 16:

ExtensionOld VersionNew Version
pg_jsonschema0.3.10.3.3
pg_graphql1.5.71.9

For a complete list of Postgres extensions supported by Neon, see Postgres extensions.

And don't forget to check out this week's fixes and improvements:

Fixes & improvements
  • Neon Authorize

    Neon Authorize is now supported on Postgres 17. This recently introduced feature lets you move Postgres Row-Level Security (RLS) policies into your codebase. To learn more, read the announcement or check out the docs.

  • Neon Vercel Integration

    The Neon Vercel Integration is now supported on Organization-owned projects.

  • Neon API updates

    We've introduced several new endpoints for managing Organizations in Neon. The new endpoints include:

  • Fixes

    • A previously specified query was not cleared from the Neon SQL Editor state after selecting a different query from the History list. This caused the previous query to be run instead of the newly selected query when clicking Run.

    • Resetting a child branch from an unprotected parent branch regenerated Postgres role passwords on the child branch. Passwords should only be regenerated when the parent branch is defined as a protected branch.

    • Fixed an issue on the Monitoring page where lines on the RAM and Working set size graphs overflowed the graph area.

    • Removed usage alerts from shared Neon projects. The alerts should only appear for project owners.

    • Added validation that prevents an Organization name field from being left blank when creating a new Organization.

    • Fixed an issue with the psql \help or \h commands accessible via the Neon SQL Editor. The specified help page failed to display.

      Did you know?

      The Neon SQL Editor supports psql meta-commands, which act like shortcuts for interacting with your database. If you are already familiar with using meta-commands from the psql command-line interface, you can use many of those same commands in the SQL Editor.

      To get a list of supported commands, use \?. For more info, see the meta-commands section of our Query with Neon's SQL Editor docs page.

Neon Authorize

Announced at Neon Deploy, Neon Authorize lets you move Postgres Row-Level Security (RLS) policies into your codebase. By integrating with JWT-based authentication providers like Clerk and Stack Auth, this new approach simplifies your code while tightening security. Read our announcement and learn more in the docs.

Neon Authorize Architecture

Build RAG pipelines with the pgrag extension

Also introduced at Neon Deploy, our new pgrag Postgres extension lets you create end-to-end Retrieval-Augmented Generation (RAG) pipelines in Postgres. There's no need for additional programming languages or libraries. With the functions provided by pgrag, you can build a complete RAG pipeline directly within your SQL client.

pg_mooncake Support

We're also announcing support for another new Postgres extension, pg_mooncake, brought to the community by mooncake.dev. pg_mooncake introduces native columnstore tables with DuckDB execution for fast analytics directly in Postgres. You don't need complex ETL; with pg_mooncake you keep your stack simple — Postgres and Python. Check out the blog post for a deeper dive.

And don't forget to check out this week's fixes and improvements:

Fixes & improvements
  • Neon Console enhancements

    • Improved the design and usability of our API Keys page, available under Account Settings. This is in preparation for Organization API keys – coming soon!
    • Cleaned up an issue where you could open both the Time Travel and Generate with AI popups in the SQL Editor at the same time.
    • Fixed an issue where removed members were sent to the organization page they no longer belong to when logging back in, causing an error. They now go to their personal page, as expected.
    • Added HINTS to the AI response when you run a failed query in the SQL Editor. For example, if you try to run an experimental Postgres extension like pgrag, along with the Error description, the AI response also gives the HINT: to proceed with installation, run SET neon.allow_unstable_extensions='true'
  • Neon API changes

    We've introduced a new Get active regions endpoint for retrieving a list of regions supported by Neon. The response body includes data such as the region ID, name, and the region's approximate geographical latitude and longitude.

    curl --request GET \
       --url https://console.neon.tech/api/v2/regions \
       --header 'accept: application/json' \
       --header 'authorization: Bearer $NEON_API_KEY'

Read Replicas on the Free Plan

You may have seen the announcement earlier this week: Read replicas are now available in the Free Plan.

Add read replica

If you're not familiar Neon Read Replicas, you might be interested to know that we take a fundamentally different approach by leveraging our serverless architecture. In Neon, read replicas are independent compute instances designed to handle read operations on the same data as your primary read-write compute. There's no replication or copying of data involved, allowing you to create a read replica almost instantly with no additional storage cost.

Neon's Read Replicas support a variety of use cases, including:

  • Horizontal scaling
  • Analytics and ad-hoc queries
  • Read-only data access

To learn more about Neon Read Replicas, check out these docs and articles:

Postgres extension updates

We added support for several extensions to Postgres 17, including pgvector 7.4.

create extension pgvector

Now available on Postgres 17:

ExtensionVersion
hypopg1.4.1
pg_hint_plan1.7.0
pg_ivm1.9
pg_partman5.1.0
pg_uuidv71.6.0
pgvector7.4
pgtap1.3.3
plv83.2.3
rdkit4.6.0
timescaledb2.17.0
wal2json2.6

In addition, we updated the following extension versions on Postgres 14, 15, and 16:

ExtensionOld VersionNew Version
hypopg1.4.01.4.1
pg_ivm1.71.9
pg_partman5.0.15.1.0
pg_uuidv71.0.11.6.0
pgvector7.27.4
pgtap1.2.01.3.3
plpgsql_check2.5.32.7.11
wal2json2.52.6

For a complete list of Postgres extensions supported by Neon and upgrade instructions, see Postgres extensions.

Neon SQL Editor AI features are now open to everyone

The AI-driven features in the Neon SQL Editor we opened to Early Access users a few weeks ago are now available to everyone. In case you missed that announcement, here's what's new:

  • SQL generation: Convert natural language requests to SQL with ease. Press the ✨ button or use Cmd/Ctrl+Shift+M, type your request, and the AI assistant will generate the corresponding SQL. It’s schema-aware, so you can reference table names, functions, and other objects in your schema.
  • Fix with AI: When your query returns an error, click Fix with AI next to the error message. The AI assistant will analyze the issue, suggest a fix, and update the SQL Editor so you can run the query again.
  • AI-generated query names: Queries in the Neon SQL Editor's History are automatically assigned descriptive names. This feature helps you quickly identify and reuse previous queries.

To learn more, see Neon SQL Editor AI features.

Easier User to Org account conversion

We've introduced a new way to convert personal Neon accounts to organization accounts. Previously, this process required setting up a new organization, transferring projects, and entering billing details again. You can now convert your user account to an organization with a single action. This will instantly transfer all of your projects and billing to the new organization, with no service disruption and no changes to your connections. Your personal account will automatically switch to the Free Plan after conversion.

For more details on how to convert your account, see Convert your personal account.

And don't forget to check out this week's fixes and improvements:

Fixes & improvements
  • Neon Console enhancement

    We added a Settings option to the Account navigation sidebar in the Neon Console for easier access to personal and organization account settings. Account settings

  • Neon API changes

    • Updated the Create Project API to return a 404 error instead of a 500 error when an invalid region is specified.
    • Updated the project_id field for the Get consumption metrics for each project API. You can now specify project IDs as a comma-separated list in addition to an array of parameter values. This provides more flexibility when filtering responses by project. If omitted, the response will include all projects.
      • As an array: project_ids=cold-poetry-09157238&project_ids=quiet-snow-71788278
      • As a comma-separated list: project_ids=cold-poetry-09157238,quiet-snow-71788278
  • Fixes

    We fixed an issue with the Neon Vercel Integration where the PGPASSWORD variable in Vercel was not defined as expected after enabling branch protection on the main branch. Enabling branch protection resulted in a new password being generated for preview branches, rendering the existing PGPASSWORD setting invalid. To prevent this issue, a PGPASSWORD variable is now set for each new preview branch.

New monitoring graphs

We're continuing to improve visibility into your database performance with two new graphs on the Monitoring page: LFC hit rate and Working set size.

LFC graphs for monitoring page

working set graph for monitoring page

The Local file cache hit rate graph shows the percentage of read requests served from memory. A high hit rate indicates better performance, as more data is served from cache (faster) instead of being pulled from storage (slower). See What is the Local File Cache for more info.

The Working set size graph tracks the amount of data your database accesses over time. For best performance, your working set should fit within the LFC, minimizing slower queries that pull data from storage. See Working set size for details.

New banner for custom date range selection

Along with the new graphs on the Monitoring page, we also now added a banner to show your custom date range selection, making it a bit easier to keep track of your selected time frame when analyzing performance metrics.

custom date range selection banner on monitoring page

Postgres extension updates

We added support for the following extensions to Postgres 17.

ExtensionVersion
address_standardizer3.5.0
address_standardizer_data_us3.5.0
h34.1.3
h3_postgis4.1.3
pg_hashids1.2.1
pg_roaringbitmap0.5
pgjwt0.2.0
pgrouting3.6.2
plv83.5
postgis3.5.0
postgis_raster3.5.0
postgis_sfcgal3.5.0
postgis_tiger_geocoder3.5.0
postgis_topology3.5.0
prefix1.2.10
semver0.40.0
unit7

For a complete list of Postgres extensions supported by Neon, see Postgres extensions.

Support for removing backup branches created by restore operations

When working with branches, we recommend removing old and unused branches where possible. This helps free up disk space and keep your project organized. We’ve made that easier: you can now remove the backup branches created by restore operations on your project’s root branch (typically named main). Previously, the backup branches could not be removed.

For more details, and other recommendations, see Deleting backup branches.

Fixes & improvements
  • Added email verification for Microsoft login

    • New users signing in with Microsoft need to verify their email.
    • Existing users linking a Microsoft account will receive an email to complete the linking process.
  • Neon API change

    Removed the deprecated /consumption/projects endpoint entirely from the API.

  • Fixes

    • Fixed an issue where Free Plan users were sometimes unable to select a paid plan after their previous selection failed to register.
    • Fixed a problem with the Support form that became unresponsive when switching between Organizations.

10x-ing Projects on the Free Plan

10 projects on the Neon Free Plan

You may have seen the announcement already — Neon Free Plan users can now create up to 10 projects. We hope this increase will make it easier for you to learn a new stack, build the AI-powered app you've been thinking about, ship an MVP, upgrade to the next version of Postgres, or anything else the previous limit kept you from doing. Why did we make this change? Read all about it here: 10x-ing our Free Plan: Everyone Gets Ten Projects.

To create a new project, navigate to the Projects page in the Neon Console and click New Project.

Please note that Free Plan account-level allowances for compute hours, storage, and bandwidth remain unchanged.

Drag-to-zoom monitoring graphs

We've enhanced the graphs on our Monitoring page to support drag-to-zoom. You can now click and drag to zoom in on a selected range.

drag-to-zoom monitoring graphs

Fixes & improvements
  • Neon CLI update: We released a new version of the Neon CLI, with the following updates:

    • Fixed an issue with the login alias for the neon auth command.
    • Removed the previously deprecated set-primary primary subcommand from the branches command. It was replaced by the set-default subcommand.
    • Removed the previously deprecated --allow-list and --ip-primary-only options from the projects update command. Operations performed by these options are supported by the ip-allow command.
    • Removed the previously deprecated --primary-only option from the ip-allow command. It was replaced by the ip-allow add --protected-only option.
    • Updated the project list command to output a user-friendly message when there are no projects or shared projects to display.

    To update your Neon CLI installation to the latest version, follow our CLI upgrade instructions.

  • Create Support Ticket modal enhancements: We've made a few updates to the Create support ticket modal in the Neon Console:

    • Added a drop-down menu for selecting a personal account or organization.
    • To help resolve support cases faster, the consent option to allow Neon Support staff to connect to your database is now selected by default. You can leave this option selected or deselect it when opening a support ticket.
  • Organizations and Collaborators update: When a project collaborator is added as a member of an organization, they are now automatically removed as a collaborator from projects within that organization to avoid redundancy.

  • Neon Console enhancements: The table on the Projects page in the Neon Console now includes an Integrations column that lists your project's integrations. If there are no integrations, an Add option takes you to the Integrations page where you can view available integrations.

  • Extension update: Updated the neon extension to version 1.5 for all Postgres versions to add support for Neon-internal functions and views owned by the Neon system role.

  • Neon API change: The Delete a project endpoint now returns a 404 Not Found response instead of a 200 OK response if the project has already been deleted. This is a potentially breaking change for applications that expect a 200 OK response for all delete operations, regardless of whether a project was actually deleted.

  • Fixes:

    • Fixed an issue that prevented deleting a branch with an ephemeral compute endpoint created for performing a schema diff.
    • Fixed an issue where the GitHub integration drawer wouldn’t update after changes were made.
    • Fixed an issue in the GitHub integration that allowed connecting to the same GitHub repository from different Neon projects, which would overwrite previously configured variables.

Sign up for Neon Deploy

Join us online on October 30th at 10:00 AM PT to learn how Neon empowers developers to ship faster with Postgres. Tune in for Product updates and technical deep dives. Sign up today!

join us at Neon Deploy

Neon on Azure is open for beta

Neon on Azure is now available for public beta! Create a new project now and try it out.

azure project creation globe

More projects

Customers with database-per-tenant, developer platforms, and AI Agents told us they needed more projects: we've expanded the project limits across all paid Neon plans.

New limits:

  • Launch Plan: Up to 100 projects
  • Scale Plan: Up to 1,000 projects
  • Business Plan: Up to 5,000 projects

A reminder, last week we introduced the experimental @neondatabase/toolkit, which allows you to spin up a Postgres database in seconds and run SQL queries — ideal for quick setups and testing environments, and for taking advantage of your new, higher project limits.

ISO27110 & ISO27701 compliance

These new certifications add to our growing list of compliance achievements. For more about Neon's compliance milestones, see Compliance.

Database limits per branch

In case you missed last week's heads up — this week we've started enforcing a limit of 500 roles and 500 databases per branch. If you have any concerns about these new limits, please reach out to the Neon Support team. Previously, these limits were recommended but not enforced.

At a glance metrics for Free plan users

We're making it easier for Free Plan users to check how much room you've got left on your account-level metrics. Find it on your Projects page.

account metrics widget on all projects page

And we've also added a project-level usage widget on the Project Dashboard as well, letting you know your current consumption levels for the month for each individual project.

project metrics on individual project page

Guests are now Collaborators

We've renamed Project sharing to Collaborators in both your Project and Organization settings pages in the Neon Console. This update streamlines collaboration with other users, whether from a personal account project or with external users for Organization-owned projects.

To manage collaboration from the project level, Project → Settings → Collaborators. And to manage collaboration for all projects in your Organization, Organization → People → Collaborators.

Fixes & improvements
  • We've removed deprecated language and actions from the Neon CLI. A few months ago, we started calling your root branch default instead of primary. The CLI now reflects this change: primary is no more, it's default everywhere. For more info, see set-default.
  • Added support for organization scopes in Neon OAuth, including create, read, update, delete, and manage organization permissions. See Neon OAuth integration for details.
  • Added an account selector to let users choose between personal and organization accounts when submitting a support ticket. This prevents issues for users with both free and paid accounts.
  • Fixed a UI issue where very long parent branch names broke the layout on the Branches view.
  • Resolved an issue where paid users incorrectly received alerts for hitting their monthly compute limits.
  • Corrected a display issue on the Monitoring page where charts showed an inaccurate pattern of breaks for autoscaling computes.
Was this page helpful?