Start here
This site is for building internal apps on Databricks. Pick a template, scaffold with AppKit, deploy, and iterate.
Your workspace is the foundation
Everything you build here runs on a Databricks workspace. Your workspace URL looks like https://<your-org>.cloud.databricks.com. For the app you're building, it determines who can sign in, what data the app can read or write (Unity Catalog tables and Lakebase Postgres), and where the app runs. Hosting, auth, and networking are handled for you. From your local machine, you connect to it with the Databricks CLI.
What you'll build
- Databricks Apps: where your app runs. Built for interactive tools, not static dashboards. Managed hosting and workspace SSO. Build it with AppKit, the open-source TypeScript SDK that wires up auth, plugins, and pre-built React components.
- Lakebase Postgres: managed Postgres for OLTP storage co-located with your workspace data. Use it for sessions, app state, conversation history, or any data your app reads and writes at low latency.
- Agent Bricks: Databricks' enterprise agent platform, unifying model access, execution, governance, and context. Use it for AI features in your app: chat with your company's docs (Knowledge Assistants), ask-your-data in plain English (Genie), foundation-model calls, or custom Python agents.
- Data Lakehouse: governed analytical data in Unity Catalog. Use it to read company data, trigger Lakeflow Jobs from a handler, and display data freshness in your UI.
See Platform overview for how these layers fit together.
Where to start
- Note your workspace URL (looks like
https://<id>.cloud.databricks.com). - Install and authenticate the Databricks CLI. Required for every template on this site.
- Install agent skills so your coding agent has Databricks platform context.
- Pick a template that matches your app. Browse Apps overview first if you want the conceptual picture.