dev.databricks.com is the home for developers building data and AI applications on Databricks. It is opinionated documentation and copy-paste-friendly templates so you—and your coding agents—can go from idea to deployed app in minutes not months.
Databricks brings operational data, AI agents, and apps together on one platform: Lakebase for Postgres that lives next to your lakehouse, Agent Bricks for governed, production-grade agents on your data, and Databricks Apps for secure, serverless frontends and APIs. DevHub is where we show you how those pieces fit into real workflows—not slides, but documentation and templates you can run.
The easiest way to get started building on Databricks is AppKit. AppKit is the open-source TypeScript SDK for building those apps: React UI, Express server, Databricks Asset Bundle integration, and plugins (Lakebase, Genie, analytics, and more). DevHub templates are built with AppKit.
- Browse Templates — Search and filter by service to find walkthrough prompts and full reference app codebases side by side.
- Copy — Use Copy as Markdown on a template page so your agent gets steps, commands, and context in one paste.
- Give it to your coding agent — Paste into Cursor, Claude Code, Codex, or your usual tool. Add a short brief: domain, data, UX, and what “done” looks like.
- Build end to end — Work with your agent on application code, Databricks Asset Bundles, Lakebase, and platform wiring until you have a production-ready agentic application: secure, deployable, and aligned with how Apps and Agents are meant to run on Databricks—not a one-off script.
You will need the Databricks CLI installed and authenticated to your workspace before you deploy. The Vercel CLI is also required for local development and deployments. For prerequisites, prompts, and companion docs (Agents, Apps, Lakebase), see Start here.
Whether you are typing databricks apps init yourself or pasting a bootstrap prompt into your agent, the goal is the same: ship faster on a platform that already unifies data, governance, and deployment.
See CONTRIBUTING.md for local development setup, content authoring guidelines, image requirements, and the pull request workflow.