Launching today
Relium
Catch risky dbt changes before they break business metrics
6 followers
Catch risky dbt changes before they break business metrics
6 followers
Relium is a pre-merge reliability layer for SQL and dbt. It reviews every PR, understands semantic changes, traces downstream model and KPI impact, checks warehouse evidence, and returns ALLOW / WARN / BLOCK before production. Unlike observability tools that alert after data breaks, Relium helps teams catch silent logic failures before they ship.
@abhishekh2 Not dbt on my side, just plain SQL over a job index, but the failure you describe is the one that got me. I tightened the query that decides whether a posting belongs to our industry at all, every check passed, and the next weekly report had one country losing a big share of its openings. Part of that drop was correct, junk we never should have counted, and part was the new condition quietly excluding companies with no country set. What would earn my trust is less the ALLOW/WARN/BLOCK label and more a handful of concrete rows that moved in each direction, so I can tell in a minute which side is the bug. A bare verdict I would probably learn to click through within a week. When a change touches millions of rows, how do you pick which ones to show, the biggest contributors to the metric or the rows the diff logic hits directly?