dbt, joined, in and out.
DataGlue marries dbt data with your other systems and sends outcomes back. Every number shows its formula and its records.
dbt: A transformation tool for writing, testing and documenting SQL models in a warehouse.
- IN + OUT
- NO NATIVE CONNECTOR · YOUR WAREHOUSE OR DATABASE
Bring dbt and one decision to the call. Tool names are enough; no access needed.
Trusted by
- Your warehouse or databaseIN + OUT
What moves between dbt and DataGlue. Clean models such as customers and orders come in. Outcome tables go out for your models to reference.
- IN + OUT
Your warehouse or database
dbt models live in your warehouse. DataGlue can read the clean models your team already trusts, and DataGlue's outcome tables can be referenced as sources in your own dbt project, where the build sets that up.
There is no native dbt 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. dbt 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 "Your definitions, kept".
- 02
DataGlue works it out from the definitions of your data sources, dbt included, and shows the formula in concise English.
- 03
Send it on: to reports, BI tools, any destination, or the AI tools your team already uses.
- EXAMPLE OUTCOME 01
Your definitions, kept
THE FORMULAYour dbt customer and order models used as the source of truth for outcomes.
- EXAMPLE OUTCOME 02
Outcomes in your lineage
THE FORMULAOutcome tables as dbt sources, so they show in your own documentation.
Want one of these from your dbt data? We map the route and the first outcome on the call.
Book a CallBring dbt 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.