This 250+ engineer team replaced shared staging with isolated database branches for safer deploys
/Changelog

Changelog

The latest product updates from Neon

RSS feed

New graphs for monitoring pooled connections

Neon uses PgBouncer for connection pooling, allowing thousands of client connections to share a smaller pool of actual Postgres connections. The monitoring page in the Neon Console now includes Pooler client connections and Pooler server connections graphs (these display data when you use a pooled connection). The Pooler client connections graph shows connections from your applications to PgBouncer, while Pooler server connections displays the actual connections from PgBouncer to Postgres. These graphs help you understand connection usage patterns, identify bottlenecks, and determine when to adjust your pool size or compute resources. For more information, see Monitoring dashboard.

Pooler client connections graph

Additionally, the OpenTelemetry and Datadog integrations now export PgBouncer connection pooling metrics, giving you visibility into pooler client and server connections in your observability platform alongside the new charts in the Neon Console. New integrations automatically include these metrics. To enable them for existing integrations, you can either edit the integration settings to trigger a collector upgrade or delete and recreate the integration.

GitHub Action support for Neon Auth and Data API

The Neon Create Branch GitHub Action now supports retrieving branch-specific URLs for Neon Auth and the Neon Data API. This makes it easy to run integration tests against isolated branch environments with the same auth and data access patterns you use in production. Set get_auth_url: true or get_data_api_url: true in your workflow to access the auth_url and data_api_url outputs for your test branch.

- name: Create Neon Branch
  uses: neondatabase/create-branch-action@v6
  id: create-branch
  with:
    project_id: ${{ vars.NEON_PROJECT_ID }}
    branch_name: feature-branch
    api_key: ${{ secrets.NEON_API_KEY }}
    get_auth_url: true
    get_data_api_url: true
- name: Use outputs
  run: |
    echo "Auth URL: ${{ steps.create-branch.outputs.auth_url }}"
    echo "Data API URL: ${{ steps.create-branch.outputs.data_api_url }}"

Introducing the new Neon VS Code Extension

The Neon VS Code Extension brings a revamped database development experience directly into your IDE. Connect to your Neon organizations, projects, and branches, browse schemas in a rich tree view, run SQL queries, and view or edit table data in a spreadsheet-like interface—all without leaving your editor.

This release replaces the previous Neon Local extension. The new extension no longer uses a local proxy or localhost connection strings. Instead, it helps you manage direct Neon connection strings for your branches.

The extension also automatically configures the Neon MCP Server, enabling AI-powered workflows for managing projects, branches, and databases from your coding agent.

Available for VS Code, Cursor, Windsurf, and other VS Code-compatible editors. Get started with the Neon VS Code Extension.

Neon VS Code Extension

Fixes & improvements
  • Instagres
    • Added a logical_replication option to Instagres databases (default is false). This lets sync engines spin up Postgres databases with logical replication enabled without needing to sign up for a Neon account to manually enable it.
  • Neon CLI
    • Fixed a misleading "org_id is required" error in the Neon CLI when running neon branches list without specifying a project. The CLI now provides clearer guidance when you have multiple projects, and automatically selects your project if you only have one. Upgrade your Neon CLI installation to get this fix. See upgrade instructions.
  • OpenTelemetry integrations
    • You can now edit endpoint and authentication credentials for existing OpenTelemetry integrations, enabling you to fix configuration issues without having to delete and recreate the integration.
  • Monitoring
    • Fixed monitoring graph x-axis labels to dynamically adjust based on the selected time range. When you zoom into a custom range on the graph, the labels now show more granular time information (hours instead of just day names) making it easier to read detailed metrics.
    • Fixed an issue on the monitoring page where clicking once on a chart would cause empty charts to display. Clicking on a chart now has no effect, preventing unintended empty range selections.
  • Postgres extension updates
    • Updated the anon extension (PostgreSQL Anonymizer) to version 2.5.1, which fixes a table name escaping bug that could cause anonymization failures.
  • Neon Console
    • Added a project count display to the Projects page in the Neon Console, making it easier to see how many projects you have at a glance.
    • Projects created from the Neon Console are now created with a production branch only. Previously, projects created in the Neon console included both production and development branches. Projects created via the Neon CLI or API are unaffected by this change.

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.

Dashboard page showing 100 Free Plan projects

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).

Address masking functions

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:

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).

Fixes & improvements
  • SQL Editor:

    SQL Editor commands like \d and \h now fully support all Postgres 18 features through an updated psql-describe package.

  • Neon Auth:

    • Added Vercel as an OAuth provider, enabling you to integrate Vercel authentication into your applications.
    • Now works with branch expiration.
  • Data Anonymization:

    • Materialized views are now automatically refreshed after data anonymization to prevent stale un-anonymized data from remaining in views.
    • GitHub Actions now supports creating anonymized branches directly in your CI/CD workflows using the new masking_rules input to specify which columns to mask.
  • Vercel Integration:

    • Added support for Vercel Marketplace to trigger database credential rotation for enhanced security.
    • Deleted Vercel integrations are now handled gracefully without triggering errors during operations.
  • Documentation:

    Added an Encore framework integration guide showing how to build backend applications with automatic infrastructure provisioning and Neon Postgres.

Was this page helpful?

Subscribe to our changelog.
No spam, guaranteed.