Databricks Serverless Pricing per DBU and What Serverless Jobs and SQL Really Cost

Databricks serverless pricing is a single per-DBU rate that already includes the cloud compute. On AWS in US East, Premium tier, serverless Jobs and Lakeflow pipelines cost $0.35 per DBU, serverless SQL costs $0.70 per DBU and serverless notebooks cost $0.75 per DBU. Enterprise tier raises jobs and pipelines to $0.45 and notebooks to $0.95. There is no separate EC2 bill, but there is also no spot, no Reserved Instance and no Savings Plan discount on the compute underneath.

That last sentence is why the comparison with classic compute is harder than the price list suggests. Classic Jobs Compute looks cheap at $0.15 per DBU because the virtual machines are billed separately by AWS, Azure or Google. Serverless folds both halves into one number. Below are the current list rates from Databricks' own price data, what they come to at real monthly volumes, how to work out the break-even against your classic clusters, and what to put in place so the serverless line does not drift.

Databricks serverless pricing per DBU in 2026

These are list prices in US dollars per DBU, read from the data file that feeds the price tables on databricks.com, for US regions. Negotiated commit contracts lower them; nothing else does.

Two patterns stand out. Serverless SQL is the same $0.70 on every cloud and both tiers in the US, so the tier decision does not move your SQL bill. Jobs and notebooks cost 27 to 29 percent more on Enterprise than on Premium, and Azure Premium is priced like AWS Enterprise for those two products. Regions outside the US cost more: serverless SQL on AWS runs $0.88 in Singapore and $1.00 in Tokyo, which matters if a US company runs analytics close to an overseas team.

How Databricks serverless is priced compared with classic compute

Classic compute has two invoices. Databricks bills DBUs for the platform, and your cloud provider bills the virtual machines, disks and network for the same cluster. Serverless has one invoice, because the machines run in Databricks' account and their cost is inside the DBU rate. Here are the classic rates beside the serverless ones on AWS Premium.

To compare like with like, put a price on the classic VM half. Databricks publishes how many DBUs each instance type burns per hour, and AWS publishes the on-demand price of the instance. For three common Jobs Compute worker types in US East:

So a classic job on on-demand m5d instances really costs about $0.48 per DBU once the EC2 bill is counted, against $0.35 for serverless jobs. That does not mean serverless is 27 percent cheaper. A serverless DBU and a classic DBU are not the same amount of work, because Databricks picks and scales the serverless machines itself. The honest break-even is this: a job that burns 30 classic DBUs on m5d.2xlarge costs about $14.40 all-in, so serverless wins only if the same job finishes in fewer than about 41 serverless DBUs.

Is Databricks serverless more expensive?

For steady, well-tuned batch jobs on discounted instances, usually yes. For short, bursty or badly sized work, often no. Serverless removes the costs classic clusters waste: minutes spent booting a cluster, idle clusters waiting for an auto-terminate timer, and oversized nodes nobody revisits. It also removes the discounts classic clusters can earn. Spot workers can take a large share off the EC2 half of a classic bill, and EC2 Savings Plans and Reserved Instances apply to classic clusters because the instances run in your account. None of that applies to serverless.

The workloads that tend to come out cheaper on serverless are ad hoc notebooks, where classic All-Purpose costs $0.88 per DBU all-in on m5d.2xlarge against $0.75 serverless, small jobs that run for a few minutes many times a day, and BI dashboards that sit idle between queries. The workloads that tend to come out more expensive are long nightly ETL runs on spot fleets and anything already covered by a compute Savings Plan.

What Databricks serverless costs at real monthly volumes

At list price on AWS Premium, the serverless bill scales linearly with DBUs consumed. These are the monthly totals at three usage levels, before any commit discount.

A team running 20,000 serverless DBUs a month across jobs and SQL is spending $100,000 to $170,000 a year on that line alone. At that size a 10 percent improvement in how jobs are configured pays for most cost tools several times over, which is why the next two sections matter more than the rate card.

The serverless charges people miss

Performance mode. Serverless jobs run in performance optimized mode or standard mode. Databricks' documentation says both use the same SKU price, but standard mode "uses less compute to reduce costs" and suits work that can tolerate a startup latency of 4 to 6 minutes. A nightly batch job left in performance optimized mode pays for speed nobody is waiting for. Check this setting on every scheduled serverless job.

Networking. Serverless on AWS bills connectivity separately from DBUs: public connectivity per GB of data processed, private connectivity per GB, and data transfer for cross-region, inter-AZ and internet traffic. In-region storage access through S3 gateway endpoints is not charged by Databricks. A serverless job reading a bucket in another region pays twice, once to Databricks and once in transfer.

Reporting lag. Serverless usage lands in the system.billing.usage table, and Databricks warns there can be up to a 24-hour delay. Account budgets also alert rather than stop spend for most compute. A runaway serverless warehouse can therefore run for a day before anything on the Databricks side tells you.

Attribution. Classic clusters carry cluster tags into the cloud bill. Serverless has no cluster in your account to tag, so cost lands under Databricks with whatever tags your serverless usage policies (formerly called budget policies) apply. Without a policy per team, a serverless bill arrives as one undivided number.

How to keep a Databricks serverless bill under control

Start with the switches that cost nothing. Put batch jobs in standard performance mode. Keep serverless SQL warehouse auto-stop short. Create one serverless usage policy per team or cost center so every DBU carries an owner tag. Keep compute and storage in the same region.

Then decide whether you need a tool, and which kind. Some tools only report: they read billing data, split it by team and alert on spikes. Others change how Databricks runs, by tuning job configs or routing SQL queries. Our guide to Databricks cost optimization tools lists eleven options with every published price side by side, from native system tables to Definity at $0.003 per vCore-hour, Espresso AI at 40 percent of the savings it finds on Databricks SQL, and Acceldata at $100,000 a year per workspace.

For allocation, the hard part is knowing which pipeline feeds which table and which team owns it. If your data team already maps that with data lineage, the owner tags for serverless usage policies fall out of the same map instead of a guessing exercise. Snowflake teams face the same problem with credits, and our Snowflake chargeback model walks through rules that work for Databricks too.

CostAnalyst covers the reporting side without access to your workspace. You upload a Databricks usage export (date, service, cost) alongside your AWS, Azure or Google Cloud billing export, and it splits serverless and classic spend by team, flags anomalies by email and adds a weekly digest finance can read. That puts the Databricks line next to the EC2 or VM line that classic clusters still generate, which is the only way to see whether a move to serverless actually saved money. Plans start at $59 a month billed annually and are listed on the pricing page, or you can run one export through the analysis first.

Frequently asked questions

How is Databricks serverless priced?

Per DBU, at a rate that includes the cloud compute. On AWS Premium in US East, serverless jobs and pipelines are $0.35 per DBU, serverless SQL $0.70 and serverless notebooks $0.75. You get one Databricks charge and no separate virtual machine bill, but networking charges for cross-region and internet traffic are billed on top.

Is Databricks serverless cheaper than classic compute?

It depends on how efficiently your classic clusters run. Counting EC2, a classic job on on-demand m5d.2xlarge workers costs about $0.48 per DBU against $0.35 for serverless jobs, but the DBU counts differ. Serverless usually wins for short, bursty and interactive work and loses for long batch runs on spot instances or Savings Plans.

Does Databricks serverless include the cloud infrastructure cost?

Yes. Serverless compute runs in Databricks' cloud account, and the DBU rate covers those machines, so nothing appears on your AWS, Azure or Google compute bill for it. The trade-off is that your own cloud discounts, such as EC2 Savings Plans, Reserved Instances and spot pricing, cannot be applied to serverless workloads.

What is the difference between standard and performance optimized serverless jobs?

Both bill at the same SKU price. Standard mode uses less compute, so it consumes fewer DBUs for the same job, and it accepts a startup latency of 4 to 6 minutes. Performance optimized mode starts and runs faster for time-sensitive work. Most scheduled overnight jobs belong in standard mode.

How do I track Databricks serverless costs by team?

Attach a serverless usage policy with custom tags to each team, then group system.billing.usage by those tags, keeping in mind the table can lag by up to 24 hours. For finance reporting across Databricks, cloud and SaaS spend, export usage on a schedule into a cost tool that allocates it next to the rest of the bill.

Is Databricks Enterprise tier worth it for serverless?

Only for its security and compliance features, not for price. On AWS, Enterprise raises serverless jobs from $0.35 to $0.45 per DBU and notebooks from $0.75 to $0.95, while serverless SQL stays at $0.70. A team running mostly SQL warehouses pays almost nothing extra for Enterprise; a jobs-heavy team pays about 29 percent more on that line.