DecisionBox for Databricks

Hey PH, Selçuk here from DecisionBox, If you're on Databricks, your lakehouse already has the data. Unity Catalog tells you what's in it. A SQL warehouse will run anything you ask. The hard part is figuring out which questions are worth asking, and getting validated answers without dedicating a team on it for weeks. That's what we built DecisionBox for. Connect it to your workspace, point it at a domain pack, and the agent writes its own SQL, validates every finding against the data, and ships a ranked backlog of insights and recommendations. No prompting, no question-writing. Today we're adding Databricks to the list of supported warehouses, with the same posture your security team already lives with for dashboards and dbt jobs. Read-only, scoped by Unity Catalog. The agent connects with a principal you choose, typically USE CATALOG and USE SCHEMA on what you want exposed, SELECT on the tables you opt in to, and CAN USE on the SQL warehouse. Unity Catalog is the boundary. The agent cannot reach anything it hasn't been granted. Runs on the SQL warehouse you pick. Serverless, Pro, or Classic, whichever size, whatever Auto Stop you've set. Every cost guardrail you've already configured for your dashboards and other workflows applies to the agent the same way. The whole Databricks provider is in the public repo, AGPL v3 — the Unity Catalog reads, the OAuth flow, the SQL the agent writes. Same agent runs against BigQuery, Redshift, Snowflake, Postgres, and MSSQL too. If your stack moves, your DecisionBox install moves with it. Happy to dig into the service principal setup, best practices, or anything else in the comments.

<p>Congrats on the launch! The part where it validates the SQL against real data before surfacing the insight is something I keep having to rebuild. Good luck with the Databricks rollout.</p>

<p>Congrats on the launch 🔥</p>

<p>Are you seeing teams self host this inside their Databricks VPC, or is it mainly used as a local dev tool?</p>