For the head of data and the CFOOn request
We review the state of your Databricks (a health check) and tell you which jobs leave tables half-written, which clusters cost money without delivering and which access nobody needs. We don't sell licenses.
You get the broken jobs with the tables they affect and the clusters you can adjust. Scope and timeline are in writing before we start.
Updated on
You don't need it if you have a single team with few jobs and someone already goes over costs and failures every month.
What comes out of Databricks feeds reports and AI models. If the input is broken, so is the output, and the compute cost is paid all the same. Each job (a scheduled process) worked the day it was launched. Over time, some fail without warning and others stay on with nobody needing them.
The control points of these five reviews are not counted yet, so we publish no figure: the scope is agreed in writing for each case.
Trademarks and logos belong to their respective owners. Their use here is descriptive only and implies no commercial relationship or sponsorship.
In 30 minutes we look at which teams use Databricks and what depends on it. Then you get the scope and timeline in writing.
We look at and measure jobs, clusters, costs and access. We change nothing in your workspace unless you ask.
You get which jobs fail and which tables they affect, and which clusters you can adjust. We go through it with your team.
Priority: Medium
Cluster left on with no jobs outside working hours
An example of the report format, not a client's.
Shall we talk about your case?
A 30-minute meeting to see what you have and what to review first.
All three are useful, each for one thing. AI brings the volume and people bring the judgment: that is why our review uses an automated AI tool and senior developers supervise it.
The review is done by a team of senior developers, with many hours of development and of finding the mistakes AI makes when it codes. We know more than 1,200 review points. The automated AI tool goes through them, and people verify, direct and review.
Team of senior developers
José María Salido, founder of Sondeon, answers for it
Databricks publishes its rates, and they change over time. The cost depends on the compute your clusters and jobs consume, so what we measure is which ones spend without delivering.
We need a read-only user and someone who knows your jobs and your clusters. We change nothing unless you ask: the health check looks and measures.
It depends on your usage, and we don't give figures in advance. We measure it in the first review with your own clusters and jobs: which ones cost more than they deliver and which can be tuned.
Whenever many new jobs and clusters appear. We recommend repeating it every quarter, because silent failures and costs grow when nobody is looking.
Yes, if you ask us to. The diagnosis comes first: each job and each cluster with its evidence and its priority. The fix is separate and only happens if you request it, and your team can also apply it with the list in hand.
It reviews jobs and pipelines that fail silently, the cost of clusters and jobs, access in Unity Catalog and inactive users. Ours is a periodic health check, different from the product's activity log, and every finding arrives with its evidence and its priority.
Automations that fail silently, users who have left and unused licenses you keep paying for in your Salesforce org.
Pipelines that feed reports with stale or broken data, and capacity that is paid for but not used.
Reports built on stale or broken data, refreshes that fail and licenses assigned to people who no longer use them.
Accounts without MFA, guests and apps with more permissions than they need, and Microsoft 365 licenses paid for and not used.
Fill in the form and we email you to set a day and a time. It is 30 minutes to see what you have and what to review first.