Changelog

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.

70 projects on the Free plan

We've increased the project limit on the Free plan to 70 projects.

That's 70 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 increased project limits on the Free plan

Postgres version updates

We updated supported Postgres versions to 14.20, 15.15, 16.11, 17.7, and 18.1, respectively.

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.

New Data API advanced settings

The Neon Data API provides a ready-to-use REST API for your Neon database, letting you query tables, views, and functions using standard HTTP requests. We've added two new options to the Advanced settings panel:

• OpenAPI mode — Enables automatic generation of an OpenAPI schema for your Data API. Use it to generate API documentation, build typed client libraries, import your API into Postman, or integrate with API gateways.
• Enable server timing headers — Adds Server-Timing headers to API responses, showing how long different parts of each request took to process. Use this to debug slow queries, measure performance, and troubleshoot latency issues.

To learn more about Data API advanced settings, see Manage Data API.

Neon is now a Kiro Power

Kiro announced powers at AWS re:Invent — a new way for developers to access curated tools directly from the IDE. Neon is one of the first launch partners, alongside Figma, Stripe, and Postman.

With the Neon power, you can manage your Postgres databases without leaving Kiro:

• Deploy instantly — Provision a Neon database in seconds whenever your workflow needs a Postgres backend.
• Branch for safe testing — Create lightweight, isolated copies of your database to test migrations, validate queries, or run integration tests without touching production.
• Time-travel and restore — Roll back to any past state, inspect historical data, or restore from a previous point in time.

Read more: Just Launched: Neon Is Now a Kiro Power

Custom Neon agents for GitHub Copilot

GitHub Copilot now supports custom agents, and we've built two specialized agents that bring Neon's branching workflow directly into your IDE:

• Neon Migration Specialist — Safe Postgres migrations with zero downtime. Test schema changes in isolated database branches, validate, then apply to production—all automated with support for Prisma, Drizzle, or your favorite ORM.

• Neon Performance Analyzer — Identify and fix slow Postgres queries automatically. Analyzes execution plans, tests optimizations in isolated branches, and provides clear before/after performance metrics with actionable code fixes.

Both agents leverage Neon's instant branching to give you a safe environment for testing database changes before they hit production.

To learn more about using these agents, see Neon agents for GitHub Copilot.

More projects on the Free plan

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

• 50 projects
• 60 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

AI-powered Neon setup expands to VS Code and Claude

The one-command Neon setup, which configures the Neon MCP Server for AI-assisted project onboarding, now supports VS Code with GitHub Copilot and Claude Code CLI in addition to Cursor.

Run this command in your project directory:

npx neonctl@latest init

┌  Adding Neon to your project
│
◆  Which editor(s) would you like to configure? (Space to toggle each option, Enter to confirm your selection)
│  ◼ Cursor
│  ◼ VS Code
│  ◻ Claude CLI
│
◒  Authenticating
┌────────┬──────────────────┬────────┬────────────────┐
│ Login  │ Email            │ Name   │ Projects Limit │
├────────┼──────────────────┼────────┼────────────────┤
│ alex   │ alex@domain.com  │ Alex   │ 60             │
└────────┴──────────────────┴────────┴────────────────┘
◇  Authentication successful ✓
│
◇  Installed Neon MCP server
│
◇  Success! Neon is now ready to use with Cursor / VS Code.
│
│
◇  What's next? ─────────────────────────────────────────────────────────────╮
│                                                                            │
│  Restart Cursor / VS Code and type in "Get started with Neon" in the chat  │
│                                                                            │
├────────────────────────────────────────────────────────────────────────────╯

After setup, ask your AI assistant to "Get started with Neon" to launch an interactive onboarding guide. The guide analyzes your codebase and walks you through selecting or creating a project, configuring connection strings, installing dependencies, and more, all with contextual recommendations.

For more details about this feature, see our blog post.

HIPAA support now available for Postgres 18

HIPAA compliance is now supported for Postgres 18 projects in AWS regions. You can now create Postgres 18 projects in HIPAA-enabled Neon organizations and enable HIPAA compliance on existing Postgres 18 projects.

For more information, see HIPAA compliance.

Four ways platforms integrate with Neon

Whether you're building an agent platform, a developer tool that needs instant Postgres, or a SaaS that offers databases to users, there's a platform integration path designed for your use case:

☑ AI Agents integration — For codegen and agent platforms that need database versioning and isolated environments (platforms like Replit and CMS systems like Strapi)

☑ Claimable database flow — For plugins and platforms that want instant Postgres as part of their developer experience, with no signup required upfront (see TanStack, Netlify DB, or try Instagres at neon.new)

☑ Embedded Postgres — For SaaS platforms offering Postgres to users (platforms like Retool, which manages 300k+ databases, and Koyeb, which offers serverless Postgres)

☑ OAuth integration — For tools that interact with existing Neon accounts (platforms like Hasura Cloud, which uses OAuth for authentication and database provisioning)

If you're building an agent platform, check out the Neon Agent Plan, designed specifically for platforms that need to manage large fleets of databases with flexible resource limits and instant provisioning. Early-stage startups can also apply to the Neon Startup Program for startup credits.