Studio
Studio is the admin surface over Roots. It is how definitions get agreed, access gets granted, and the questions that did not work get turned into the ones that do. Smaller customers are happy to let our team run this for them; larger ones want it in-house, and Studio is how they take it.
Define and certify what things mean
Metric definitions, business terminology, entity relationships and approved calculation patterns all live here, with the ability to mark a definition as certified so everyone downstream knows it has been agreed rather than assumed.
The value is not the editor. It is that the argument about what revenue means happens once, in one place, with a record of who settled it.
Control access and scope
Add data sources, set user and row-level permissions, define which domains a team can reach, and configure the model and security policies that apply to them. Changes take effect on the next question rather than the next release.
Review what did not work
Every question that returned an unknown, every ambiguous term, every query that ran slowly — Studio surfaces them as a working list rather than leaving them buried in logs. Each one is a concrete instruction about what to define, connect or instrument next.
Most organizations guess at that roadmap. This one is derived from what people actually tried to ask.
Studio gives your data experts control over what DeepGarden knows, how it reasons and what it is allowed to access.