Neon Release Notes
Last updated: Feb 21, 2026
Neon Products
All Neon Release Notes (37)
- Feb 20, 2026
- Date parsed from source:Feb 20, 2026
- First seen by Releasebot:Feb 21, 2026
Feb 20, 2026
Neon rolls out a new Connect modal default showing the database connection string for easy copy, plus the Neon Cursor plugin for natural language guided workflows and SQL ops. It also expands AWS Frankfurt capacity and introduces a CircleCI Orb to create per job DB branches for deterministic CI.
Connect modal defaults to Connection string
Developers told us they want to quickly copy the database connection string to drop into their application. Based on that feedback, the Connect modal on the project dashboard now defaults to Connection string in the snippet dropdown instead of the psql command. You can still choose any snippet from the dropdown (e.g., psql), and your preferred option is saved for the next time you open the Connect modal.
Cursor plugin for Neon
The Neon Cursor plugin is now available. It adds Neon Skills and MCP integration to Cursor so your assistant can use workflow guidance (connection methods, ORMs, branching) and run database operations from natural language, including listing projects, creating branches, running SQL, and more. In Cursor chat, run /add-plugin neon-postgres , or run /add-plugin and search for neon . The plugin appears as Neon Postgres in the Add Plugin menu:
After installation, prompt with "Get started with Neon" to complete authentication. For setup and usage, see Cursor plugin for Neon.
Expanded infrastructure capacity in AWS Europe (Frankfurt)
We've expanded infrastructure capacity in the AWS Europe (Frankfurt) region (aws-eu-central-1 ). If you have IP allowlists on external systems that Neon connects to, or if you use Private Networking in this region, update your allowlists or VPC endpoint configuration to include any new addresses. See our Regions documentation for the complete list of NAT gateway IPs and the Private Networking guide for VPC endpoint service addresses by region.
Neon CircleCI Orb: a Postgres branch for every pipeline run
A new community-contributed Neon CircleCI Orb provisions a Neon database branch per job, so your CI database is production-like in behavior with fewer "works in CI, breaks in prod" surprises. Each run gets an isolated, ephemeral branch. You can branch from a pre-migrated base to skip running migrations from scratch. The orb handles cleanup and TTL when the job ends. Because each run has its own branch, tests stay deterministic and parallel runs don't share state. Example:
version : 2.1 orbs : neon : dhanushreddy291/[email protected] workflows : test_workflow : jobs : - neon/run_tests : migrate_command : npm run db:migrate test_command : npm testSee the Automate branching with CircleCI guide to get started. The guide covers the neon/run_tests job and the neon/create_branch , neon/delete_branch , and neon/reset_branch commands.
Original source Report a problem - Feb 20, 2026
- Date parsed from source:Feb 20, 2026
- First seen by Releasebot:Feb 21, 2026
Feb 20, 2026 – Connect modal default, Cursor plugin, Neon CircleCI Orb, and more
Neon updates speed up setup with the Connect modal defaulting to the Connection string. The Neon Cursor plugin adds workflow guidance and can run SQL from natural language. Plus AWS Frankfurt capacity expansion and a Neon CircleCI Orb deliver isolated CI DB branches for every run.
Connect modal defaults to Connection string
Developers told us they want to quickly copy the database connection string to drop into their application. Based on that feedback, the Connect modal on the project dashboard now defaults to Connection string in the snippet dropdown instead of the psql command. You can still choose any snippet from the dropdown (e.g., psql), and your preferred option is saved for the next time you open the Connect modal.
Cursor plugin for Neon
The Neon Cursor plugin is now available. It adds Neon Skills and MCP integration to Cursor so your assistant can use workflow guidance (connection methods, ORMs, branching) and run database operations from natural language, including listing projects, creating branches, running SQL, and more. In Cursor chat, run /add-plugin neon-postgres, or run /add-plugin and search for neon. The plugin appears as Neon Postgres in the Add Plugin menu:
After installation, prompt with "Get started with Neon" to complete authentication. For setup and usage, see Cursor plugin for Neon.
Expanded infrastructure capacity in AWS Europe (Frankfurt)
We've expanded infrastructure capacity in the AWS Europe (Frankfurt) region (aws-eu-central-1). If you have IP allowlists on external systems that Neon connects to, or if you use Private Networking in this region, update your allowlists or VPC endpoint configuration to include any new addresses. See our Regions documentation for the complete list of NAT gateway IPs and the Private Networking guide for VPC endpoint service addresses by region.
Neon CircleCI Orb: a Postgres branch for every pipeline run
A new community-contributed Neon CircleCI Orb provisions a Neon database branch per job, so your CI database is production-like in behavior with fewer "works in CI, breaks in prod" surprises. Each run gets an isolated, ephemeral branch. You can branch from a pre-migrated base to skip running migrations from scratch. The orb handles cleanup and TTL when the job ends. Because each run has its own branch, tests stay deterministic and parallel runs don't share state. Example:
version: 2.1 orbs: neon: dhanushreddy291/[email protected] workflows: test_workflow: jobs: - neon/run_tests: migrate_command: npm run db:migrate test_command: npm testSee the Automate branching with CircleCI guide to get started. The guide covers the neon/run_tests job and the neon/create_branch, neon/delete_branch, and neon/reset_branch commands.
Original source Report a problem All of your release notes in one feed
Join Releasebot and get updates from Neon and hundreds of other software products.
- Feb 13, 2026
- Date parsed from source:Feb 13, 2026
- First seen by Releasebot:Feb 21, 2026
Feb 13, 2026 – Add org members by domain, Neon MCP Server updates, and the Compute Autoscaling Report
Neon rolls out domain based organization membership allowing admins to auto-add members by email domain. New MCP Server tools fetch docs and connect to Google Jules, plus an autoscaling performance report and a configurable OpenTelemetry API key header for easier integrations.
Add organization members by domain
Link to Add organization members by domain
Add organization members by domain
You can now add members to your organization by email domain. Organization admins can add and verify one or more domains (for example, yourcompany.com ) in your Neon organization Settings , under Domains .
When a user signs up or logs in to Neon with an email that matches a verified domain, they’re automatically added to your Neon organization as a Member, no invite email required. They see your organization in the org switcher in the Neon Console.
This is useful for teams that want everyone within the company email domain to have access without needing to send individual invites. You simply add your domain in the Neon Console, add a TXT record at your DNS provider to verify ownership, then click Verify in the Neon Console.
Domain section on the Organization Settings page
Colleagues who already have Neon accounts are added to the organization the next time they log in. For the full flow and behavior (roles, multiple domains), see Add members by domain .
Neon MCP Server updates
Neon MCP Server updates
This week’s Neon MCP Server release brings new tools for pulling Neon documentation and setup guidance into your development environment, plus a new guide for connecting Google Jules to the Neon MCP Server.
New documentation retrieval tools
The MCP Server now includes two tools so your AI agent or MCP client can fetch Neon docs on demand:
- list_docs_resources – Lists all available Neon documentation pages from the docs index. Returns page URLs and titles so you can choose which page to load.
- get_doc_resource – Fetches a specific Neon documentation page as markdown. Use list_docs_resources first to discover page slugs, then pass the slug to this tool to load the content.
Together, these tools let your agent or assistant look up setup, configuration, and how-to content from the Neon docs without leaving the chat.
Neon MCP Server on Google Jules
The Neon MCP Server is now available in Google Jules , Google's AI-powered coding assistant. Create a Neon API key, add the server in Jules settings, and you're set. Full setup steps are in Connect MCP clients to Neon .
Neon MCP Server in Google Jules
Compute Autoscaling Report
Compute Autoscaling Report
We've published a Compute Autoscaling Report that breaks down how Neon's autoscaling compute compares to provisioned, fixed compute sizes, based on real production workloads that run on Neon.
KEY FINDINGS
- Production databases on Neon use 2.4x less compute and 50% less cost than if they were running on provisioned, fixed compute sizes.
- Putting the same production workloads on provisioned, fixed compute sizes would result in 55 performance degradations per database per month.
- Read replicas on Neon use 4x less compute than if they were running on provisioned, fixed compute sizes.
- Running the same small scale-to-zero workloads on provisioned, fixed compute sizes would cost 7.5x more.
- The report walks through what happens when you use provisioned, fixed compute sizes vs. autoscaling compute, and how that impacts cost and performance. If you've ever wondered how much autoscaling actually saves you (or how it behaves under real traffic), the report lays it out with real data and the full methodology.
Autoscaling report graph
To learn more about Neon's autoscaling feature and how to enable it for your projects, see Autoscaling .
Custom API key header for OpenTelemetry
Link to Custom API key header for OpenTelemetry
Custom API key header for OpenTelemetry
You can now specify a custom header name for API key authentication when configuring OpenTelemetry integrations. The header defaults to X-API-Key if not specified. This makes it easier to integrate with services like Honeycomb that expect a different header name for API keys.
OpenTelemetry custom header name configuration
Back to all changelog posts
Original source Report a problem - Feb 13, 2026
- Date parsed from source:Feb 13, 2026
- First seen by Releasebot:Feb 18, 2026
Feb 13, 2026
Neon rolls out domain-based org membership, auto-adding users by verified email domain for seamless team access. New MCP Server docs tools, Google Jules integration, and an autoscaling report showing cost and performance benefits. Also adding custom OpenTelemetry API key header support.
Add organization members by domain
You can now add members to your organization by email domain. Organization admins can add and verify one or more domains (for example, yourcompany.com) in your Neon organization Settings, under Domains.
When a user signs up or logs in to Neon with an email that matches a verified domain, they’re automatically added to your Neon organization as a Member, no invite email required. They see your organization in the org switcher in the Neon Console.
This is useful for teams that want everyone within the company email domain to have access without needing to send individual invites. You simply add your domain in the Neon Console, add a TXT record at your DNS provider to verify ownership, then click Verify in the Neon Console.
Colleagues who already have Neon accounts are added to the organization the next time they log in. For the full flow and behavior (roles, multiple domains), see Add members by domain.
Neon MCP Server updates
This week’s Neon MCP Server release brings new tools for pulling Neon documentation and setup guidance into your development environment, plus a new guide for connecting Google Jules to the Neon MCP Server.
New documentation retrieval tools
The MCP Server now includes two tools so your AI agent or MCP client can fetch Neon docs on demand:
- list_docs_resources – Lists all available Neon documentation pages from the docs index. Returns page URLs and titles so you can choose which page to load.
- get_doc_resource – Fetches a specific Neon documentation page as markdown. Use list_docs_resources first to discover page slugs, then pass the slug to this tool to load the content.
Together, these tools let your agent or assistant look up setup, configuration, and how-to content from the Neon docs without leaving the chat.
Neon MCP Server on Google Jules
The Neon MCP Server is now available in Google Jules, Google's AI-powered coding assistant. Create a Neon API key, add the server in Jules settings, and you're set. Full setup steps are in Connect MCP clients to Neon.
Compute Autoscaling Report
We've published a Compute Autoscaling Report that breaks down how Neon's autoscaling compute compares to provisioned, fixed compute sizes, based on real production workloads that run on Neon.
KEY FINDINGS- Production databases on Neon use 2.4x less compute and 50% less cost than if they were running on provisioned, fixed compute sizes.
- Putting the same production workloads on provisioned, fixed compute sizes would result in 55 performance degradations per database per month.
- Read replicas on Neon use 4x less compute than if they were running on provisioned, fixed compute sizes.
- Running the same small scale-to-zero workloads on provisioned, fixed compute sizes would cost 7.5x more.
The report walks through what happens when you use provisioned, fixed compute sizes vs. autoscaling compute, and how that impacts cost and performance. If you've ever wondered how much autoscaling actually saves you (or how it behaves under real traffic), the report lays it out with real data and the full methodology.
To learn more about Neon's autoscaling feature and how to enable it for your projects, see Autoscaling.
Custom API key header for OpenTelemetry
You can now specify a custom header name for API key authentication when configuring OpenTelemetry integrations. The header defaults to X-API-Key if not specified. This makes it easier to integrate with services like Honeycomb that expect a different header name for API keys.
Original source Report a problem - Feb 13, 2026
- Date parsed from source:Feb 13, 2026
- First seen by Releasebot:Feb 18, 2026
Feb 13, 2026 – Add org members by domain, Neon MCP Server updates, and the Compute Autoscaling Report
Neon introduces domain based organization membership for automatic member enrollment by verified email domains. The MCP Server gets docs retrieval tools and Google Jules support, plus an autoscaling performance and cost report. Also add a custom OpenTelemetry API key header name for easier integrations.
Add organization members by domain
Add organization members by domain
You can now add members to your organization by email domain. Organization admins can add and verify one or more domains (for example, yourcompany.com) in your Neon organization Settings, under Domains.
When a user signs up or logs in to Neon with an email that matches a verified domain, they’re automatically added to your Neon organization as a Member, no invite email required. They see your organization in the org switcher in the Neon Console.
This is useful for teams that want everyone within the company email domain to have access without needing to send individual invites. You simply add your domain in the Neon Console, add a TXT record at your DNS provider to verify ownership, then click Verify in the Neon Console.
Domain section on the Organization Settings pageColleagues who already have Neon accounts are added to the organization the next time they log in. For the full flow and behavior (roles, multiple domains), see Add members by domain.
Neon MCP Server updates
Neon MCP Server updates
This week’s Neon MCP Server release brings new tools for pulling Neon documentation and setup guidance into your development environment, plus a new guide for connecting Google Jules to the Neon MCP Server.
New documentation retrieval tools
The MCP Server now includes two tools so your AI agent or MCP client can fetch Neon docs on demand:
- list_docs_resources – Lists all available Neon documentation pages from the docs index. Returns page URLs and titles so you can choose which page to load.
- get_doc_resource – Fetches a specific Neon documentation page as markdown. Use list_docs_resources first to discover page slugs, then pass the slug to this tool to load the content.
Together, these tools let your agent or assistant look up setup, configuration, and how-to content from the Neon docs without leaving the chat.
Neon MCP Server on Google Jules
The Neon MCP Server is now available in Google Jules, Google's AI-powered coding assistant. Create a Neon API key, add the server in Jules settings, and you're set. Full setup steps are in Connect MCP clients to Neon.
Neon MCP Server in Google Jules
Compute Autoscaling Report
Compute Autoscaling Report
We've published a Compute Autoscaling Report that breaks down how Neon's autoscaling compute compares to provisioned, fixed compute sizes, based on real production workloads that run on Neon.
KEY FINDINGS- Production databases on Neon use 2.4x less compute and 50% less cost than if they were running on provisioned, fixed compute sizes.
- Putting the same production workloads on provisioned, fixed compute sizes would result in 55 performance degradations per database per month.
- Read replicas on Neon use 4x less compute than if they were running on provisioned, fixed compute sizes.
- Running the same small scale-to-zero workloads on provisioned, fixed compute sizes would cost 7.5x more.
- The report walks through what happens when you use provisioned, fixed compute sizes vs. autoscaling compute, and how that impacts cost and performance. If you've ever wondered how much autoscaling actually saves you (or how it behaves under real traffic), the report lays it out with real data and the full methodology.
Autoscaling report graph
To learn more about Neon's autoscaling feature and how to enable it for your projects, see Autoscaling.
To learn more about Neon's autoscaling feature and how to enable it for your projects, see Autoscaling.Custom API key header for OpenTelemetry
Custom API key header for OpenTelemetry
You can now specify a custom header name for API key authentication when configuring OpenTelemetry integrations. The header defaults to X-API-Key if not specified. This makes it easier to integrate with services like Honeycomb that expect a different header name for API keys.
OpenTelemetry custom header name configuration
Original source Report a problem - Feb 6, 2026
- Date parsed from source:Feb 6, 2026
- First seen by Releasebot:Feb 21, 2026
Feb 06, 2026 – Track usage programmatically, simpler MCP Server setup, and new PG18 extension support
Neon rolls out a new consumption history API on all paid plans for usage based billing, plus simpler MCP server setup and expanded Postgres 18 extensions including pg_graphql and pgx_ulid. These updates enable programmatic usage tracking, easier integration, and broader extension support.
Track your usage programmatically on paid plans
A new consumption history API for current usage-based plans is now available on all paid plans, including Launch. The metrics returned align directly with usage-based billing, so what you query matches what you see on your invoice.
Use this API to build custom dashboards, integrate with your reporting tools, or set up usage alerts. Query at hourly, daily, or monthly granularity for metrics like compute usage, storage (root and child branches), instant restore, data transfer, and extra branches.
This example retrieves month-to-date usage for all metrics:
curl --request GET \ --url 'https://console.neon.tech/api/v2/consumption_history/v2/projects?from=2026-02-01T00:00:00Z&to=2026-02-06T00:00:00Z&granularity=daily&org_id=$ORG_ID&metrics=compute_unit_seconds,root_branch_bytes_month,child_branch_bytes_month,instant_restore_bytes_month,public_network_transfer_bytes,private_network_transfer_bytes,extra_branches_month' \ --header 'Accept: application/json' \ --header 'Authorization: Bearer $NEON_API_KEY' | jqFor API details, see Retrieve project consumption metrics. For more information, see Querying consumption metrics.
Try it with your AI agent:
Copy this prompt to have an AI assistant help you build the curl command for your desired time period.Simpler MCP Server setup
You can now configure the Neon MCP Server for all detected AI agents and editors in your workspace with a single command:
npx add-mcp https://mcp.neon.tech/mcpThis adds the MCP config to your editor; restart your editor (or enable the MCP server in settings). When you use the connection, an OAuth window will open in your browser to authorize access. For the full setup (MCP server plus agent skills and VS Code extension), use npx neonctl@latest init instead. It configures the MCP server for Cursor, VS Code, Claude Code, and others using API key authentication.
With OAuth, the MCP server uses your personal Neon account by default. To use organization projects, provide org_id or project_id in your prompt. For API key-based authentication (e.g., remote agents), use:
npx add-mcp https://mcp.neon.tech/mcp --header "Authorization: Bearer $NEON_API_KEY"For more setup options (including global vs project-level), see Connect MCP clients to Neon and the add-mcp repository.
Postgres extension updates
We've expanded extension support for Postgres 18:
Extension | Version | Description
pg_graphql | 1.5.12 | Adds a GraphQL API layer directly to your Postgres database
pgx_ulid | 0.2.2 | Generates universally unique lexicographically sortable identifiers (ULIDs)To install these extensions, run:
CREATE EXTENSION pg_graphql; CREATE EXTENSION pgx_ulid;For a complete list of Postgres extensions supported by Neon, see Postgres extensions.
Original source Report a problem - Feb 6, 2026
- Date parsed from source:Feb 6, 2026
- First seen by Releasebot:Feb 18, 2026
Feb 06, 2026
Neon launches a consumption history API on all paid plans with hourly to monthly usage metrics aligned to invoices, perfect for dashboards and alerts. It also simplifies MCP Server setup with single commands and OAuth, plus expanded Postgres extensions pg_graphql and pgx_ulid.
Track your usage programmatically on paid plans
A new consumption history API for current usage-based plans is now available on all paid plans, including Launch. The metrics returned align directly with usage-based billing, so what you query matches what you see on your invoice.
Use this API to build custom dashboards, integrate with your reporting tools, or set up usage alerts. Query at hourly, daily, or monthly granularity for metrics like compute usage, storage (root and child branches), instant restore, data transfer, and extra branches.
This example retrieves month-to-date usage for all metrics:
curl --request GET \ --url 'https://console.neon.tech/api/v2/consumption_history/v2/projects?from=2026-02-01T00:00:00Z&to=2026-02-06T00:00:00Z&granularity=daily&org_id=$ORG_ID&metrics=compute_unit_seconds,root_branch_bytes_month,child_branch_bytes_month,instant_restore_bytes_month,public_network_transfer_bytes,private_network_transfer_bytes,extra_branches_month' \ --header 'Accept: application/json' \ --header 'Authorization: Bearer $NEON_API_KEY' | jqFor API details, see Retrieve project consumption metrics. For more information, see Querying consumption metrics.
Try it with your AI agent:
Copy this prompt to have an AI assistant help you build the curl command for your desired time period.Simpler MCP Server setup
You can now configure the Neon MCP Server for all detected AI agents and editors in your workspace with a single command:
npx add-mcp https://mcp.neon.tech/mcpThis adds the MCP config to your editor; restart your editor (or enable the MCP server in settings). When you use the connection, an OAuth window will open in your browser to authorize access. For the full setup (MCP server plus agent skills and VS Code extension), use npx neonctl@latest init instead. It configures the MCP server for Cursor, VS Code, Claude Code, and others using API key authentication.
With OAuth, the MCP server uses your personal Neon account by default. To use organization projects, provide org_id or project_id in your prompt. For API key-based authentication (e.g., remote agents), use:
npx add-mcp https://mcp.neon.tech/mcp --header "Authorization: Bearer $NEON_API_KEY"For more setup options (including global vs project-level), see Connect MCP clients to Neon and the add-mcp repository.
Postgres extension updates
We've expanded extension support for Postgres 18:
Extension Version Description pg_graphql 1.5.12 Adds a GraphQL API layer directly to your Postgres database pgx_ulid 0.2.2 Generates universally unique lexicographically sortable identifiers (ULIDs)To install these extensions, run:
CREATE EXTENSION pg_graphql; CREATE EXTENSION pgx_ulid;For a complete list of Postgres extensions supported by Neon, see Postgres extensions.
Original source Report a problem - Feb 6, 2026
- Date parsed from source:Feb 6, 2026
- First seen by Releasebot:Feb 18, 2026
Feb 06, 2026 – Track usage programmatically, simpler MCP Server setup, and new PG18 extension support
Neon rolls out a new consumption history API for paid plans to align usage metrics with invoices, plus an easier MCP Server setup and enhanced Postgres extensions. These updates enable deeper usage insights, smoother agent integration, and broader extension support.
Track your usage programmatically on paid plans
Track your usage programmatically on paid plans
A new consumption history API for current usage-based plans is now available on all paid plans, including Launch. The metrics returned align directly with usage-based billing, so what you query matches what you see on your invoice.
Use this API to build custom dashboards, integrate with your reporting tools, or set up usage alerts. Query at hourly, daily, or monthly granularity for metrics like compute usage, storage (root and child branches), instant restore, data transfer, and extra branches.
This example retrieves month-to-date usage for all metrics:
curl --request GET \ --url 'https://console.neon.tech/api/v2/consumption_history/v2/projects?from=2026-02-01T00:00:00Z&to=2026-02-06T00:00:00Z&granularity=daily&org_id=$ORG_ID&metrics=compute_unit_seconds,root_branch_bytes_month,child_branch_bytes_month,instant_restore_bytes_month,public_network_transfer_bytes,private_network_transfer_bytes,extra_branches_month' \ --header 'Accept: application/json' \ --header 'Authorization: Bearer $NEON_API_KEY' | jqFor API details, see Retrieve project consumption metrics. For more information, see Querying consumption metrics.
Try it with your AI agent:
Copy this prompt to have an AI assistant help you build the curl command for your desired time period.Simpler MCP Server setup
Simpler MCP Server setup
You can now configure the Neon MCP Server for all detected AI agents and editors in your workspace with a single command:
npx add-mcp https://mcp.neon.tech/mcpThis adds the MCP config to your editor; restart your editor (or enable the MCP server in settings). When you use the connection, an OAuth window will open in your browser to authorize access. For the full setup (MCP server plus agent skills and VS Code extension), use npx neonctl@latest init instead. It configures the MCP server for Cursor, VS Code, Claude Code, and others using API key authentication.
With OAuth, the MCP server uses your personal Neon account by default. To use organization projects, provide org_id or project_id in your prompt. For API key-based authentication (e.g., remote agents), use:
npx add-mcp https://mcp.neon.tech/mcp --header "Authorization: Bearer $NEON_API_KEY"For more setup options (including global vs project-level), see Connect MCP clients to Neon and the add-mcp repository.
Postgres extension updates
Postgres extension updates
We've expanded extension support for Postgres 18:
Extension Version Description pg_graphql 1.5.12 Adds a GraphQL API layer directly to your Postgres database pgx_ulid 0.2.2 Generates universally unique lexicographically sortable identifiers (ULIDs)To install these extensions, run:
CREATE EXTENSION pg_graphql; CREATE EXTENSION pgx_ulid;For a complete list of Postgres extensions supported by Neon, see Postgres extensions.
Original source Report a problem - Jan 30, 2026
- Date parsed from source:Jan 30, 2026
- First seen by Releasebot:Feb 21, 2026
Jan 30, 2026 – Neon Auth SDK simplified, Instagres REST API, and more
Neon rolls out a major update to the server side Neon Auth SDK for Next.js with a unified createNeonAuth() API, explicit config, and built‑in session caching that slashes Auth server calls. Expect breaking changes and a migration guide for upgrading smoothly.
Neon Auth SDK simplified
We've released a major update to the server-side Neon Auth SDK (@neondatabase/auth/next/server) for Next.js applications.
Unified entry point
The SDK now uses a single createNeonAuth() function that replaces the previous separate functions (neonAuth(), authApiHandler(), neonAuthMiddleware(), createAuthServer()). Configure authentication once and access all functionality from a single object:
// lib/auth/server.ts import { createNeonAuth } from '@neondatabase/auth/next/server'; export const auth = createNeonAuth({ baseUrl: process.env.NEON_AUTH_BASE_URL!, cookies: { secret: process.env.NEON_AUTH_COOKIE_SECRET! }, }); // Use everywhere in your app export const { GET, POST } = auth.handler(); // API routes export default auth.middleware({ loginUrl: '...' }); // Middleware const { data: session } = await auth.getSession(); // Server components await auth.signIn.email({ email, password }); // Server actionsExplicit configuration
Configuration is now explicit rather than implicit. You must pass baseUrl and cookies.secret directly to createNeonAuth() instead of relying on automatic environment variable reading, making dependencies clear and eliminating "magic" behavior.
Session caching
Session data is now automatically cached in a signed cookie, reducing API calls to the Auth Server by 95-99%. Sessions are cached for 5 minutes by default (configurable) and automatically refresh as needed.
Breaking changes
This release includes breaking changes. If you're using Neon Auth and want to upgrade to the latest SDK version, you will need to update your application code. Key changes include replacing separate auth functions with the unified createNeonAuth() API, adding a required NEON_AUTH_COOKIE_SECRET environment variable, and adding dynamic = 'force-dynamic' to server components that use auth methods.
For detailed migration instructions, see the migration guide. For complete API documentation, see the Next.js Server SDK reference.
Getting started
To see the latest SDK in action, check out the demo applications, including a Next.js demo with server components, a React + Vite demo with external UI, and a React demo with the full neon-js SDK. The repository also includes AI coding assistant skills for Cursor and Claude Code with updated setup guides and code examples. See the Neon Auth quickstart guide and Server SDK reference to get started.
Neon Auth is a managed authentication service that branches with your database. See the Neon Auth overview to learn more.
Claimable Postgres by Neon adds REST API
Claimable Postgres by Neon now offers a REST API for programmatic database provisioning, making it easy to integrate Postgres into your platform, CI/CD pipelines, testing frameworks, and automation workflows.
The new API enables you to create databases with a single HTTP request:
curl -X POST https://pg.new/api/v1/database \ -H 'Content-Type: application/json' \ -d '{"ref": "your-app-name"}'The API returns the ID, status, Neon project ID, connection string, claim URL, expiration timestamp, and creation/update timestamps. You can also retrieve database details using GET /api/v1/database/:id. Unclaimed databases have a 100 MB storage limit and expire after 72 hours. Claim your database to a Neon account to remove the expiration and get full Free plan limits.
The get-db CLI also adds a new --logical-replication flag to enable logical replication for real-time sync with tools like ElectricSQL.
Claimable Postgres provides instant cloud-hosted Postgres that spins up in seconds. No signup or registration required. See the Claimable Postgres documentation for more information.
New NAT gateway IP addresses
We've added new NAT gateway IP addresses in the AWS US East (N. Virginia), US East (Ohio), and US West (Oregon) regions to expand infrastructure capacity. If you have IP allowlists on external systems that Neon connects to, update those allowlists to include the new addresses. Connections may be affected intermittently if traffic routes through non-allowlisted NAT gateways.
See our Regions documentation for the complete list of NAT gateway IPs for all regions.
New VPC endpoint services for Private Networking
We've added new VPC endpoint service addresses for Private Networking in the AWS US East (N. Virginia), US East (Ohio), and US West (Oregon) regions. If you've set up Private Networking in these regions, you can now use the additional endpoint service addresses for enhanced infrastructure capacity and reliability.
For the complete list of VPC endpoint service addresses by region, see our Private Networking guide.
Original source Report a problem - Jan 30, 2026
- Date parsed from source:Jan 30, 2026
- First seen by Releasebot:Feb 18, 2026
Jan 30, 2026
Neon Auth SDK for Next.js unveils a major update with a unified createNeonAuth() API, explicit config, and cached sessions, boosting performance. Breaking changes require code upgrades with a migration guide. Instagres adds a REST API for instant Postgres provisioning and new NAT and VPC endpoints expand Private Networking.
Neon Auth SDK simplified
We've released a major update to the server-side Neon Auth SDK (@neondatabase/auth/next/server) for Next.js applications.
Unified entry point
The SDK now uses a single createNeonAuth() function that replaces the previous separate functions (neonAuth(), authApiHandler(), neonAuthMiddleware(), createAuthServer()). Configure authentication once and access all functionality from a single object:
// lib/auth/server.ts import { createNeonAuth } from '@neondatabase/auth/next/server'; export const auth = createNeonAuth({ baseUrl: process.env.NEON_AUTH_BASE_URL!, cookies: { secret: process.env.NEON_AUTH_COOKIE_SECRET! }, }); // Use everywhere in your app export const { GET, POST } = auth.handler(); // API routes export default auth.middleware({ loginUrl: '...' }); // Middleware const { data: session } = await auth.getSession(); // Server components await auth.signIn.email({ email, password }); // Server actionsExplicit configurationConfiguration is now explicit rather than implicit. You must pass baseUrl and cookies.secret directly to createNeonAuth() instead of relying on automatic environment variable reading, making dependencies clear and eliminating "magic" behavior.
Session caching
Session data is now automatically cached in a signed cookie, reducing API calls to the Auth Server by 95-99%. Sessions are cached for 5 minutes by default (configurable) and automatically refresh as needed.
Breaking changes
This release includes breaking changes. If you're using Neon Auth and want to upgrade to the latest SDK version, you will need to update your application code. Key changes include replacing separate auth functions with the unified createNeonAuth() API, adding a required NEON_AUTH_COOKIE_SECRET environment variable, and adding dynamic = 'force-dynamic' to server components that use auth methods.
For detailed migration instructions, see the migration guide. For complete API documentation, see the Next.js Server SDK reference.
Getting started
To see the latest SDK in action, check out the demo applications, including a Next.js demo with server components, a React + Vite demo with external UI, and a React demo with the full neon-js SDK. The repository also includes AI coding assistant skills for Cursor and Claude Code with updated setup guides and code examples. See the Neon Auth quickstart guide and Server SDK reference to get started.
Neon Auth is a managed authentication service that branches with your database. See the Neon Auth overview to learn more.
Instagres adds REST API
Instagres now offers a REST API for programmatic database provisioning, making it easy to integrate Postgres into your platform, CI/CD pipelines, testing frameworks, and automation workflows.
The new API enables you to create databases with a single HTTP request:
curl -X POST https://instagres.com/api/v1/database \ -H 'Content-Type: application/json' \ -d '{"ref": "your-app-name"}'The API returns the ID, status, Neon project ID, connection string, claim URL, expiration timestamp, and creation/update timestamps. You can also retrieve database details using GET /api/v1/database/:id. Unclaimed databases have a 100 MB storage limit and expire after 72 hours. Claim your database to a Neon account to remove the expiration and get full Free plan limits.
The get-db CLI also adds a new --logical-replication flag to enable logical replication for real-time sync with tools like ElectricSQL.
Instagres provides instant cloud-hosted Postgres that spins up in seconds. No signup or registration required. See the Instagres documentation for more information.
New NAT gateway IP addresses
We've added new NAT gateway IP addresses in the AWS US East (N. Virginia), US East (Ohio), and US West (Oregon) regions to expand infrastructure capacity. If you have IP allowlists on external systems that Neon connects to, update those allowlists to include the new addresses. Connections may be affected intermittently if traffic routes through non-allowlisted NAT gateways.
See our Regions documentation for the complete list of NAT gateway IPs for all regions.
New VPC endpoint services for Private Networking
We've added new VPC endpoint service addresses for Private Networking in the AWS US East (N. Virginia), US East (Ohio), and US West (Oregon) regions. If you've set up Private Networking in these regions, you can now use the additional endpoint service addresses for enhanced infrastructure capacity and reliability.
For the complete list of VPC endpoint service addresses by region, see our Private Networking guide.
Original source Report a problem