Hex
Connect Hex notebooks and published apps to the warehouse tables, models, and source systems they depend on across the full platform.
Semantic Layers & BIWhy Hex matters
Hex blurs the line between exploration and production. A quick notebook analysis can become a published app that stakeholders rely on for weekly decisions. SQL queries, Python transformations, parameterized inputs, and computed metrics all live inside Hex, invisible to the rest of the data platform. Because notebooks evolve organically, the dependencies they create on warehouse tables are rarely documented. When upstream data changes, nobody knows which Hex notebooks and apps break.
Typedef connects Hex to the full upstream lineage, so teams can see which notebooks and apps are affected by upstream changes, trace any number back to its source, and surface where Hex-computed metrics diverge from definitions in the semantic layer or other BI tools.
What Typedef unlocks
Impact analysis into notebooks and apps
Before changing an upstream table or model, see which Hex notebooks and published apps are affected, including exploratory work that has quietly become production reporting.
Notebook-to-source tracing
Follow any number in a Hex app back through the SQL, warehouse tables, transformation layer, and all the way to the source system.
Hidden logic and semantic drift
Surface the SQL, Python, and computed metrics inside Hex and flag where they diverge from definitions in the semantic layer or other BI tools.
Notebook cleanup and migration
Consolidate redundant notebooks, retire unused apps, or migrate tools with full visibility into what each notebook depends on and who consumes its output.
Related integrations
Make calculated fields, LOD expressions, and data blending logic visible to the rest of the platform for impact analysis.
Surface the business logic hidden inside LookML so impact analysis doesn't stop at the BI layer.
See the full inventory of saved questions and dashboards that depend on each warehouse table, including ones the data team does not know about.
See the full picture: what feeds every table and what depends on it across the stack.