/

/

Databricks cost per job, DBUs plus the VMs under them

Databricks cost per job, DBUs plus the VMs under them

Data platform

Databricks cost per job, DBUs plus the VMs under them

Daily Parquet export of Databricks system tables to storage you own, read-only

DBU spend by workspace, job and cluster

Level 1 brings Databricks DBU billing into Costory by workspace, product, job, cluster, SQL warehouse and your custom tags, next to the rest of your infra cost. Serverless is covered at this level: the DBU price already includes the compute.

On a direct contract, Costory prices DBUs from your list prices minus an optional discount, and keeps list cost visible. If you pay through AWS, Azure or GCP Marketplace, Costory uses your real price from the cloud bill and does not count DBUs twice.

The full cost of a job

Level 2 joins DBUs to the cloud VM lines that ran each workload. Costory matches instance ids from the Databricks compute system tables to the cluster, job and job run that held them, so you see DBUs plus EC2, Azure VM or Compute Engine cost on one job. Pools included: idle pool time shows up as pool idle instead of disappearing into anonymous VM spend.

Matching uses instance ids, not cloud cost allocation tags, so it also works on past dates, as far back as Databricks keeps its compute system tables.

No Databricks keys

A daily export job you run writes Parquet to an S3 bucket, ADLS Gen2 container or GCS bucket you own, in the same cloud as your workspace. Costory reads that prefix with a read-only grant. It never gets access to your Databricks account or holds Databricks API keys.

Setup in short

Plan 30 to 60 minutes with a Unity Catalog admin. Enable the billing and access system schemas (plus compute for Level 2), import the export notebook and schedule it daily, grant Costory read access, then send Costory support the billing root path and how you pay for Databricks. Costory support completes the connection. The first run can load up to 12 months of history. Both levels work on AWS, GCP and Azure. Level 2 needs your AWS, GCP or Azure billing already in Costory.

Questions you can ask

  • “What did each Databricks job cost last month, DBUs plus VMs?”

  • “Which instance pools had the most idle cost this month?”

  • “Show Databricks DBU spend by workspace and team tag, next to AWS.”

Out of scope

Classic and Pro SQL warehouse VMs (Databricks does not expose them; DBUs are still broken down per warehouse), networking and storage such as S3, ADLS and GCS, and Level 2 in regions without a compute export job.

Full setup guide: Databricks in the Costory docs.

Set up in 30 to 60 minutes, then Costory support completes the connection.

30-day free trial. Plans from €250/month, billed annually. We recommend Team (€600/month) once more than one team uses Costory.

First optimization recommendation

The next day

PRICE

From 250€/month, never a % of your bill

Setup

30 to 60 minutes

Data residency

EU

Access

Read-only on your cloud

From 250€/month, never a % of your bill. 30 days free, no credit card.