Data-driven apps

Sometimes a dashboard isn't enough and you need a real application: a data-entry screen, an approval flow or a data product. With Databricks Apps I build and host those applications directly on the platform, with Lakebase (managed Postgres) as a fast operational layer that integrates directly with the Lakehouse.

Some processes need more than a report: a data-entry screen for corrections, an approval flow, a data product for customers. With Databricks Apps I build those applications on the platform itself, next to the data, with the same Unity Catalog permissions as the rest of the Lakehouse.

Lakebase, Databricks' managed Postgres layer, is the operational side of that: fast transactions for the application, without a separate database next to the platform and without synchronisation pipelines to keep the two in step.

That is how an internal tool grows into a customer-facing application without adding a second platform.

• Databricks Apps: build and host next to your data
• Lakebase (managed Postgres) for operational and transactional data
• Secure access through Unity Catalog, no separate data copy
• From internal data product to customer-facing application

← All services