On the radar·Lakebase·since July 2026 Beta

Lakehouse//RT

Analytics over live operational data in Lakebase, separate from registering the database as a Unity Catalog catalog.

Why it is worth watching

It is the answer to "can we report on the application database without copying it", and it is not settled yet.

What Beta promises

Open to most customers but not for production: support runs through engineering, and the shape of it can still move. On by default on Premium, off on Enterprise.

Who can use itMost customers
Production useNo
SupportEngineering only
On by defaultPremium yes, Enterprise no

The definitions are Databricks' own, on its release types page. The label on this page is the one the feature's documentation states, last checked on 15 Sept 2026.

Where to read more

It is part of something we wrote up: Registering a Lakebase database in Unity Catalog — A read-only Unity Catalog catalog that mirrors one Lakebase database, so Postgres tables can be discovered, governed and joined with Delta tables from a serverless SQL warehouse.

The Databricks documentation for Lakehouse//RT

Newsletter

Hear when Lakehouse//RT changes label

We re-read the documentation behind every preview and tell you when a label moves, or when a feature quietly disappears.

Choose what you get5 of 15

Each one is a section of the letter, and you only get the ones you tick. Every email carries a link back to this list, so you can change it later without an account.

Double opt-in: we send one email to check the address is yours. Nothing else until you confirm.