On 14 May 2025 Databricks announced it would acquire Neon, a serverless Postgres company. Fifteen months later Lakebase, the product Neon became, is named in the headline of the company's August 2026 funding release as one of three products the new capital goes into. That is a fast promotion for a database, and it tells you what the lakehouse was missing.
Where the lakehouse stopped #
A lakehouse is very good at the analytical half of a company's data. Tables in object storage, one catalog, cheap to keep everything, and a query engine that scales to whatever you point it at. What it was never built for is an application: a screen that reads one customer's record and writes it back in the time it takes a person to blink. Every team that tried to build an app straight on the lakehouse learned this on the second day, and every one of them then ran a Postgres beside it with a copy job between the two. Two systems, one sync, and a permissions model that had to be maintained twice.
What Lakebase is #
Buying Neon was Databricks admitting that. Lakebase is a real Postgres, registered in Unity Catalog, with lakehouse tables synced into it and the operational data living beside the analytics under one set of grants. The stack most teams run as three systems and two copy jobs collapses into one, and an agent answering questions over the same data inherits the user's permissions instead of a prompt telling it what not to say.
Built in a room #
We built an application on Lakebase live at the first Gilbert Databricks User Group session on 18 September 2026, in front of a room, with the seams left visible. The recording goes on the events page afterwards. The honest edges, meaning what's generally available and what's still in preview, are in the chapter and were in the room, because a recommendation that can't say where it stops isn't one.
Where the money goes next #
Three products got named in that release, Lakebase, Genie and Unity AI Gateway, and all three sit closer to the end user than anything the company sold in 2023. The platform is moving from where data is kept to where it's used, and the applications and agents on top of it are where the Databricks Apps and Agents chapters now spend most of their words.