
Autonomous Compute Savings, SLA Safe
Auto Tune reads how your job clusters, SQL warehouses, and all-purpose clusters actually run, then moves each to a cheaper setup on its own. The waste creeps in through default cluster templates that nobody revisits, and at hundreds or thousands of jobs, nobody can revisit them by hand. Auto Tune revisits them continuously. Approve it once; it applies between runs, monitors continuously, and rolls back the moment anything slows down.
Every automated change runs the same loop. No exceptions, no surprises.
Approval-gated — you choose the jobs, warehouses, and clusters it may touch.
Policy-checked — changes clear your SLA rules before they apply.
Atomic — one snapshot, one change, applied only between runs.
Watched — continuous monitoring against the prior baseline.
Reversible — failure or degradation triggers automatic rollback.
Watch a real pass: analysis, gate checks, the applied change, the watch window that follows, and the audit trail every event lands in.
Get Serverless Efficiency at Classic Compute Pricing.
Serverless is often pitched as a better solution where compute requirements are unpredictable, but it trades over-provisioning for a premium rate under Databricks pricing. Altimate's Auto Tune for Databricks fixes the sizing directly, on the classic compute you already own, and shows you which workloads are genuinely ad hoc enough to run on serverless. Already running serverless SQL warehouses? Auto Tune tunes those too.
Spark Waste, Found and Fixed
Slow shuffles, oversized executors, steps that run one after another when they could run together. Altimate reads each run, prices it, and recommends the fix — so a job creeping up on cost is caught weeks before month-end, with a concrete change already in hand.
The Fastest-Growing Line on the Bill Is the Least Watched.
Model serving, vector search, AI gateway, and Genie — the fastest-growing spend on the platform. Altimate attributes every dollar by service, team, and day, and flags endpoints serving nobody.
3 idle model-serving endpoints. 30 days. Zero requests. $19,800/month in invisible waste.
We flagged it. They fixed it. $240K saved annually. Zero disruption.
Every Opportunity Sized, Owned, and Tracked to Done.
Spot-instance misconfigurations, wrong instance families, notebooks parked on all-purpose clusters, resources idling for days. A co-pilot does the heavy lifting, turning each into an opportunity with a dollar value, an effort score, and a name next to it.
From finding to fix: how an opportunity gets explained, assigned, and closed.
Know Which Team Spent What. See Next Quarter Early.
Spend split by team first, then by workspace, SKU, product, and user, and projected forward. Each SKU carries its own rate in the Databricks pricing model, so the split shows which rates drive the bill. Every dollar rolls up to an owning team, so budget conversations happen before the invoice arrives, not after.
Cost Optimization Is a Team Sport.
Autonomous savings and the opportunities your team closes land on one Summary page — measured in dollars and engineer-hours, each with an owner. Cost optimization stops being only the platform team's job.
Auto Tune agents apply the change themselves. Gated, monitored, reversible.
A co-pilot does the heavy lifting — sizing each opportunity in dollars, scoring the effort, and naming an owner. Your team gives the final go-ahead.
Questions, Answered.
Native tools give you visibility and storage upkeep. Cost dashboards and budgets show Databricks cost, and Predictive Optimization maintains tables. None of them change a cluster or warehouse config. Altimate acts on compute, the part that dominates the bill, and every action carries a snapshot and an automatic rollback.
A scoped service principal with read-only metadata access for analysis. Write permission exists only on the specific jobs, warehouses, and clusters you enable Auto Tune for, and it changes configuration only: never code, schedules, or data. Unity Catalog is required.
Per run, from your billing data, at your contracted rate rather than list price. Realized savings appear next to each tuned job, warehouse, and cluster, and roll up to the Summary page ledger, which tracks the cost of Databricks next to what Auto Tune saved.
Serverless removes cluster management, but Databricks serverless pricing carries a higher rate, so migrating over-provisioned workloads to serverless replaces one cost problem with another. The cheaper first step is to right-size the compute you already run: Auto Tune resizes job clusters, SQL warehouses, and all-purpose compute automatically, with typical reductions of 20 to 35%. Altimate then shows which workloads are spiky or ad hoc enough that serverless genuinely fits. And if you already use serverless SQL warehouses, Auto Tune optimizes those too.
Engineers rarely know what a job needs before it runs, so they pick a default small, medium, or large template and move on. Those defaults are sized for the worst case, they are almost never revisited, and at hundreds or thousands of jobs no team has time to revisit them manually. Auto Tune reads how each job actually runs and resizes it between runs, approval-gated and rolled back automatically if runtime degrades past 1.5x its baseline.
Auto Tune watches every touched job, warehouse, and cluster continuously. A failed run, or runtime beyond 1.5 times the recent baseline, triggers Backoff: the prior configuration is restored automatically and the event lands in the history.
A Databricks Unit (DBU) is the unit Databricks uses to meter compute. Your DBU cost is the number of DBUs a workload consumes multiplied by the per-DBU rate for its SKU, cloud, and pricing tier. A cluster that is larger than the job needs consumes more DBUs on every run, so right-sizing it lowers the DBU cost directly.
On classic compute, Azure Databricks bills in two parts: DBUs at the Azure Databricks rate for the workload type, plus the Azure virtual machines, storage, and networking underneath. Both parts grow with cluster size, so an over-provisioned cluster raises Azure Databricks cost twice.
Yes. Databricks publishes a pricing calculator, and the Azure pricing calculator covers Azure Databricks. Each one estimates cost from the configuration you plan to run. Altimate measures what each job, warehouse, and cluster actually cost per run, from your billing data, so you can compare the estimate with the real figure.
"Significant money savings on warehouses that were already optimized by us."
Aniket, VP of Data, ThredUp






