You don’t need a vector database - just use Postgres for everything. Read the case study on switching from Pinecone to Neon

Changelog

The latest product updates from Neon

RSS feed

Accelerate development with the Neon Local Connect VS Code Extension

The Neon Local Connect VS Code Extension lets you develop with Neon using a familiar localhost connection string. Your app connects to localhost:5432 like a local Postgres instance, but the underlying Neon Local service routes traffic to your actual Neon branch in the cloud.

Neon Local Connect VS Code Extension

Key features:

  • Static connection string: Use postgres://neon:npg@localhost:5432/<your_database> for all branches — no need to update your app config when switching branches
  • Branch management: Create, switch, or reset branches directly from the VS Code panel
  • Ephemeral branches: Automatically create and cleanup temporary branches for testing and experiments
  • Integrated tools: Launch psql shell, SQL Editor, or Table View without leaving your IDE

The extension is available on both the VS Code Marketplace and OpenVSX Marketplace (for Cursor, Windsurf, and other VS Code forks).

Learn more in our docs: Neon Local Connect VS Code extension.

app.build adds Python support

app.build, our open-source agent for turning AI-generated code snippets into full-stack, deployed applications on Neon, now supports building data apps and ML dashboards with Python.

You can try it today:

npx @app.build/cli --template=python

appdotbuild python example

To learn more about app.build and its capabilities, read the blog post and visit app.build.

Storage performance improvements

We’ve made several upgrades to Neon’s storage layer to make your databases faster—especially for large and write-heavy workloads. Improvements include smarter sharding, compressed WAL transmission, faster disk writes, and more responsive compaction.

Most users will see better ingest performance, lower read latency, and faster uploads automatically.

Learn more in our blog post: Recent Storage Performance Improvements at Neon

Fixes & improvements
  • Neon MCP

    • Addressed an issue where required tool parameters, such as org-id, were being passed with empty values, resulting in an undefined error.
    • We updated our security guidance for the Neon MCP Server. To learn more, see MCP security guidance.
  • Neon API

  • neon_superuser

    The neon_superuser role is now granted the pg_signal_backend privilege, which allows it to cancel (terminate) backend sessions belonging to roles that are not members of neon_superuser.

    Roles created in the Neon Console, CLI, or API, are granted membership in the neon_superuser role. To learn more about this role, see The neon_superuser role.

  • Fixes

    Resolved an issue on the Tables page in the Neon Console where the previously selected database was incorrectly cached across projects. This caused errors when switching to a project that didn’t include the cached database. The Tables page now correctly resets the selected database when switching projects.

Meet your new Neon AI Assistant

We’ve launched a new Neon AI Assistant, available for all Launch and Scale plan users. Find it under ? > Get help in the Console. Our AI assistant can help:

  • Answer questions about Neon features, workflows, and troubleshooting.
  • Find relevant documentation and best practices.
  • Create support tickets related to your issue, connecting you directly with our support team when you need deeper help.

Neon AI Assistant in Console

Delete Neon Auth users from the UI

You can now delete Neon Auth users directly from the Auth UI (or programmatically via the Delete Auth User) API endpoint. This action soft-deletes the user in neon_auth.users_sync by setting the deleted_at column, rather than removing the record entirely.

Delete Neon Auth user from UI

Previously, deleting a user required running a SQL statement against the neon_auth.users_sync table. You may still want to use SQL deletion if you need to fully remove a user and all associated data.

Collapsible console sidebar

You asked, we delivered. The Neon Console sidebar is now collapsible, giving you more space to focus on your work. Good for smaller screens or when you just need a little extra room.

Screenshot of collapsible Neon Console sidebar

Improved branch creation page

We’ve added some polish to our branch creation page to make it easier to understand your options.

New branch creation page

  • You can now choose between Current data, Past data, Schema-only, and Anonymized data branch options, all from a streamlined, modal-style layout.

  • The page now displays the size limit for schema-only branches based on your plan, so you’ll know up front how much data you can seed or add.

  • There’s now a direct link to our anonymization docs in the Anonymized data option, a reminder that you can anonymize data manually while we work on full in-app support.

    size limit in schema only branch creation

Fixes & improvements
  • Neon Console

    • When adding an OpenTelemetry (OTel) integration, credential validation is now non-blocking. If we detect an issue, you’ll see a warning, but you can still continue if you choose to. Useful for connecting to a provider we can't fully validate yet.
  • Drizzle Studio update

Give your computes a custom name

You can now assign custom names to your branch’s computes. In the Neon Console, go to the Branches page, select a branch, and open the Compute tab. Click the edit icon next to a compute to rename it.

Naming computes

You can also set a name when adding a new compute.

This enhancement is supported for both primary (read-write) and read replica computes.

TanStack integration & new open-source tools for JavaScript developers

We're excited to announce that Neon is now the official database partner of TanStack, and that we’ve released new open-source tools to simplify Postgres integration across the TanStack and Vite ecosystems:

  • Create TanStack Add-on
    Instantly set up a fullstack application with a Neon Postgres database with one simple command: pnpm create tanstack --add-on neon

  • Neon Launchpad
    Instantly spin up a Postgres database with Neon Launchpad — no signup required. Perfect for workshops and rapid prototyping. Try it at neon.new. To learn more, see our Neon Launchpad docs.

  • NeonDB (CLI + SDK)
    Bootstrap Neon Postgres database with the neondb CLI:
    npx neondb --yes
    Or integrate programmatically via instantNeon().

  • Vite Plugin for Neon
    Use Neon Launchpad to spin up a Postgres database with any Vite app:
    npm add -D @neondatabase/vite-plugin-postgres

These open-source tools are designed to streamline fullstack development with TanStack, Vite, and Postgres. Learn more:

OAuth provider management for Neon Auth

You can now manage your project's OAuth providers (Google, GitHub, Microsoft) directly in the Neon Auth config tab—enable or disable providers, and choose between using shared Neon Auth credentials or setting up your own custom client credentials.

New API endpoints also let you manage providers programmatically:

To learn more, see the Neon Auth documentation.

Fixes & improvements
  • Neon CLI

    • The Neon CLI now supports a --name option that you can use when adding a compute or a read replica to a Neon branch.

      neon branches add-compute mybranch --name myreplica --type read_only
    • The CLI now automatically detects invalid credentials (401 responses), deletes them, and prompts for re-authentication instead of failing immediately

      🚀 If you're not using the Neon CLI yet, get set up in just a few steps with the Neon CLI Quickstart.

  • Fixes

    • Addressed an issue where projects created via Netlify DB and claimed into Vercel-managed org accounts could lose certain project configuration settings. To avoid this issue, transfers of projects created via Netlify DB to Vercel-managed org accounts are currently not supported.
Was this page helpful?

Subscribe to our changelog.
No spam, guaranteed.