Independent pricing guide. Not affiliated with Databricks, Inc. Rates verified April 2026.

Databricks DBU Pricing: Every Rate, Every Workload Type

A complete reference for understanding Databricks Units. What a DBU actually measures, how rates differ by compute type, instance-to-DBU mapping, and step-by-step examples showing how to calculate your monthly cost.

What Is a DBU?

A Databricks Unit (DBU) is a normalized measure of processing capability. It abstracts away hardware differences so Databricks can price compute consistently across instance types and cloud providers. Think of DBUs as compute currency: when you run a cluster, each node consumes a certain number of DBUs per hour based on its size. Your Databricks platform bill is the total DBUs consumed multiplied by the per-DBU rate for your workload type.

The key insight is that DBU charges are only the Databricks portion of your bill. You also pay your cloud provider (AWS, Azure, or GCP) for the underlying virtual machines, storage, and network transfer. The DBU charge is the fee for the Databricks platform layer: managed Spark, Delta Lake, Unity Catalog, notebooks, workflows, and SQL warehouses.

The Two-Layer Formula

Total Cost = (DBUs consumed x DBU rate) + Cloud infrastructure cost

Complete DBU Rate Reference

Compute TypeRate/DBUDescriptionIncludes Compute?
Jobs Light Compute$0.07Lightweight automated batch jobsNo
Jobs Compute$0.15Standard batch and scheduled pipelinesNo
Delta Live Tables Core$0.20Declarative ETL with core featuresNo
Delta Live Tables Pro$0.25ETL with CDC, expectations, advanced monitoringNo
All-Purpose Compute$0.40Interactive notebooks and developmentNo
SQL Classic$0.22Classic SQL warehouse endpointsNo
SQL Pro$0.55Advanced SQL with query profilingNo
SQL Serverless$0.70Fully managed SQL, instant startupYes
Model Training$0.65ML model training workloadsNo
Model Serving$0.07Real-time model inference endpointsYes

AWS Premium tier rates shown. Azure rates are 10-30% higher for compute-intensive types. Verify current rates at databricks.com.

How DBUs Are Consumed

Each cloud instance type has a defined DBU consumption rate. Larger instances consume more DBUs per hour. The rate depends on the instance family and size, not on what your code does. A node consuming 2 DBU/hr burns 2 DBU/hr whether it is processing data or sitting idle.

Instance Type (AWS)vCPUsMemoryDBU/hrUse Case
m5.xlarge416 GB0.75Light workloads, dev
m5.2xlarge832 GB1.50General ETL
i3.xlarge430.5 GB1.00Storage-optimized
i3.2xlarge861 GB2.00Default production
i3.4xlarge16122 GB4.00Large pipelines
i3.8xlarge32244 GB8.00Heavy processing
r5.xlarge432 GB1.00Memory-intensive
r5.2xlarge864 GB2.00Large datasets in memory
p3.2xlarge (GPU)861 GB5.50ML model training

Compute Type Deep Dives

Jobs Compute ($0.15/DBU)

Jobs Compute is the workhorse of most Databricks deployments. It runs non-interactive batch jobs: ETL pipelines, data transformations, scheduled notebooks, and orchestrated workflows. At $0.15/DBU, it is the second cheapest compute type (after Jobs Light at $0.07/DBU).

Jobs clusters start when a job begins and automatically terminate when the job finishes. There is no idle cost. This makes Jobs Compute the most cost-efficient option for production workloads that do not require interactive access.

Best for: Production ETL, scheduled data pipelines, batch ML inference, dbt jobs.

All-Purpose Compute ($0.40/DBU)

All-Purpose Compute powers interactive notebooks where data engineers and scientists explore data, develop pipelines, and run ad-hoc queries. The cluster stays running between cell executions, which is why the rate is 2.7x higher than Jobs Compute.

The major cost risk with All-Purpose Compute is idle time. A developer starts a cluster in the morning, runs a few notebooks, goes to lunch, and the cluster burns compute for 2 hours doing nothing. Always set auto-termination to 10 to 15 minutes.

Best for: Development, data exploration, ad-hoc analysis, notebook prototyping. Never use for production jobs.

SQL Warehouses ($0.22-$0.70/DBU)

SQL warehouses come in three flavors: Classic ($0.22/DBU), Pro ($0.55/DBU), and Serverless ($0.70/DBU). All provide JDBC/ODBC endpoints for BI tools and SQL clients. The difference is in features and management overhead.

Classic: Manual cluster management, cheapest per-DBU rate but requires infrastructure configuration. Pro: Adds query profiling, intelligent workload management, and Photon acceleration. Serverless: No infrastructure to manage, starts in under 10 seconds, and includes compute cost in the DBU rate.

Best for: BI dashboards, SQL analytics, reporting. Choose Pro for medium teams, Serverless for bursty usage.

Delta Live Tables ($0.20-$0.25/DBU)

DLT is a declarative ETL framework where you define the desired state of your data and Databricks manages the pipeline execution. Core ($0.20/DBU) handles standard ETL. Pro ($0.25/DBU) adds change data capture (CDC), data quality expectations, and advanced monitoring.

DLT pricing is on top of the underlying compute. A DLT pipeline running on a Jobs cluster pays both the DLT DBU rate and the Jobs Compute DBU rate for the same compute hours. This effectively doubles the per-DBU cost compared to running equivalent Spark code directly.

Best for: Teams that value pipeline reliability and automation over raw cost. DLT reduces engineering time at the expense of higher per-hour costs.

Model Training & Serving ($0.65 / $0.07)

Model Training at $0.65/DBU covers ML model training workloads, typically on GPU instances. The high DBU rate reflects the premium compute (V100, A100 GPUs) and MLflow integration for experiment tracking, model registry, and artifact management.

Model Serving at $0.07/DBU is the cheapest rate and is serverless-only. It runs inference endpoints that scale to zero when not receiving requests. You pay only for the compute seconds your model actually uses to process requests. This makes it cost-effective even at low inference volumes.

Best for: Training: deep learning, LLM fine-tuning, XGBoost at scale. Serving: REST API endpoints for model predictions in production applications.

Step-by-Step Cost Calculation

Scenario: Daily ETL Pipeline on AWS

Cluster configuration3x i3.2xlarge nodes
DBU/hr per node (i3.2xlarge)2.0 DBU/hr
Total DBU/hr (3 nodes)6.0 DBU/hr
Runtime per day8 hours
Workdays per month22
Total DBU/month6.0 x 8 x 22 = 1,056 DBU
Jobs Compute rate$0.15/DBU
Databricks cost1,056 x $0.15 = $158.40/mo
AWS cost (i3.2xlarge: $0.624/hr)3 x $0.624 x 8 x 22 = $329.47/mo
Total monthly cost$158.40 + $329.47 = $487.87/mo

Premium vs Enterprise Tier

Databricks offers Premium and Enterprise tiers. The per-DBU rate is the same for both tiers on most clouds. The difference is in features, not unit pricing. Enterprise adds advanced security (customer-managed keys, HIPAA, FedRAMP), enhanced governance, and dedicated support.

CapabilityPremiumEnterprise
DBU ratesStandard published ratesSame rates (discount via commit)
Unity CatalogYesYes
Customer-managed keysNoYes
HIPAA / FedRAMPNoYes
Enhanced audit loggingBasicVerbose
Committed-use discountsAvailableBetter rates at scale
Support SLAStandardPremium + TAM

Most organizations start on Premium and move to Enterprise when compliance requirements demand it. See the Enterprise pricing page for negotiation details.

Frequently Asked Questions

What does DBU stand for?
DBU stands for Databricks Unit. It is a normalized unit of processing capability that measures compute consumption on the Databricks platform. Think of it as compute currency: different workloads consume DBUs at different rates, and each DBU type costs a different amount.
How are DBUs calculated?
DBU consumption depends on two factors: the instance type running your cluster and the workload type. Each instance type has a defined DBU-per-hour rate. For example, an i3.2xlarge on AWS consumes 2.0 DBU/hour for Jobs Compute. Your total DBU consumption is: DBU/hour per node x number of nodes x hours running.
Why do different workloads have different DBU rates?
Databricks charges different rates for different features and SLA levels. Jobs Compute at $0.15/DBU is cheapest because it runs non-interactive batch workloads. All-Purpose Compute at $0.40/DBU is more expensive because it supports interactive notebooks with immediate results. SQL Serverless at $0.70/DBU is highest because it includes the cloud compute infrastructure cost.
Is DBU pricing the same across AWS, Azure, and GCP?
No. Azure DBU rates are typically 10% to 30% higher than AWS rates for compute-intensive workloads (Jobs, All-Purpose, DLT). SQL rates are comparable across clouds. GCP rates are between AWS and Azure. Always check the cloud-specific pricing page for exact rates.