The Neon CLI moved fast over the last couple of months. It is a key tool for agents, who do all the work without ever opening the Console - let’s take a look at some of recent changes.

Agents treat code as lightweight: branch it, deploy it, throw it away. The infrastructure under that code should work the same way. Working with an OLTP database is traditionally heavy and full of friction, but very little of that is a Postgres problem.

Open-weight models are built for performance, but how they're served determines whether end users actually feel that speed. Neon AI Gateway calls Databricks Foundation Model APIs for Databricks-hosted open-weight models, a stack that has years of inference engineering behind it.

We keep expanding our backend observability - the most recent addition: you can now query backend logs outside the Console! neon logs reads what Neon Functions and Object Storage emit on a branch, with filters for source, severity, and message text.

Neon Functions are Node.js 24 compute you deploy onto a Neon branch, in the same region as your Lakebase Postgres database, with DATABASE_URL injected automatically. They're long-running enough that agents can stream for minutes and WebSockets or SSE can stay open while data flows.

Neon AI Gateway is how we put LLM calls into the Neon backend the same way we put files, functions, and auth there. It allows you to call models right from Neon, instead of collecting lab accounts.

Vercel just gave their CLI a new trick: when you install a Marketplace integration from the terminal, it also installs that provider's agent skills. A single command now provisions a Neon database on your Vercel project and hands your coding agent the instructions it needs to actually use it.

I just released Neon for Herdr, a Herdr plugin that puts your Neon projects in a pane next to whatever you are already doing, so creating a branch, grabbing its connection string, or suspending a compute is only a keypress away.

Today Databricks announced that Electric, the team behind PGlite and the Electric sync engine, is joining Databricks. We have our own reason to celebrate: Electric is joining the Neon team within Databricks, bringing lightweight WASM Postgres + real-time sync to Neon.

We just launched Neon Object Storage, a branch-aware, S3-compatible object store built into the Neon backend. If you've used Neon branches before, you know the workflow: branch main into a child and get an isolated copy of your database in about a second. Object Storage adds files to that picture.

“Most teams' best training data is just sitting in their databases. The problem is that turning raw data into something usable is hard, and letting agents read, search, and mutate data cheaply at scale requires advanced infra. Pointing Castform at Neon skips both.” — Ying Hang Seah, cofounder, Castf...

Neon now supports a new permission structure, with four org-level roles (Admin, Editor, Viewer, and Collaborator) and per-project permissions that let you control exactly which projects your agents and collaborators can access.

"We're running lakebase_text and lakebase_vector across three different parts of our product. Query latency improved 1,000x and we don't need a separate search stack sitting next to our Postgres."

GitHub has been down a lot lately. During one of those episodes, I had the idea of asking my agent to use our new backend suite (still in beta) to build a working Git host. This is genuinely outside of my comfort zone as I had no prior knowledge of Git server internals, so I didn't have much hopes, ...

The Neon CLI now ships `neon inspect db`: read-only, high-signal Postgres diagnostics that answer "what is slow?" without leaving the terminal or writing a single catalog query. Each subcommand runs one known-good query against Postgres' own statistics and catalog views and prints a clean table (or ...

Storage, Functions, and AI Gateway are now in beta and available to all users: object storage that branches with your data, long-running compute that lives next to your database, and one API with one bill for seven model providers backed by Databricks. Let your agent deploy a full Neon backend by de...

CLIs have become the default tool for AI agents because they package complex environments into predictable commands. But human-friendly CLIs lag behind the underlying API, and letting agents call the raw API risks leaking secrets. `neon api` closes both gaps.

A few months ago, Stripe changed how we think about backend infrastructure by launching Stripe Projects. Today, Stripe is taking it one step further with `stripe projects build`. Discover and scaffold fully wired templates in a single command.

The Neon API is open and follows the OpenAPI spec, so you can provision and manage almost everything you see in the console programmatically. But provisioning infrastructure over REST means polling operations until resources are ready. @neon/sdk adds an ergonomic, type-safe layer on top so platforms...

Today we're shipping the beta of Lakebase Search on Neon: hybrid vector + full-text retrieval via two Postgres extensions, lakebase_vector and lakebase_text. This post is the story of why and how we built it: IVF + RaBitQ instead of HNSW, BM25 with top-K pushdown instead of GIN on tsvector, and inde...

As Neon turns into a platform with backend primitives for apps and agents, provisioning those primitives matters more than ever. neon.ts is our branch config and infrastructure-as-code file: declare your Neon services, get type-safe environment variables and program your branch settings, all in Type...

The Vercel CLI now lets agents provision a database for your project with a single command from your terminal: 𝚟𝚎𝚛𝚌𝚎𝚕 𝚒𝚗𝚝𝚎𝚐𝚛𝚊𝚝𝚒𝚘𝚗 𝚊𝚍𝚍 𝚗𝚎𝚘𝚗

We're hard at work on the private preview of Neon Platform and along the way we're rethinking Neon's branch-first developer experience. First up: three new Neon CLI commands that turn branch-first development into a tight, repeatable loop for both humans and agents.

neonctl psql used to fail with "command not found" whenever psql wasn't on your PATH — which is most macOS laptops, slim Linux containers, Windows boxes, CI runners, and sandboxes. So we did the uncomfortable thing: reimplemented the psql client in pure TypeScript, embedded it in the CLI, and built ...

Agents are much better at using APIs, CLIs, and MCP servers than clicking through dashboards. That's why APIs matter even more in the age of agents. At Neon, we aim to expose all platform functionality through our open API — if you see an action in our console, the associated endpoint should be open...

Starting June 1, 2026, every Neon paid plan includes 500 GB of data transfer per month, up from 100 GB — enough to remove egress charges for most workloads. The change is automatic and appears on your June invoice.

Recently, everyone has been talking about throwing it all away and building entirely new magic sci-fi cloud infrastructure for agents. Building real infrastructure is hard enough as it is. AI has only raised the stakes, dialing up the operational requirements and pushing the limits on every axis ima...

In the last year, agents have strained the limits of cloud infrastructure with new usage patterns: higher throughput of control-plane operations, more demand for on-demand infrastructure, and capacity crunch. The resulting spate of failures and incidents amongst cloud services has taught us lessons ...

We've been working on neon-for-agent-platforms, a companion skill that complements our existing neon-postgres skill. The existing skill covers auth, drivers, branching, the Data API, MCP, and core Postgres-on-Neon guidance. Agent platforms have a different problem though: they don't just use one dat...

Thanks to Neon's lakebase architecture with separation of storage and compute, we've managed to give customers up to 5x performance increase on write-heavy workloads by disabling full-page writes.