Team accounts with unlimited members now available to everyone! Invite your teammates and ship faster together, even on the Free Plan.
Neon
    Docs
    Log inSign up
    /Changelog

    Changelog

    The latest product updates from Neon

    Neon Postgres in Stripe Projects

    Neon is now part of Stripe Projects. Stripe Projects is a Stripe CLI workflow for hooking an app up to backends. You pick services from a catalog (databases, hosting, auth, and more), provision them into your provider accounts, and get connection strings and keys in your environment so your agent can run against a live backend.

    Example Stripe CLI flow (after you install the Stripe CLI):

    stripe projects init my-app   # set up your project
stripe projects catalog        # browse available services
stripe projects add neon/postgres       # provision a Neon database

    Learn more in Neon works with Stripe Projects for agentic provisioning.

    Automatic cache prewarming for compute updates

    To apply updates to your Neon compute (Postgres upgrades, security patches, and the like), we restart the compute where Postgres runs during your update window. The restart itself typically takes only a few seconds, but in-memory caches are left cold, which can impact query performance until they warm up again.

    To protect performance, we now prewarm your compute's cache during the update process without affecting restart times. There are no additional compute or storage costs associated with this enhancement.

    For the technical details, see our blog post: Zero-Downtime Patching Part 1: Prewarming.

    Neon Auth webhooks walkthrough with Resend

    We announced support for Neon Auth webhooks a couple of weeks ago. With webhooks, your app receives auth events over HTTP so you can send OTPs and other auth messages through your own email, SMS, or WhatsApp providers, validate signups, or sync to other systems.

    This week we have a new guide, Customizing Neon Auth with Webhooks, that walks you through setting up a Next.js app that handles webhooks, sends OTP email with Resend, tests locally with ngrok, and uses a blocking handler to reject signups you don't want. You can reference this guide alongside our Webhooks docs when you are ready to implement.

    AI agents and instant database branching

    Neon's instant database branching and AI coding agents work well together. Branching gives each run an isolated Postgres database in seconds, so agents can perform schema migrations, run tests, and try risky changes safely. The new guides below demonstrate this workflow with Codex and Claude Code.

    One-command setup for more AI assistants

    The npx neonctl@latest init command, which sets up Neon and configures the Neon MCP Server for you, now supports more AI assistants including VS Code, Claude Code, Cursor, Claude Desktop, Codex, OpenCode, Antigravity, Cline, Cline CLI, Gemini CLI, GitHub Copilot CLI, Goose, MCPorter, and Zed.

    Run it from the root directory of your project:

    npx neonctl@latest init

    The init command uses add-mcp to configure the Neon MCP Server for your AI assistant. See Supported agents (add-mcp) for the full list of supported agents.

    Request billing support from the Billing page

    Request billing support button

    Paid plans can open Request billing support on the Billing page. The form lets you choose an invoice and describe your issue.

    New examples and guides

    Unlimited Neon org members on the Free plan

    You can now add unlimited members to each organization on the Free plan. Collaborate with teammates, invite others to your org, or keep separate workspaces for personal projects, side projects, and collaborations.

    Unlimited members on the Free plan

    What are orgs and members?

    An organization is a workspace that owns Neon projects and where you manage projects and collaborate. Members are people you invite to your organization. Learn more.

    With unlimited members, listing them efficiently matters. The API for listing organization members now supports pagination and sorting, and the Console members page supports sorting and pagination. Member objects also include an optional has_mfa field, and the Console shows a 2FA indicator, following the recent introduction of two-factor authentication (2FA).

    Organizations API example
    # First page
curl -X GET \
  'https://console.neon.tech/api/v2/organizations/{org_id}/members?limit=20&sort_by=joined_at&sort_order=desc' \
  -H 'Authorization: Bearer $NEON_API_KEY'

# Next page (use cursor from response.pagination.next)
curl -X GET \
  'https://console.neon.tech/api/v2/organizations/{org_id}/members?limit=20&cursor=...' \
  -H 'Authorization: Bearer $NEON_API_KEY'

    Response includes pagination.next for the next page and, per member, a user object that may include has_mfa:

    "user": { "email": "user@example.com", "has_mfa": true }

    Neon Auth

    We're introducing two new Neon Auth features this week.

    Organization settings. You can now configure Organizations for Neon Auth from the Neon Console. Go to Auth > Configuration > Organizations (per branch) to enable or disable the plugin, set the maximum organization memberships per user and the maximum members per organization, choose the creator role (owner or admin) for new organizations, and control whether invitation emails are sent. These settings support multi-tenant apps where users create and join organizations. See Organization in the Neon Auth docs.

    Auth Configuration > Organizations in the Neon Console

    Webhooks. Introducing Neon Auth webhooks. Configure webhooks to receive HTTP POST requests when authentication events occur (OTP delivery, magic link delivery, user creation). Use them to replace built-in email delivery with your own channels (SMS, custom email, WhatsApp), validate signups before they complete, or sync new users to CRMs and analytics. The guide covers event types, API configuration, payload structure, signature verification, expected responses, retry behavior, and testing. See Webhooks.

    New NAT gateway IPs and VPC endpoint services in US East (N. Virginia)

    We've expanded infrastructure capacity in the AWS US East (N. Virginia) region (us-east-1) with new NAT gateway IP addresses and new VPC endpoint service addresses for Private Networking.

    Update your IP allowlists

    If you have IP allowlists on external systems that Neon connects to, update those allowlists to include the new NAT gateway addresses. Connections may be affected intermittently if traffic routes through non-allowlisted NAT gateways.

    If you use Private Networking in us-east-1, you can now use the additional VPC endpoint service addresses for enhanced capacity and reliability. See the Regions documentation for the complete list of NAT gateway IPs and the Private Networking guide for VPC endpoint service addresses by region.

    Stay on top of network transfer costs

    Network transfer monitoring

    Network transfer (egress) is data sent from your Neon databases to clients. It's one of the usage metrics that affects your bill on paid plans, and many teams only notice it when it shows up as a line item.

    We've added two things to help. First, a guide that explains what network transfer is, what typically drives it (queries, pg_dump, logical replication, log export), how to monitor it in the Console and via the Consumption API, and how to manage or reduce usage. See Reduce network transfer costs.

    Second, an agent skill that guides your AI assistant through diagnosing and fixing application-side query patterns that cause excessive egress. The skill walks through analyzing your codebase for anti-patterns (such as SELECT *, missing pagination, high-frequency queries on static data, and application-side aggregation), applying fixes, and verifying with tests. To add it:

    npx skills add neondatabase/agent-skills -s neon-postgres-egress-optimizer
    Was this page helpful?