Hex, fed from one living model.
DataGlue feeds Hex from one living model of your other systems. Every number shows its formula and its records.
Hex: A collaborative data workspace for SQL, Python notebooks and data apps.
- OUT
- NO NATIVE CONNECTOR · YOUR WAREHOUSE OR DATABASE
Bring Hex and one decision to the call. Tool names are enough; no access needed.
Trusted by
- Your warehouse or databaseOUT
- File exportOUT
What goes out to Hex. Outcome tables and evidence streams go out for Hex to query.
- OUT
Your warehouse or database
DataGlue writes outcomes, sessions, events and identity links into your Postgres where the build sets that up. Hex reads those tables like any other source, and each outcome's formula is documented in plain English beside it.
- OUT
File export
Outcome tables can also be exported as CSV files on request and opened in Hex.
There is no native Hex connector today; the routes above are how it joins. Connections are agreed in the build. We check the source data, consent and identifiers before promising a linked journey. Hex is a trademark of its owner; this page implies no partnership or endorsement.
Describe the outcome. DataGlue works it out and shows you the formula.
- 01
Describe the outcome you want in plain words, such as "Deeper analysis".
- 02
DataGlue works it out from the definitions of your data sources and shows the formula in concise English beside every number.
- 03
The outcome lands where Hex reads it, and anywhere else you send it.
- EXAMPLE OUTCOME 01
Deeper analysis
THE FORMULANotebooks that start from joined, documented outcome tables instead of raw exports.
- EXAMPLE OUTCOME 02
Scenario models
THE FORMULASpend scenarios built on historical cost per signed deal by channel.
Want one of these from your Hex data? We map the route and the first outcome on the call.
Book a CallBring Hex and one decision. We'll map the route and the first outcome on the call.
The call scopes fit. The build is a separate engagement, priced before work begins.