Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Important
Lakebase Provisioned is the original Lakebase offering that uses provisioned compute you scale manually. For supported regions, see Region availability. For the latest version of Lakebase, with autoscaling compute, scale-to-zero, branching, and instant restore, see Lakebase Autoscaling.
New Lakebase instances will be created as Autoscaling projects. Rollout starts March 12, 2026. For details, see Autoscaling by default.
Lakebase is a fully managed Postgres online transaction processing (OLTP) database engine integrated into the Databricks Data Intelligence Platform. Lakebase lets you create and manage OLTP databases stored in Databricks-managed storage, integrating with your Lakehouse for real-time transactional workloads.
Database instance architecture
A database instance manages storage and compute resources and provides the endpoints that users connect to.
- Compute nodes: One node is the primary, handling write operations. Secondary nodes are optional, separated across zones for high availability. Compute nodes can be paused, retaining storage while halting compute resources.
- Endpoints: The default endpoint routes read and write requests to the primary. Optional read-only endpoints route to secondary nodes.
- Failure handling: If the primary node fails and high availability is configured, a secondary node automatically takes over.
Limitations
- A workspace allows a maximum of ten instances.
- Each instance supports up to 1000 concurrent connections.
- The logical size limit across all databases in an instance is 2 TB.
- Database instances are scoped to a single workspace and don't support cross-workspace access.
- Databricks recommends configuring Private Link as a security best practice.
Learn about Lakebase Provisioned
| Topic | Description |
|---|---|
| Postgres roles | Understand pre-created roles and how to manage roles for Databricks identities. |
| PostgreSQL compatibility | Learn about PostgreSQL compatibility, limitations, and optimization tips. |
Get started with Lakebase Provisioned
For database owners and admins
If you're setting up a new Lakebase database for your team:
| Task | Description |
|---|---|
| Create a database instance | Set up your first Lakebase Provisioned database. |
| Add users and set permissions | Give other users access to your database and control what they can do. |
For database users
If you need to access an existing Lakebase database:
| Task | Description |
|---|---|
| Connect to your database | Get the credentials you need to access your Lakebase database. |
| Query your data | Use various tools to query your PostgreSQL data including SQL editor, notebooks, and psql client. |
Data integration and synchronization
Connect Lakebase with your existing Databricks data and workflows.
| Topic | Description |
|---|---|
| Register with Unity Catalog | Optionally register your PostgreSQL database as a catalog in Unity Catalog for federated queries. |
| Serve lakehouse data with synced tables | Create synced tables to serve Unity Catalog data through your Lakebase database instance for operational applications. |
Advanced features
Explore advanced capabilities for production workloads and enterprise use cases.
| Topic | Description |
|---|---|
| Restore data and time travel | Use child instances to perform time travel and restore data to specific points in time for data recovery, compliance auditing, and development environments. |
| Monitoring and observability | Monitor your database performance and health using built-in metrics and logging. |
Advanced configuration
Explore advanced capabilities for production workloads and enterprise use cases.
| Topic | Description |
|---|---|
| High availability | Configure high availability for your database instances to ensure business continuity. |
| Restore window | Set the restore window for your database instance for point-in-time recovery. |
Region availability
Supported regions:
westuswestus2eastuseastus2centralussouthcentralusnortheuropewesteuropeaustraliaeastbrazilsouthcanadacentralcentralindiasoutheastasiauksouth
Feature comparison
The following table compares capabilities in Lakebase Autoscaling and Lakebase Provisioned.
Note
Lakebase Autoscaling is the new version of Lakebase. New feature development is focused on Lakebase Autoscaling.
New Lakebase instances will be created as Autoscaling projects. Rollout starts March 12, 2026. For details, see Autoscaling by default.
| Feature | Autoscaling | Provisioned |
|---|---|---|
| Core capabilities | ||
| Provisioned (fixed-size) compute | ✓ | ✓ |
| Autoscaling | ✓ | |
| Scale to zero | ✓ | |
| Branching | ✓ | |
| Instant restore | ✓ | |
| Point-in-time restore | ✓ | ✓ |
| Read replicas / readable secondaries | ✓ (Read replicas, readable secondaries) | ✓ (Readable secondaries) |
| High availability | ✓ | ✓ |
| Inbound Private Link | ✓ | ✓ |
| Inbound Private Link for performance-intensive services | ✓ | |
| Compliance security profile | ✓ (set to HIPAA, C5, TISAX, or None) | |
| Customer-managed keys (CMK) | ✓ | |
| Data integrations | ||
| Unity Catalog registration | ✓ | ✓ |
| Synced tables (serve lakehouse data with Lakebase) | ✓ | ✓ |
| Lakehouse Sync (sync Lakebase tables to Delta/Iceberg tables) | ✓ Public Preview | |
| Query federation | ✓ | ✓ |
| Application integrations | ||
| Databricks Apps | ✓ | ✓ |
| Feature Store | ✓ | ✓ |
| Notebooks | ✓ | ✓ |
| Stateful AI agents | ✓ | ✓ |
| Access control | ||
| UI for Postgres role management | ✓ | ✓ |
| Workspace ACLs | ✓ | ✓ |
| Developer tools | ||
| Infrastructure as code (Asset Bundles, Terraform) | ✓ (Beta) | ✓ |
| Programmatic access (REST API, CLI, SDKs) | ✓ (Beta) | ✓ |
| PostgREST API support | ✓ (PostgREST-compatible Data API) | ✓ (Private Preview) |
| Cost management | ||
| Tags and serverless usage policies | ✓ | ✓ |