Double billing: DBU costs plus cloud compute costs simultaneously
Databricks charges per DBU on top of cloud provider compute costs for the same cluster. Teams unfamiliar with this model describe first invoices significantly exceeding expectations.
Cloud Data & Analytics Infrastructure · Risk Score 49 · Caution
Databricks Complaints: What Buyers Are Actually Reporting
The data and AI lakehouse — technically impressive, double-billed for compute
3 documented complaints against Databricks — paraphrased from BBB filings, Trustpilot reviews, Reddit threads, and public forum posts. Newest complaints first.
Our AI scanner searches Reddit, Trustpilot, BBB, and news sources for fresh complaints from the past year, paraphrases what it finds, and adds anything new to this page. Takes up to 90 seconds.
0
Critical
2
High
1
Medium
0
Low
Who reported these complaints
Sourced from public platforms across US, UK, and global markets — each report links to the original source.
| Platform | Reports | Who's reporting |
|---|---|---|
| 2 | US & global users | |
| G2 | 1 | Global B2B buyers |
Steep learning curve for organizations not already using Apache Spark
Organizations without prior Spark experience describe a 3–6 month onboarding ramp. PySpark's programming model, Delta Lake concepts, and Databricks-specific features like Auto Loader require significant upskilling.
Interactive cluster idle time accumulates costs quickly during development
Development clusters that remain running between data science sessions accumulate both DBU and cloud compute costs even when idle. Without automatic termination policies, monthly development costs can be surprisingly high.