Changelog

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.

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.

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:

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.

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:

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.

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.

Postgres extension updates

Now available on Postgres 17:

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

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:

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.

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:

Read Replicas on the Free Plan

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

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:

• Neon Read Replica documentation
• Blog: The problem with Postgres replicas
• Case Study: Neon Read Replicas in The Wild: How BeatGig Uses Them

Postgres extension updates

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

Now available on Postgres 17:

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

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:

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.

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.

Postgres extension updates

We added support for the following extensions to Postgres 17.

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.

10x-ing Projects on the 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.

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 Dashboard 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 (@neon/toolkit on JSR). 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.