Changelog

More projects on the Free Plan

Our Free plan users told us they needed more projects: we've expanded the project limits from 1 to 10.

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!

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.

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.

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

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.

Support for Postgres 17

We're excited to announce that Neon now supports Postgres 17. To start using Postgres 17, create a new Neon project and select 17 as the Postgres version. For detailed instructions, refer to our Create a project guide.

If you need to migrate data from an existing Neon project to one running Postgres 17, check out our Upgrading your Postgres version guide for supported migration options.

As always, it's important to thoroughly test before migrating production data or applications. We recommend reviewing the key changes in Postgres 17, which you can find in the Postgres Release 17 documentation.

Early Access to AI Features in Neon SQL Editor

Join our Early Access Program to try out the AI features we're testing in the Neon SQL Editor.

Explore three AI-driven features:

• 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.

A new Postgres toolkit for AI agents and test environments

We're excited to announce an experimental release of the @neondatabase/toolkit. This toolkit lets you spin up a Postgres database in seconds and run SQL queries. It includes both the Neon API Client and the Neon Serverless Driver, making it an excellent choice for AI agents that need to quickly set up an SQL database, or for test environments where manually deploying a new database isn't practical.

With a few lines of code, you can create a Postgres database on Neon, run SQL queries, and tear down the database when you're done. Here's a quick look:

import { NeonToolkit } from "@neondatabase/toolkit";

const toolkit = new NeonToolkit(process.env.API_KEY!);
const project = await toolkit.createProject();

await toolkit.sql(
  project,
  `
    CREATE TABLE IF NOT EXISTS
        users (
            id UUID PRIMARY KEY,
            name VARCHAR(255) NOT NULL
        );
`,
);

await toolkit.sql(
  project,
  `
    INSERT INTO users (id, name) VALUES (gen_random_uuid(), 'Sam Altman');
`,
);

console.log(
  await toolkit.sql(
    project,
    `
    SELECT name FROM users;
`,
  ),
);

await toolkit.deleteProject(project);

As with all of our experimental features, changes are ongoing. If you have any feedback, we'd love to hear it. Let us know via the Feedback form in the Neon Console or our feedback channel on Discord.

Neon Organizations now in Public Beta

We're happy to announce that the Neon Organizations feature is now available in Public Beta.

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.

This week’s changelog – Live from Lisbon!

Our team is in Lisbon this week, wrapping up Q3 and refining our roadmap. It's been a great opportunity to reconnect, welcome new colleagues, meet with customers, and ensure we're delivering on the features and improvements our users are asking for.

As we look ahead as a team, here's a quick look back at some key features we've released over the past few months:

• Inbound Logical Replication: Enables low-downtime migrations to Neon from other providers and between Neon projects. Check out our guides on Replicating Data to Neon and Project-to-Project Replication.
• Organizations: Now available for Early Access users. This long-requested feature allows you to create and manage your organization's projects and teams from a single account. Join our Early Access Program and refer to the Organizations docs for more information.
• Autoscaling GA: Neon's Autoscaling feature is now generally available, automatically adjusting resources as needed. Read the announcement here and explore the Autoscaling docs.
• Autoscaling on Free Plan: Free Plan users can now experience Neon's Autoscaling. Learn more in the Autoscaling Guide.
• A New Business Plan: Offers 500 GiB of storage and 1,000 compute hours, with potential cost savings for customers needing more storage than offered by our Scale plan. Learn more on our Pricing and Plans pages.

We do have a few small updates to share this week, which you can check out below.

A new Business plan with more compute and storage

We're pleased to announce that we've launched a new Business plan that provides higher storage and compute allowances (500 GiB of storage and 1,000 compute hours) in addition to all of Neon's advanced features. This plan offers potential cost savings for customers requiring more than our Scale plan provides.

To learn more about our new plan, please refer to our Pricing page and Plans documentation.

New monitoring graphs for Read Replicas

We added two new charts to the Monitoring page in the Neon Console for monitoring Read Replica replication lag. These charts are visible when selecting a Replica compute from the Compute drop-down menu.

• Replication delay bytes: Measures the total size, in bytes, of the data that has been sent from the primary compute but has not yet been applied on the replica.

  

• Replication delay seconds: Indicates the time delay, in seconds, between the last transaction committed on the primary compute and the application of that transaction on the replica.

  

For more information, see Monitoring dashboard.

A Protected Branches update

New passwords are automatically generated for Postgres roles on branches created from protected branches. You can learn more about this feature here.

Previously, resetting or restoring a child branch (where passwords were previously regenerated) reset the passwords back to those used on the parent branch. Now, when you perform a branch reset or restore operation from a protected branch, the role passwords on the child branch are preserved.

The protected branches feature is available with the Neon Scale or Business plan. To learn more, refer to our Protected Branches guide.

Autoscaling is now GA

In case you missed the announcement earlier this week, we're excited to share that Neon's Autoscaling feature is now generally available. Autoscaling has been a core objective for Neon from the very beginning. With Autoscaling, your database automatically adjusts its compute resources up or down based on demand, including scaling down to zero when not in use. This feature is now ready for production, making it easier than ever to manage workloads efficiently.

If you're not yet familiar with Neon's Autoscaling feature, you can learn more here:

• An introduction to Neon's Autoscaling
• Understanding Neon's Autoscaling algorithm
• Enabling Autoscaling

Autoscaling on the Free Plan

In addition to our Autoscaling GA announcement, we've made Autoscaling available on our Free Plan, where you can automatically scale computes from 0.25 vCPU with 1 GB of RAM up to 2 vCPU with 8 GB of RAM. To learn how, see Enabling Autoscaling.

When you try Autoscaling on the Free Plan, we recommend monitoring your monthly compute hour allowance. A compute that scales up regularly to meet demand will consume your compute hour allowance more quickly.

Postgres version updates

Supported Postgres versions were updated to 14.13, 15.8, and 16.4, respectively.

Upcoming change for branch reset and restore from a protected branch

A few weeks ago, we introduced a new protected branches feature: When you create a child branch from a protected branch, new passwords are automatically generated for the matching Postgres roles on the child branch. This helps prevent the exposure of passwords that could be used to access your protected branch. You can read more about this feature here.

Next week, we'll be making a related change, and we wanted to give you a heads-up in case any updates are needed for your CI scripts or workflows. Coming next week: When you perform a branch reset or restore operation on a child branch, the role passwords on the child branch will be preserved. Currently, resetting or restoring a child branch (where passwords were previously regenerated) resets the passwords back to those used on the parent branch.

The protected branches feature is available with the Neon Scale plan. To learn more, refer to our Protected Branches guide.

Replicating data from Neon for Change Data Capture (CDC) is now GA

Neon is pleased to announce GA support for replicating data from Neon to other data services and platforms for Change Data Capture (CDC). Define Neon as a publisher to stream data to a variety of external destinations, including data warehouses, analytical database services, messaging platforms, event-streaming platforms, and external Postgres databases. This feature is open to all Neon users. To get started, jump into one of our step-by-step logical replication guides.

Replicating data to Neon is now available in Beta

Migrate data to Neon from other Postgres providers by defining Neon as a logical replication subscriber. This feature supports near-zero downtime data migrations, continuous replication setups, and migrating data between Neon projects. Refer to our logical replication migration guides to get started.

As with all of our Beta features, improvements are ongoing. If you have any feedback, we'd love to hear it. Let us know via the Feedback form in the Neon Console or our feedback channel on Discord.

Early Access to Neon Organizations

We're also very happy to announce that Neon Organizations are now available for members of our Early Access Program.

Create a new organization, transfer over your projects, invite your team and get started collaborating. Join now to get a first look at Neon Organizations and other upcoming features before they go live.

See Neon Organizations to learn more.

Console enhancements

We've made several enhancements to the Neon Console to improve your experience and streamline your interaction with our user interface.

• You can now access Neon projects shared with you from the project breadcrumb selector in the Neon Console.
• The Billing page for Free Plan users now shows a percentage value for branch compute usage.
• We've added a new example to the Neon Console Quickstart showing how to connect to to your Neon database from NestJS. You can access the Quickstart from your Project Dashboard.
• The Primary compute column on the Branches page now shows your configured autoscaling range, replacing the Autoscales badge that was shown previously.

More CLI support for Organizations

For users of Neon's Organizations feature, which is currently in private preview, the Neon CLI projects command now supports an --org-id option, which lets you list or create projects in a specified organization; for example, you can use this command to list all projects belonging to the same organization:

neon projects list --org-id org-xxxx-xxxx
Projects
┌───────────────────────────┬───────────────────────────┬────────────────────┬──────────────────────┐
│ Id                        │ Name                      │ Region Id          │ Created At           │
├───────────────────────────┼───────────────────────────┼────────────────────┼──────────────────────┤
│ bright-moon-12345678      │ dev-backend-api           │ aws-us-east-2      │ 2024-07-26T11:43:37Z │
├───────────────────────────┼───────────────────────────┼────────────────────┼──────────────────────┤
│ silent-forest-87654321    │ test-integration-service  │ aws-eu-central-1   │ 2024-05-30T22:14:49Z │
├───────────────────────────┼───────────────────────────┼────────────────────┼──────────────────────┤
│ crystal-stream-23456789   │ staging-web-app           │ aws-us-east-2      │ 2024-05-17T13:47:35Z │
└───────────────────────────┴───────────────────────────┴────────────────────┴──────────────────────┘

Additionally, the Neon CLI set-context command now supports setting an organization context so you don't have to specify an organization ID when running CLI commands. To learn more about setting a context for the Neon CLI, see Neon CLI commands — set-context.

Postgres extension updates

The following Postgres extensions were updated to a newer version:

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

New docs navigation

We've revamped the Neon docs sidebar to enhance navigation across our documentation. The new design features a flatter structure, allowing for easier scanning and quicker access to content. Additionally, we've introduced second-level sidebars to accommodate content expansion within various categories.

If you have any feedback regarding this change, we'd love to hear it. Let us know via the Feedback form in the Neon Console or our feedback channel on Discord.

Safer project deletes

We've heard you. Where it might have felt just a little too easy to delete a project — along with its branches, databases, and roles — we've added a bit more friction to the process. You now have to type out the name of your project by hand before you can delete.

Local File Cache (LFC)-aware autoscaling

As we continue to mature our Autoscaling offering, we've rolled out LFC-aware autoscaling to all regions.

One hour of real-time autoscaling from a selection of your databases.

The idea behind this feature is to improve performance by keeping your entire working set (a subset of frequently accessed or recently used data) in memory. We already recommend this in the docs, and we've now made it a native part of how autoscaling works: your compute now dynamically resizes to fit your working set within the LFC.

If you're not familiar with Neon's Local File Cache (LFC), you can learn more about it here: What is the Local File Cache?