Databricks Pricing Explained — DBUs, Tiers, and Clouds
How Databricks pricing works: what a DBU is, list rates by compute type, plan tiers, cloud and region differences, and the costs the calculator misses.
Databricks pricing is consumption-based: you pay per DBU (Databricks Unit), a measure of processing capability metered per second, and the rate per DBU changes with the compute type, plan tier, cloud, and region. For certain workloads (for instance, classic compute clusters) you also pay your cloud provider separately for the underlying VMs, storage, and networking. This guide explains the Databricks pricing model — how tiers and clouds change the number, and the costs the pricing calculator won’t show you.
While the model is simple on paper, in practice, it can often become confusing when trying to explain costs of specific workloads — for instance, the difference in cost for the same SQL query can change significantly depending on the type of warehouse used to execute it.
What a DBU Is and How You’re Billed
A DBU is a normalized unit of processing capability that Databricks meters per second of use. It is not a fixed amount of CPU or memory; it’s a billing unit whose consumption depends on multiple factors, such as cluster instance type. Your DBU cost for any workload is DBUs consumed times the per-DBU rate for that workload’s SKU.
The important part, as stated above, is that the full bill has two layers. Databricks meters DBUs. Your cloud provider (AWS, Azure, or GCP) separately bills the VMs, storage, and networking the workload ran on.
A migration that moves workloads from classic compute to serverless can look like “DBUs up, infrastructure down” while total spend barely moves — because serverless SKUs fold the infrastructure into a single, higher DBU rate. For the deeper mechanics of how DBUs meter, see the DBUs explained post.
DBU Rates by Compute Type
Different compute types bill at different per-DBU rates, and the spread is wide. Jobs compute is the cheapest classic SKU, while all-purpose (interactive) compute is the most expensive; SQL and serverless sit in between or above. The list rates below are for AWS, Premium tier, in US dollars per DBU as of June 2026 (Databricks pricing); they change over time and differ by cloud, region, and tier — so treat them as the shape of the model rather than a quote.
| Compute type | List $/DBU (AWS, Premium) |
|---|---|
| Jobs Compute (Lakeflow Jobs Classic) | $0.15 |
| Lakeflow Declarative Pipelines (Core) | $0.20 |
| SQL Classic | $0.22 |
| Serverless (jobs / pipelines) | $0.40 |
| All-Purpose Compute | $0.55 |
| SQL Pro | $0.55 |
| SQL Serverless | $0.70 |
All-purpose compute runs at roughly three to four times the rate of jobs compute, which is why scheduled work that quietly lands on an interactive cluster is such an easy source of cost to miss (all-purpose vs jobs compute). Note the product names: what many still call Databricks Workflows is now Lakeflow Jobs, and Delta Live Tables is now Lakeflow Declarative Pipelines. The classic billing SKUs still carry the older prefixes, which is why both names show up in cost data.
Serverless rates need a caveat when you compare them. SQL Serverless at $0.70 looks far above SQL Classic at $0.22, but the serverless number folds in the cloud VM cost that classic compute bills separately on top of its DBU rate. Comparing a serverless $/DBU against a classic $/DBU is not like-for-like. The honest comparison is total cost, DBUs plus the separate infrastructure line, and on bursty workloads serverless often comes out ahead despite the higher headline rate.
Pricing Tiers: Standard, Premium, Enterprise
Your plan tier multiplies every rate above. On AWS and GCP the tiers are Standard, Premium, and Enterprise; on Azure there are two, Standard and Premium, with Azure Premium playing the role Enterprise plays elsewhere. Higher tiers cost more per DBU and add governance, security, and compliance features.
One tier fact matters for cost tooling specifically: Unity Catalog requires the Premium plan or above, and it is enabled by default on workspaces created since late 2023 (Unity Catalog setup). That’s relevant because the system tables you use to track cost live in Unity Catalog. If you’re on a Standard workspace, the detailed usage data isn’t available until you move up. Azure is also retiring its Standard tier in late 2026, so most new environments start at Premium regardless.
Why Cost Differs by Cloud and Region
The same compute type costs different amounts on AWS, Azure, and GCP — and within a cloud it varies by region. DBU rates are set per cloud, and the underlying VM prices that sit beneath classic compute follow each cloud’s own regional pricing. Azure Databricks pricing is published by Microsoft and structured around its own VM families; AWS and GCP have their own rate cards.
“How much does Databricks cost?” has no single answer because the rate depends on compute type, tier, cloud, and region all at once.
This is why a number someone quotes from a blog post or a proposal rarely matches your bill. The model is consistent — the inputs are specific to your setup.
The Pricing Calculator and What It Misses
Databricks publishes an official pricing calculator that multiplies an estimated DBU consumption by the rate for a compute type and tier. It’s useful for a first estimate and for comparing SKUs. What it can’t do is predict how your environment behaves.
The calculator assumes a clean consumption number. Real environments add autoscaling that overshoots and holds extra nodes, clusters that idle between runs at the full rate, and jobs that fail and retry, re-paying startup each time. None of those show up in an estimate. The gap between the calculator and the invoice is almost always in the environment behavior.
Hidden Cost Drivers Teams Discover Late
Most pricing surprises come from a handful of drivers that the rate card doesn’t make obvious.
- Photon. Enabling Photon doesn’t raise the price per DBU; it consumes more DBUs per hour because Photon-enabled nodes carry a higher DBU multiplier. On compute-bound work it finishes faster and can lower total cost; on work it can’t accelerate, it just bills more per hour. Whether it pays off is a per-workload question.
- Autoscaling overshoot. Autoscaling adds nodes quickly and releases them slowly, so a brief spike can keep extra capacity billing long after the spike passes.
- Idle compute. An interactive cluster or a warehouse with a long auto-stop window bills at the full rate while doing nothing.
- Storage is separate. DBUs cover compute. Cloud storage and data transfer are billed by the cloud provider on top.
- Commitments, not reserved instances. Databricks discounts come from committed-use agreements (measured in DBCUs, Databricks Commit Units), not the “reserved instances” model you know from cloud VMs, which lower your effective rate below list.
Once a workload is running, the only source of truth is your own usage data. Databricks system tables record actual DBU consumption and the list rate for every line item, so you can reconcile what you were billed against what you estimated. The recurring lesson is that the surprises live in behavior, and behavior is what an estimate can’t capture; for the wider playbook on acting on that data, see Databricks cost optimization.
Databricks pricing is predictable once you separate the model from the behavior. The rate card is straightforward. The surprises come from the gap between the model and how your environment runs day to day — such as shared clusters, autoscaling, idle time, Photon. Closing this gap is a visibility problem more than a pricing one.
FAQ
1. What is a DBU in Databricks?
A DBU (Databricks Unit) is a normalized unit of processing capability, billed per second of use. The DBUs a workload consumes per hour depend on its instance type and node count, and the dollar rate per DBU depends on the compute type, tier, cloud, and region.
2. How much does Databricks cost per DBU?
It depends on the compute type and plan. For instance, a rough AWS Premium guide for June 2026: jobs compute around $0.15, SQL Classic around $0.22, all-purpose around $0.55, and SQL Serverless around $0.70 per DBU.
3. Why is all-purpose compute so much more expensive than jobs compute?
All-purpose (interactive) compute is the priciest classic SKU because it’s built for shared, interactive sessions. It runs roughly three to four times the jobs-compute rate, so scheduled work placed on it by accident is a frequent, easily-missed cost.
4. Does Photon increase the DBU rate?
No. Photon keeps the same price per DBU but consumes more DBUs per hour. It lowers total cost only when the speedup outweighs the extra consumption, which depends on the workload.
5. Why doesn’t the pricing calculator match my bill?
The calculator estimates rate times a clean DBU number. Your bill reflects real behavior (idle time, autoscaling overshoot, retries), plus separately billed cloud infrastructure and any committed-use discount. Those gaps are where estimates and invoices diverge.
LakeSentry shows your real effective rates and DBU usage across every connected workspace, reading only system-table cost metadata, never your business data, notebooks, or query results. Free tier, no card.
See your real Databricks rates and usage across every workspace
Free tier — unlimited workspaces, no credit card. Connect in minutes.
Related reading
Databricks cost optimization is matching compute and warehouses to actual workload demand. Five steps: see cost, right-size, tune, automate, monitor.
A DBU is the metering unit Databricks uses to bill compute, with rates that differ by compute type. How to tune DBU spend without risking workloads.
When Databricks spend moves, start here. Seven common drivers from DBU multipliers to retry storms, with diagnostic steps and safe first moves for each.
Evaluating Databricks cost tools? Compare them side by side →