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.
The data and AI lakehouse — technically impressive, double-billed for compute
TL;DR: Databricks carries a Risk Score of 49/100 (Caution) based on 3 documented complaints — a non-trivial pattern of issues worth reading before you sign up.
Databricks is a unified analytics and AI platform built on Apache Spark and Delta Lake, providing data engineering, ML, and SQL analytics. Pricing is consumption-based (Databricks Units / DBUs) on top of cloud provider compute costs — organizations pay both Databricks and their cloud provider simultaneously. Enterprise contracts start at $100K+/year.
Databricks is the dominant platform for large-scale data engineering and machine learning. The technical capabilities are industry-leading for PySpark workloads, ML model training, and unified lakehouse architectures.
The cost structure is genuinely complex: organizations pay Databricks per DBU AND their cloud provider for the underlying compute — effectively double-billing for infrastructure. Understanding and optimizing costs requires expertise in both Databricks pricing and cloud compute pricing simultaneously. It's the most technically complex billing model in data infrastructure.
Each complaint type is weighted differently in the Risk Score. Billing and marketing deception weigh heaviest.
Complaints are sourced from public platforms spanning US, UK, and global consumers. Each report links back to its original source.
| Platform | Reports | Who's reporting |
|---|---|---|
| 2 | US & global users | |
| G2 | 1 | Global B2B buyers |
Documented pricing complaints, billing issues, and support failures — newest 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.
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.
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.
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.
We've documented 2 billing complaints against Databricks — a signal worth weighing before committing to a paid plan. Its Risk Score of 49/100 puts it in the "Caution" band. See the full complaints breakdown → before deciding.
Cancellation difficulty is one of the top SaaS frustration patterns. Check the complaints page → — we tag cancel-related issues under "Billing" and "Contract Trap" categories. If none are documented yet, run a scan to surface what's currently out there.
Hidden-fee complaints fall under our "Billing Issue" category. We've documented 2 billing complaints for Databricks so far. See all complaints → for the full picture.
We track other cloud data & analytics infrastructure tools and rank them by Risk Score. See our alternatives comparison → to find lower-risk options in the same category.
The highest-severity documented complaints involve billing problems. Read all 3 documented complaints on the complaints page →
Probably not in the strict legal sense — most SaaS products with bad reputations are real companies delivering a real (if disappointing) product. But "is it a scam" is the question people ask when they feel they were misled. Read our full scam analysis →
We weight each warning by severity (Low to Critical) and category, then aggregate. Lawsuits and misleading-marketing claims weigh heaviest. The current 49/100 score puts Databricks in the "Caution" band. Full methodology →
Each warning is paraphrased from a public source — BBB filings, Trustpilot or G2 reviews, Reddit threads, Capterra ratings, court records, or news articles. The source URL is attached to every warning so you can verify it yourself. More on our methodology →
Sibling products in the same category, ranked by Risk Score (lowest first).
Open-source ELT alternative to Fivetran — increasingly popular, increasingly commercialized
SQL data transformation — essential data team tool with a pricing model in transition
Automated ELT pipelines — convenient, reliable, and aggressively priced per changed row
The cloud data warehouse that redefined the category — and the billing model