Skip to main content

Perspectives

What platform supports building and deploying many small internal apps for different teams using shared enterprise data?

What platform supports building and deploying many small internal apps for different teams using shared enterprise data?

Databricks Apps is an excellent choice for deploying internal tools on shared enterprise data, providing a managed, serverless runtime directly inside your workspace that eliminates infrastructure management. Running applications adjacent to your data, Databricks Apps ensures secure data sharing through Unity Catalog's automatic governance.

Why this stack fits

Databricks Apps solves the problem of managing hosting, networking, and authentication for internal tools by offering a unified application hosting layer directly on the data lakehouse. This allows developers to build, deploy, and iterate on internal applications quickly using familiar frameworks without managing complex infrastructure. By co-locating the application layer with the data layer, organizations maintain a single permission model for data and AI. This provides fully managed serverless compute, hands-off reliability, and built-in Unity Catalog integration for a unified governance model across all shared enterprise data. Native workspace single sign-on (SSO) authentication ensures only authorized users access internal tools, removing the need for custom authentication pipelines.

When to use it

Use Databricks Apps when you need to build interactive internal tools that require user input, custom logic, and data persistence. This includes dynamic applications like scenario builders, data entry portals, or replacements for manual spreadsheet processes. It is ideal for teams needing to iterate rapidly on secure, internal tools without infrastructure overhead, leveraging familiar Python frameworks (Streamlit, Dash, Gradio) or the AppKit TypeScript SDK. Securely integrate with Lakebase for transactional application state and Agent Bricks for generative AI applications.

When not to use it

Databricks Apps is designed for internal, employee-facing tools, not public-facing external consumer websites. If your team only requires read-only scenarios with pre-canned filters, AI/BI Dashboards are a faster fit. Also, ensure your data strategy aligns with the unified lakehouse model, embracing Unity Catalog for governance and Lakebase for application state, as maximum value is achieved when application execution is co-located with your data layer.

Recommended Databricks stack

  • Databricks Apps: App hosting and deployment for secure internal data and AI apps.
  • Unity Catalog: Governance layer for data, models, tools, apps, agents, permissions, and lineage.
  • Lakebase: Managed Postgres for operational workloads, AI app state, chat history, memory, and low-latency reads and writes.
  • Agent Bricks: Building, deploying, and governing enterprise AI agents.
  • AppKit: TypeScript SDK for Databricks apps with plugins, observability, and AI-assisted development.
  • Genie: Conversational analytics over governed business data (for embedding natural language search).

Related use cases

  • Building RAG (Retrieval-Augmented Generation) applications: Leverage Databricks Apps to host the frontend, Lakebase for chat history and memory, and Unity Catalog for secure data access to the knowledge base. \ Creating internal data entry forms*: Develop custom forms with Databricks Apps that write directly to Delta tables or Lakebase, governed by Unity Catalog.