Changelog

Help shape what we build in 2026

From the Neon team, we'd like to extend a warm and heartfelt Happy New Year to every member of our community.

What a year 2025 was. In May, Neon joined Databricks, but our mission hasn't changed. We're still focused on delivering the best Postgres experience for developers and AI agents.

Beyond that, we shipped a ton of features in 2025. You can see everything we built here.

Here's the thing though, none of this happens without you. Your feedback, whether you chat with us in Discord, ping us on Twitter, or drop it in the console, that's what shapes what we build. Every suggestion, bug report, and feature request matters to us.

So as we kick off 2026, we want to ask What should we ship next?

Got a feature you're waiting for? A bug that's causing you trouble? An idea that would take things to the next level? We want to hear it.

You can share your feedback on Discord, Twitter/X, or via the Send Feedback modal in the Neon Console.

Thank you for being part of this journey with us. Let's build great things together in 2026! 🚀

Project recovery

Accidentally deleted a project? You can now recover it within 7 days of deletion. This feature restores your entire project infrastructure, including all branches, endpoints, compute configurations, and project settings. Your connection strings, collaborators, and snapshots all come back exactly as they were.

Recovery is available through the CLI and API. There are no storage costs or recovery fees during the 7-day recovery window.

For more information, see Recover a deleted project.

100 Free plan projects

Another week, yet another increase: The Neon Free plan now includes:

• 80 projects
• 100 projects

That's 100 separate database projects you can spin up, experiment with, and build on. Whether you're prototyping ideas, learning Postgres, or running multiple side projects, you've got plenty of room to work.

This change applies automatically to all Free plan users. No action required. For more information about plan limits, see Neon plans.

Learn about why we're increasing project limits on the Free plan

Easier setup for Neon MCP Server

Connecting AI editors to the Neon MCP Server is now a single command:

npx neonctl@latest init

This command authenticates via OAuth, automatically creates a Neon API key, and configures Cursor, VS Code, or Claude Code CLI to connect to Neon. It handles all the setup steps that previously required manual configuration file edits and API key management. Once configured, you can immediately ask your AI assistant to create projects, manage branches, or query your database.

If you’re an existing Neon MCP user, setting up the MCP Server this way means you won’t be prompted to repeatedly reconnect through browser-based OAuth flows. Your local configuration and API key are created and saved for reuse.

For more information, see Connect MCP clients to Neon.

Data masking enhancements

We've added address-specific masking functions to data masking in the Neon Console. These functions provide specialized handling for text fields like street addresses, cities, and postal codes, letting you mask location data while preserving geographic patterns.

As well, all masking functions are now organized into categories (Names, Email Addresses, Phone Numbers, and Addresses).

For more information about data masking, see Data anonymization.

AI-powered Neon Auth setup

Your AI editor can now scaffold complete authentication flows with Neon Auth. We've published AI rules, MCP prompt templates, and a Claude skill that teach AI assistants how to integrate Neon Auth into your apps. These tools detect your framework, install the right packages, create the necessary files, and follow best practices automatically.

The setup includes:

• AI rules
• MCP prompt templates
• Claude skill

This means you can open Cursor, Claude, or VS Code, ask your AI assistant to "add Neon Auth," and let it handle the implementation.

Learn more in our blog post, Teaching AI to Do Auth (So You Don't Have To).

Neon Auth: branchable identity in your database

We've rebuilt Neon Auth using Better Auth as the foundation. Auth was the last part of Neon that didn't yet branch. Now it does. All authentication data lives directly in your Neon database, so when you branch, your entire auth state branches with it.

Users, sessions, organizations, configuration, and JWKS are stored in a dedicated neon_auth schema. Each branch gets its own isolated auth endpoint. No more external identity provider, no webhook syncing, no drift between environments.

What branchable auth enables:

• Preview environments that actually work. Spin up a branch that mirrors production exactly: same users, same roles, same permissions. Test full signup, login, password reset, and OAuth flows before release.
• Safe multi-tenant testing. Clone your environment, invite test organizations, modify access rules, and confirm permissions propagate correctly without risking production data.
• Real auth in CI/CD. Test the complete user lifecycle in automated pipelines with real authentication, not mocked tokens.

How it works:

• Auth lives in your database. Your user model sits in Postgres, evolving with your migrations and integrating naturally with your schema.

• Works with RLS automatically. Your Row-Level Security policies can reference the authenticated user directly, without duplicate identity tables.

• Data API integration. JWTs from Neon Auth are validated by the Data API, so authenticated queries work with your RLS policies out of the box.

• One SDK for everything. The new @neondatabase/neon-js package brings Neon Auth, Data API, and database access together:

  import { createAuthClient } from '@neondatabase/neon-js/auth';
  import { NeonAuthUIProvider, AuthView } from '@neondatabase/neon-js/auth/react/ui';
  
  const authClient = createAuthClient(import.meta.env.VITE_NEON_AUTH_URL);
  
  export default function App() {
    return (
      <NeonAuthUIProvider authClient={authClient}>
        <AuthView pathname="sign-in" />
      </NeonAuthUIProvider>
    );
  }

Neon Auth is available on all plans, including Free. Get started with Next.js, React, or TanStack.

"Owning your auth means keeping your user model inside your architecture. Neon users now get that ownership while letting Better Auth take care of the parts that make authentication hard." — Bereket Engida, creator of Better Auth

Read more: Meet the New Neon Auth: Branchable Identity in Your Database and The Case for Owning Your Auth

More projects on the Free plan

Another week, another increase: The Neon Free plan now includes:

• 70 projects
• 80 projects

More projects means more room to experiment, prototype, and build without worrying about limits.

This change applies automatically to all Free plan users. No action required. For more information about plan limits, see Neon plans.

Learn about why we're increasing project limits on the Free plan

Purely usage-based billing

We've removed the $5 monthly minimum from our paid plans. Neon is now purely usage-based: if you use $3 one month, that's the bill you'll receive.

For more details, see Neon plans.