Lakebase

Lakebase is the current Databricks name, previously Lakebase Autoscaling (since August 2026).

Lakebase Provisioned → Lakebase Autoscaling → Lakebase

A fully managed, serverless Postgres (OLTP) database integrated into the Databricks platform, for building real-time transactional apps alongside lakehouse data.

• The name has been handed down once already: it debuted in June 2025 on a Postgres you sized by hand, and by August 2026 the docs describe the autoscaling platform that replaced it as 'now known simply as Lakebase'. 🔗
• In August 2025 the Compute section's 'OLTP Database' tab was quietly renamed 'Lakebase Postgres.' 🔗
• You can debug it by talking to it - database issues and early warnings surface as Insights and you investigate them conversationally with Genie, all fed by database telemetry captured into Unity Catalog. 🔗

⚠ Limitations: Lakebase Postgres enforces per-project limits: a default of 20 concurrently active computes (the default branch is exempt, and Support can raise the limit), up to 500 branches per project, 500 Postgres roles and 500 databases per branch, 6 read replicas per branch, a 16 TB storage quota per branch that Support can also raise, up to 1000 projects per workspace, and a history retention window of at most 30 days. 🔗

Category

Data engineering

In use from

August 2026🔗

Announced at

GA announcement blog, February 2026🔗

Also known as

Lakebase Postgres, OLTP Database, Databricks Postgres

Verified

2026-09-10