neon.ts config language ships; Functions, Storage, AI…

Jun 19, 2026– Refer a friend and earn credits, Neon backend private preview, and more

Refer a friend and earn credits

We're piloting a referral program. Send a friend your referral link, and when they sign up for Neon and spend $5, you get $5 in credits.

This is an early pilot, so we're still shaping it. Tell us what would make a referral program most useful to you, whether that's different rewards, how you share your link, or something else, in our Discord feedback channel.

Neon backend for apps and agents now in private preview

Neon Storage, Functions, and AI Gateway are now in private preview.

Functions: long-running Node.js compute next to your database. WebSocket servers, SSE streams, AI agents.
Storage: S3-compatible object storage that branches with your data.
AI Gateway: one credential for frontier and open-source models (Claude, GPT, Gemini, and more).

Get early access to the Neon backend platform

We're expanding Neon into a complete backend platform. Drop your email and we'll reach out soon for early access.

Get access

Introducing neon.ts: infrastructure as code for your Neon project

neon.ts is a TypeScript config file you commit to your repo. Use it as branch policy infrastructure as code (for example, TTL, compute sizing, and scale-to-zero settings), and to declare which Neon services your project uses:

import { defineConfig } from "@neondatabase/config/v1";

export default defineConfig({
  auth: true,
  dataApi: true,
  branch: (branch) => {
    if (!branch.exists) {
      return {
        ttl: "7d",
        postgres: {
          computeSettings: {
            autoscalingLimitMinCu: 0.25,
            autoscalingLimitMaxCu: 1,
            suspendTimeout: "5m",
          },
        },
      };
    }
    return {};
  },
  preview: {
    functions: { /* ... */ },
    buckets: { /* ... */ },
    aiGateway: true,
  },
});

Apply it with neonctl deploy, preview changes first with neonctl config plan. The @neondatabase/env package gives you type-safe access to the environment variables each declared service injects, so missing or misconfigured variables surface at build time rather than runtime.

If you've signed up for the Neon backend for apps and agents private preview, the preview block enables Functions, Storage buckets, and AI Gateway in the same config. Fork a branch and you get an isolated copy of your database, files, storage, functions, and AI gateway.

See the neon.ts reference for the full config schema, or read the blog post for a full walkthrough.

Export Neon metrics to SigNoz

This new guide shows how to export your Postgres logs and metrics to SigNoz using the Neon OpenTelemetry integration. Once set up, your database telemetry lands alongside your application data in SigNoz, making it easier to spot and investigate performance issues across your stack.

Send Postgres logs and metrics from Neon to SigNoz

Fixes & improvements

Neon API

The deprecated GET /consumption_history/account endpoint has been removed. Use GET /consumption_history/v2/projects instead. See Querying consumption metrics for details.

Vercel integration

For Neon-Managed (Connectable Account) Vercel integrations, rotating the selected Postgres role password in Neon now automatically syncs updated credentials to Vercel environment variables. This removes the need to manually re-save integration settings after password rotation.

neon.ts config language ships; Functions, Storage, AI Gateway in private preview