Neon now has realtime
Neon Realtime is live in public beta. Any SQL query can now be a live query. Subscribe to it and the result stays up to date as your data changes. That makes your whole app reactive, with no polling…
Blog — Neon Docs
The latest product updates from Neon
October 2026
BM25 is only as good as your tokens
Lakebase Search is the search primitive of the Neon backend. One of the best things about it is that it ranks keyword results with BM25. That said, BM25 can only score the terms it's given.
Building a searchable photo library on the Neon backend with TanStack
A photo library looks simple, but each photo carries files, metadata, vectors, and an owner. Atlas is a TanStack Start app that keeps all of it on the Neon backend, so one branch gives you a full pre…
Generate embeddings with Neon AI Gateway
Neon AI Gateway now serves embedding models on the same OpenAI-compatible endpoint and with the same credential you already use for chat. Generate vectors, store them in Lakebase Postgres, and query…
Neon gives you 100 projects for free, with 1 GB of Postgres storage each
Database storage on the Neon Free plan is now 1 GB per project, up from 0.5 GB. You still get 100 projects, with existing projects getting the new limit automatically.
Announcing @neon/effect
@neon/effect brings the Neon SDK to Effect. Provision projects and branches, handle tagged errors and compose infrastructure workflows with retries, cancellation and timeouts.
pg_redact: Content-aware PII redaction with Jev, enforced in Postgres
PII redaction in Postgres today works column by column. Its limitation is that it only works when each piece of personal data has its own column, which is rarely the case with free text.
September 2026
How we systematically improved our reliability
Earlier this year, we had two incidents in one week. After those incidents, we doubled down on reliability. This post summarizes the reliability work we've been rolling out since then to keep uptime…
Lakebase Search: the retrieval primitive for agents on Neon
Build the search engine, ingestion layer, and serving layer for agent retrieval with Lakebase Search, Functions, Object Storage, and AI Gateway.
Inside Skydive: building virtual coworkers, powered by Neon
Skydive is a platform that lets teams build AI coworkers that do real work. When a Skydive agent needs a durable state, it deploys an isolated Neon backend mid-task, with no human in the path, and it…
Inside branch-based restores in Lakebase Postgres
Restores are broken in managed OLTP, and they have been broken for a long time. They are slow, and they get slower with scale. The databases that need recovery most, the large production ones, are th…
Electrifying Neon: building the realtime backend
Now that we've announced GA for Neon's complete backend, one of the things we're most excited about coming next is adding realtime to the Neon platform. Not least because it's being worked on by the…
When a file is uploaded, run the job on Neon
A file in a bucket is just bytes; when you upload it, there is often a job to do next with that file, and that job usually involves Postgres - a `files` row, a status, a thumbnail key. That is a perf…
Custom domains for Neon Functions
During beta, each Function was reachable only at its Neon invocation URL, something like `https://br-cool-forest-a1b2c3d4-api.compute.c-2.us-east-2.aws.neon.tech`. Now, we support custom domains - yo…
Your Neon Functions can now run on a schedule
During the beta phase, the only way to run a Neon Function was to send it an HTTP request. That works well for jobs triggered by your app, but not so much for backend jobs. If you wanted to pull an e…
The Neon backend is GA: a complete set of primitives so agents can build
Neon is now a complete suite of backend primitives built around the database and rooted on the lakebase architecture: Lakebase Postgres, Object Storage, Functions, Managed Better Auth, and AI Gateway…
Inside LuBot's database-per-tenant architecture
It took six days to go from zero to isolated Postgres per tenant, provisioned the moment someone pays. A traditional Postgres setup would have been a full quarter of work.
Claimable Neon: Provisioned by agents, claimed by humans
Claimable Neon implements the anonymous registration method in auth.md, the open agent registration protocol authored by WorkOS, to give agents a way to provision a temporary Neon project without cre…
Improving Lakebase Postgres Compute Cache on Neon, Part 1
On large fixed-size Lakebase Postgres computes on Neon, we now put most of the machine's memory into Postgres shared buffers and back that cache with huge pages. Hot pages stay in DRAM instead of fal…
Comparing token economics across 42 AI models
If headcount is often a company's largest cost, tokens will be a close second soon as agents take on more work. Imagine how much $$ a software company will be able to save just by pre-selecting model…
Give your agent Neon tools
Today we're launching @neon/tools, a package that turns the @neon/sdk ergonomic client into typed agent tools with adapters for MCP, Mastra, and Eve. We're also using it to expand the hosted Neon MCP…
Building patterns unlocked by scale to zero
Most hosted Postgres pricing works like this: you pick an instance size, the vendor assumes the instance will run for about 730 hours a month, and you pay for those hours. Lakebase Postgres addresses…
Neon is now available in Grok Bot
Neon is now available as a plugin in Grok Bot. You just have to connect your Neon account once and you'll be able to ask a Grok bot to build on Neon.
August 2026
Autoscaling Lakebase Postgres
Choosing a database instance size before you know the workload is an old building pattern. Lakebase Postgres omits the sizing experience altogether thanks to autoscaling.
Introducing Neon Labs
Today we're launching Neon Labs, a home for experimental tools built around Lakebase Postgres. We want Neon Labs to be a playground for ideas that could help the broader Postgres community.
Just landed in the Neon CLI
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.
WAL + S3: Lakebase storage for the era of agents
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 fr…
Open-weight models are fast on Neon AI Gateway. Here's why
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-hoste…
Query Neon backend logs
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, wi…
LLMs belong in your backend
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.
Neon skills landed in the Vercel CLI
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…
Neon for Herdr: A Neon pane in your Herdr workspace
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 com…
Neon Functions: backend logic next to your data
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…
Electric is joining team Neon at Databricks
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 Dat…
Building Neon Object Storage
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…
Training 100x Cheaper Retrieval models Neon and Castform
“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 sca…
Neon now has per-project permissions
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 a…
July 2026
CommSync Runs Text, Vector, and Hybrid Search on Postgres with Lakebase Search
"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."
My agent cloned GitHub (sort of) using the Neon backend
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…
Debug your Postgres from the terminal: a tour of `neon inspect db`
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…
Test out the Neon backend: Object Storage, Functions, and AI Gateway are beta
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…
Introducing @neon/sdk, our new TypeScript client for the Neon API
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 o…
Introducing the New Neon API Command
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…
Provision Your Entire Stack with Neon and Stripe Projects Build
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 scaffol…
Lakebase Search: vector and BM25 on Neon
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…
June 2026
Introducing neon.ts: infrastructure as code for your Neon projects
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…
You (And Your Agent) can provision Neon in Vercel CLI
The Vercel CLI now lets agents provision a database for your project with a single command from your terminal: 𝚟𝚎𝚛𝚌𝚎𝚕 𝚒𝚗𝚝𝚎𝚐𝚛𝚊𝚝𝚒𝚘𝚗 𝚊𝚍𝚍 𝚗𝚎𝚘𝚗
Shipping psql without psql: a pure-TypeScript Postgres client in neonctl
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 unco…
A branch-first dev loop for Neon: link, checkout and env pull
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 de…
I Slop Forked Neon. You Should Too.
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 functionali…