Databricks Lakebase
activeby Databricks · since 2025 · also known as Lakebase, Lakebase Postgres
Databricks' serverless Postgres built on Neon tech, with branching and sync to Delta tables in Unity Catalog.
Overview
Lakebase is Databricks' managed OLTP database: serverless PostgreSQL built on the storage and compute separation it acquired with Neon, wired into the Databricks platform. It offers autoscaling with scale-to-zero, instant copy-on-write branching, point-in-time recovery and high availability, plus synced tables that move data between Postgres and Delta Lake tables governed by Unity Catalog. That makes it a natural backend for Databricks Apps, AI agents and feature serving that need low-latency reads and writes next to lakehouse data. It reached general availability on AWS in January 2026 and on Azure in March 2026, supporting Postgres 16 to 18. Outside a Databricks estate, plain Neon is usually the simpler choice.
Strengths & trade-offs
Strengths
- +Postgres next to lakehouse data with managed sync to and from Delta tables
- +Unity Catalog governance and Databricks identity for OLTP data
- +Instant branching and scale-to-zero inherited from Neon
- +Low-latency serving layer for Databricks Apps, agents and features
- +Supports Postgres 16, 17 and 18
Trade-offs
- −Only usable inside a Databricks workspace
- −Young service; features rolling out region by region
- −Single-writer scaling; no sharding
- −Pricing in DBUs is harder to predict than plain per-hour billing
Great for
- +Backends for Databricks Apps and AI agents
- +Online feature and embedding serving from lakehouse pipelines
- +Operational stores whose data must land in Delta tables
- +Reverse-ETL style serving of gold tables to applications
Think twice for
- −Teams not already on Databricks
- −Very high write throughput needing horizontal scale
- −Multi-cloud or on-premises deployments
Capabilities
Native or official first-party support · 18 of 25 tracked
Scale & consistency
- Comfortable data size
- Medium · ≤ 10 TB
- Horizontal scaling
- None
- Multi-region
- No
- Transactions
- Full ACID
- Consistency
- Strong
- Schema
- Strict
- Architecture
- Serverless, Shared storage, Primary replica
- Query languages
- SQL, PL/pgSQL
Autoscaling single-writer Postgres with readable secondaries; storage up to 8 TB at GA.
Deployment
available on · AWS · Azure
Ecosystem
Alternatives to Databricks Lakebase
Serverless Postgres with copy-on-write branching and scale-to-zero, now part of Databricks.
lakebase vs neon →Serverless SQL warehouses on the Databricks lakehouse, powered by the Photon C++ engine.
lakebase vs databricks-sql →Fully managed cloud data warehouse with separate storage and compute, now spanning AI and apps.
lakebase vs snowflake →Open-source Postgres backend platform: database, auth, storage, realtime and edge functions in one project.
lakebase vs supabase →AWS's MySQL- and PostgreSQL-compatible engine on a shared, six-way replicated storage layer.
lakebase vs amazon-aurora →Google's Postgres-compatible service with disaggregated storage, a columnar engine and ScaNN vectors.
lakebase vs alloydb →Databricks Lakebase FAQ
What is Databricks Lakebase?
Databricks Lakebase is a relational database by Databricks, first released in 2025. Lakebase is Databricks' managed OLTP database: serverless PostgreSQL built on the storage and compute separation it acquired with Neon, wired into the Databricks platform. It offers autoscaling with scale-to-zero, instant copy-on-write branching, point-in-time recovery and high availability, plus synced tables that move data between Postgres and Delta Lake tables governed by Unity Catalog. That makes it a natural backend for Databricks Apps, AI agents and feature serving that need low-latency reads and writes next to lakehouse data. It reached general availability on AWS in January 2026 and on Azure in March 2026, supporting Postgres 16 to 18. Outside a Databricks estate, plain Neon is usually the simpler choice.
Is Databricks Lakebase open source?
No. Databricks Lakebase is proprietary, closed-source software.
Does Databricks Lakebase support ACID transactions?
Yes. Databricks Lakebase supports full ACID transactions, with strong consistency.
Does Databricks Lakebase scale horizontally?
Databricks Lakebase does not scale horizontally; it runs on a single node, so you scale it up rather than out. It is comfortable at medium scale (≤ 10 TB).
How can I run Databricks Lakebase?
You can use the vendor's managed cloud and run it serverless. Managed offerings include Lakebase. It is available on AWS and Azure.
What is Databricks Lakebase best for?
Databricks Lakebase is a strong fit for backends for Databricks Apps and AI agents; online feature and embedding serving from lakehouse pipelines; and operational stores whose data must land in Delta tables. Think twice for teams not already on Databricks.
What are the best alternatives to Databricks Lakebase?
Common alternatives to Databricks Lakebase include Neon, Databricks SQL, Snowflake, Supabase and Amazon Aurora. The right choice depends on your workload, scale and hosting; WhichDB's smart match ranks them against your requirements.
How popular is Databricks Lakebase?
Databricks Lakebase ranks #604 of 844 databases on the WhichDB Score (0.8/100), and #186 among relational databases. The score combines public adoption signals such as package downloads, GitHub activity, job posts and developer discussion.