Neon Release Notes

More storage on the Free plan

1 GB of storage per project on the Neon Free plan

The Neon Free plan now gives you 1 GB of database storage per project, up from 0.5 GB. Existing projects pick up the new limit automatically. It was one of the most requested Free plan changes.

The extra storage builds on an already-generous plan: you get up to 100 projects on the Free plan, each with its own compute, storage, and egress. Spin up a new project for every app idea, experiment, or client demo, without paying for each project separately.

Read more in the blog post: Neon gives you 100 projects for free, with 1 GB of Postgres storage each, or see Neon plans for the full breakdown.

Embedding models in the Neon AI Gateway

The Neon AI Gateway now supports embedding models, so you can turn text into vectors through the same OpenAI-compatible endpoint and Neon credential you already use for chat. Call /v1/embeddings with either model:

import OpenAI from 'openai';

const client = new OpenAI({
  apiKey: process.env.NEON_AI_GATEWAY_TOKEN,
  baseURL: `${process.env.NEON_AI_GATEWAY_BASE_URL}/v1`,
});

const { data } = await client.embeddings.create({
  model: 'qwen3-embedding-0-6b', // or 'gte-large-en'
  input: 'The quick brown fox jumps over the lazy dog.', …

• Options to the neon(...) HTTP-client creation function, and to the transaction and query functions, now support individual connection parameters: user (or username), password, host (or hostname), port, database and connectionString.

  These can be strings (or number, for port) or sync or async functions to be resolved on every query. They can supplement, override parts of, or fully replace the first-argument connection string.

  So this still works:

  • const sql = neon(DATABASE_URL)

  But, for example, these now work too:

  • const sql = neon(DATABASE_URL_NO_PASSWORD, { password: () => getPasswordAsync() })
  • const sql = neon({ user, password, host, database })
  • const sql = neon({ connectionString: () => getConnectionString() })

• Client and Pool now support a sync or async function as the password connection parameter when pipelineConnect is enabled (this previously caused an error). And parseIntoClientConfig from pg-connection-string is exported at top-level to make it easy to use a password function alongside a connection string:

  import { Pool, parseIntoClientConfig } from '@neondatabase/serverless';
  
  const pool = new Pool({
    ...parseIntoClientConfig(process.env.DATABASE_URL),
    password: () => getDatabaseAuthToken('argument'),
  });
  

• A few other minor fixes.

• The package is no longer published to JSR. Please update any jsr references to npm:@neondatabase/serverless.

Reset a branch's Object Storage from its parent

Reset from parent now rolls back a branch's Object Storage along with its Postgres data. When you reset a branch, its buckets and objects return to the parent's current state, so any object storage uploads, overwrites, and deletes you made on the branch are also reverted.

You can reset a branch from the Neon Console, CLI, or API. See Reset from parent for the steps.

Resetting Object Storage is available now in AWS US East (Ohio) (aws-us-east-2) and AWS Europe (Frankfurt) (aws-eu-central-1), with support for additional regions rolling out soon.

Lakebase Search extensions updated

The Lakebase Search extensions are updated: lakebase_vector to 1.1.1 and lakebase_text to 0.1.3, with performance improvements and fixes. If you have them installed, upgrade when convenient with ALTER EXTENSION <name> UPDATE; see Upgrade the extension and indexes.

Note:

Building search with an AI coding assistant? The neon-postgres agent skill now includes Lakebase Search guidance for vector, full-text, and hybrid queries. Install it with:

neon skills -s neon-postgres

Automating workloads with Neon Functions …

The Neon backend is generally available

Neon started as serverless Postgres. Now you get the whole backend, and all of it branches. Every branch is a full copy, so a PR, preview, or agent session gets your entire backend, not just the database. Evolve your schema, storage, auth, and functions together on a preview branch, isolated from production.

▶️ Watch the walkthrough to see how it all fits together.

• Lakebase Postgres: 100% Postgres on the Lakebase architecture: autoscaling, scale to zero, and a branch for every PR, preview, or agent session.
• Object Storage: S3-compatible object storage that branches with your data, so files and rows stay in sync across branches.
• Auth: Managed Better Auth: users and sessions live in your neon_auth schema, queryable with SQL and protected by RLS.
• Functions: Long-running Node.js compute next to your database, now with triggers and custom domains.
• AI Gateway: One credential for frontier and open-weight models at provider prices with no markup. Buy prepaid credits to use it.
• Data API: An instant REST endpoint over your Postgres tables, no backend server required.

How to get started …

Claimable Neon: provisioned by agents, claimed by humans

Claimable Neon is for developers building with agents. When your agent is mid-build, the signup, email verification, or API key it needs to provision a database brings everything to a halt. Claimable Neon solves this problem. It lets your agent provision a temporary project with scoped credentials, without an account or payment details, and keep building. If you like the result, you can sign in later and claim the project.

# Agent: provision a claimable project (writes DATABASE_URL to .env)
neon claim create --env-pull

# Human: sign in and take ownership
neon claim accept

Today you can provision Lakebase Postgres, the Data API, and Managed Better Auth this way, with support for Object Storage, Functions, and AI Gateway coming soon.

For how it works, see the Claimable Neon docs and the launch blog post.

Give your agent Neon tools with @neon/tools …

Neon backend in Europe, plus new AI Gateway models

The Neon backend is now available in AWS Europe (Frankfurt) (aws-eu-central-1), alongside AWS US East (Ohio) (aws-us-east-2). If you build in Europe, you can now run these services closer to your users and data.

The AI Gateway catalog also gains new models, callable through the same API and key as the rest of the catalog:

• Fable 5.1
• GLM 5.3 Flash
• Grok 4.6
• OpenAI GPT-6 Astra (landing soon)

Try the Neon backend, free during the beta

Object Storage, Functions, and AI Gateway are in beta in AWS US East (Ohio) and AWS Europe (Frankfurt), and branch with your Postgres database, so your whole stack forks together.

Get started

Neon is now available in Grok Bot

Neon is now available as a plugin in Grok Bot. Connect your Neon account once, then ask a Grok bot to work with your database:

• Create a project and get a connection string for your app
• Spin up an isolated branch before testing a migration
• List projects and spot databases you no longer need
• Run SQL against your database
• Set up routines that summarize database usage …

Add Neon to your coding agent

Three new Neon CLI commands set up Neon in coding agents like Cursor and Claude Code, without manual config steps. Each runs an interactive walkthrough, or takes flags so you can script it.

neon mcp

Installs the Neon MCP Server into your agents by writing their MCP config for you. It points each agent at the hosted server, sets up authentication, and can limit which tools the agent sees. By default, it mints a Neon API key and writes it into the config. Alternativevly, pass --oauth to skip API-key creation and have the agent sign in to Neon on first use instead.

For example, install into Cursor and Claude Code with read-only tools:

neon mcp --agent cursor --agent claude-code --read-only

neon skills

Installs Neon's agent skills so tools like Cursor and Claude Code know how to work with Neon's Postgres, AI Gateway, Object Storage, and Functions. Skills install into the current directory by default, so they travel with the repository, and neon skills update refreshes them to their latest versions later.

For example, install the core Postgres and AI Gateway skills into Cursor:

neon skills -s neon -s neon-ai-gateway --agent cursor

neon plugins …

Faster Lakebase Search setup

Lakebase Search is now easier to install. You can install both Lakebase Search extensions (lakebase_vector and lakebase_text) directly with the following CREATE EXTENSION statements from your SQL client or the Neon SQL Editor:

CREATE EXTENSION IF NOT EXISTS lakebase_vector CASCADE;
CREATE EXTENSION IF NOT EXISTS lakebase_text CASCADE;

Previously, you had to run an SQL statement first to load the supporting libraries.

We also updated both extensions to newer versions (lakebase_vector 1.0.1 and lakebase_text 0.1.1). If you already have them installed, see Update an extension to get the latest version.

Note: Get started with Lakebase Search

Lakebase Search is a pgvector-compatible alternative for vector, keyword, and hybrid search that scales past a billion vectors, builds indexes 50–100x faster than HNSW, and stays ready after a scale-to-zero cold start. Follow the getting started guide to enable the extensions, load sample data, and run your first vector and keyword searches.

Postgres minor version updates …

A new Console layout for the Neon backend

The Console sidebar has a new shape. Every branch-level Neon backend service now sits at the same level.

• Postgres database is everything that was in the sidebar before: Tables, SQL Editor, Backup & Restore, Computes, Data API, Roles, and Databases, now under one collapsible item.
• Auth, Object storage, Functions, and AI Gateway backend services sit alongside it as siblings.

Above that section, the sidebar separates what belongs to project (Dashboard, Branches, Integrations, Settings) from what belongs to the branch (Overview, Credentials, Monitoring, Child branches). The branch picker sits between them, so it's clear which branch you're looking at when you open a service.

Overview is now a summary of the branch you have selected. It lists each backend service with its status, so you can see what the branch actually has enabled without opening each one:

The new Neon Console sidebar alongside the branch Overview page, which lists Postgres database, BetterAuth, Object storage, Functions, and AI Gateway with their status

Each service shows whether it's enabled on the branch, so the page doubles as a list of what you can still add.

Important: More regions for backend services coming soon …

Project-level permissions

A feature you've been asking for is finally here. Until now, a person's access applied across your entire organization. We're excited to bring project-level permissions to Neon, so you can now grant people and agents access on individual projects, giving them only what they need where they need it. On any project, you can make someone a Viewer to see its resources, an Editor to change them, or an Admin to manage access and the project itself.

Note: Availability

The new model is available now for newly created organizations and will roll out to existing organizations soon.

Access works in two layers. When both apply, a user keeps the higher level of access:

• Organization roles set a baseline across every project. There are now four: Admin (full control), Editor (work in every project, but can't delete or transfer them), Viewer (read-only), and Collaborator (no access until granted specific projects).
• Per-project permissions raise that baseline on specific projects. Grant a member Viewer (read-only), Editor (connect, query, and edit resources), or Admin (manage access, settings, and the project lifecycle) on any project from Settings → Project permissions. …

1 GB of storage per project on the Neon Free plan

The Neon Free plan now gives you 1 GB of database storage per project, up from 0.5 GB. Existing projects pick up the new limit automatically. It was one of the most requested Free plan changes.

The extra storage builds on an already-generous plan: you get up to 100 projects on the Free plan, each with its own compute, storage, and egress. Spin up a new project for every app idea, experiment, or client demo, without paying for each project separately.

Read more in the blog post: Neon gives you 100 projects for free, with 1 GB of Postgres storage each, or see Neon plans for the full breakdown.

The Neon AI Gateway now supports embedding models, so you can turn text into vectors through the same OpenAI-compatible endpoint and Neon credential you already use for chat. Call /v1/embeddings with either model:

import OpenAI from 'openai';

const client = new OpenAI({
  apiKey: process.env.NEON_AI_GATEWAY_TOKEN,
  baseURL: `${process.env.NEON_AI_GATEWAY_BASE_URL}/v1`,
});

const { data } = await client.embeddings.create({
  model: 'qwen3-embedding-0-6b', // or 'gte-large-en'
  input: 'The quick brown fox jumps over the lazy dog.',
  encoding_format: 'float',
});
// data[0].embedding is a 1024-dimension vector

Both models (qwen3-embedding-0-6b and gte-large-en) return 1024-dimension vectors and are billed on input tokens only. Store and search the vectors on the same branch as your data with Lakebase Search or pgvector. For the full reference, including the dimensions parameter and response format, see the Embeddings guide.

Effect is a TypeScript library for building resilient apps, with typed errors, retries, timeouts, and cancellation built in. The new @neon/effect package wraps the Neon Management SDK in Effect v4, so managing your Neon projects fits that model: every API call returns an Effect, paginated lists return a Stream, and SDK errors are tagged for Effect.catchTag. Interrupting a fiber cancels the in-flight request and readiness polling, so retries, timeouts, and cancellation compose with the rest of your program.

import { Neon, layerConfig } from '@neon/effect';
import { Effect, Stream } from 'effect';

const program = Effect.gen(function* () {
  const neon = yield* Neon;
  return yield* neon.projects.list().pipe(Stream.take(10), Stream.runCollect);
});

Effect.runPromise(program.pipe(Effect.provide(layerConfig)));

Install @neon/effect alongside effect v4. Read more in the blog post: Announcing @neon/effect, or see the Effect bindings reference.

• Updated PostGIS and its related geospatial extensions (postgis, postgis_raster, postgis_sfcgal, postgis_tiger_geocoder, postgis_topology, address_standardizer, and address_standardizer_data_us) to newer versions: 3.3.10 on Postgres 14 through 16, 3.5.7 on Postgres 17, and 3.6.4 on Postgres 18. To upgrade an existing installation, see Update an extension version.
• Updated the hll extension (HyperLogLog data type) to version 2.21 across all supported Postgres versions.

• The @neon/ai-sdk-provider (1.0.0) now supports embeddings. neon.embeddingModel('qwen3-embedding-0-6b') works with the Vercel AI SDK's embed() and embedMany(), routed through the AI Gateway with your Neon credential, so you no longer have to call the endpoint outside the provider. See Embeddings. …

Reset from parent now rolls back a branch's Object Storage along with its Postgres data. When you reset a branch, its buckets and objects return to the parent's current state, so any object storage uploads, overwrites, and deletes you made on the branch are also reverted.

You can reset a branch from the Neon Console, CLI, or API. See Reset from parent for the steps.

Resetting Object Storage is available now in AWS US East (Ohio) (aws-us-east-2) and AWS Europe (Frankfurt) (aws-eu-central-1), with support for additional regions rolling out soon.

The Lakebase Search extensions are updated: lakebase_vector to 1.1.1 and lakebase_text to 0.1.3, with performance improvements and fixes. If you have them installed, upgrade when convenient with ALTER EXTENSION <name> UPDATE; see Upgrade the extension and indexes.

Note:

Building search with an AI coding assistant? The neon-postgres agent skill now includes Lakebase Search guidance for vector, full-text, and hybrid queries. Install it with:

neon skills -s neon-postgres

Neon started as serverless Postgres. Now you get the whole backend, and all of it branches. Every branch is a full copy, so a PR, preview, or agent session gets your entire backend, not just the database. Evolve your schema, storage, auth, and functions together on a preview branch, isolated from production.

▶️ Watch the walkthrough to see how it all fits together.

• Lakebase Postgres: 100% Postgres on the Lakebase architecture: autoscaling, scale to zero, and a branch for every PR, preview, or agent session.
• Object Storage: S3-compatible object storage that branches with your data, so files and rows stay in sync across branches.
• Auth: Managed Better Auth: users and sessions live in your neon_auth schema, queryable with SQL and protected by RLS.
• Functions: Long-running Node.js compute next to your database, now with triggers and custom domains.
• AI Gateway: One credential for frontier and open-weight models at provider prices with no markup. Buy prepaid credits to use it.
• Data API: An instant REST endpoint over your Postgres tables, no backend server required.

How to get started …