Databricks Cost Optimization
Cut your Databricks bill: OhChimp flags idle clusters, warehouses with no auto-stop, and pricey all-purpose compute, then verifies the saving on your bill.
How does OhChimp connect to Databricks?
With your workspace host and a personal access token, sent as a read-only Bearer credential. OhChimp checks the token against the SCIM identity endpoint, then lists your clusters and SQL warehouses. When you provide a SQL warehouse id, it runs read-only SELECT queries against the system.billing tables. It never stores application data, secrets, or workload contents.
Does OhChimp need write access or see my data?
No. The token only needs read access to list compute and, for the spend breakdown, SELECT on the system.billing usage and list_prices tables. OhChimp reads compute configuration and billing metadata. It never stores your notebooks, table rows, secrets, or workload contents.
What Databricks costs can OhChimp actually reduce?
The main ones are interactive clusters left running with no auto-termination, SQL warehouses with auto-stop disabled, and scheduled jobs running on expensive all-purpose compute instead of cheaper job-compute SKUs. When you set a SQL warehouse id, OhChimp also breaks spend down by SKU so you can see what drives the bill.
Who applies the changes, and can they be rolled back?
You do. Each fix is a reviewable plan with a confidence score, a risk level, and rollback steps. Nothing changes until you click apply, and OhChimp applies the matching code and infrastructure changes together.
How are the savings verified, and what does it cost?
Against your real Databricks bill. A plan is marked VERIFIED only after 7 or more days, a drop of at least 10 percent, and 3 consecutive positive checks, otherwise it stays flagged "not implemented". Pricing is a flat monthly fee with no cut of your savings, plus a year-one ROI guarantee: a full refund of subscription fees if it does not pay for itself in your first 12 months on a paid plan.