Every number, traced to its source.
You can't trust a number you can't trace. Sluice records end-to-end lineage — every KPI follows a deterministic path back through each transformation to the raw source rows.
Lineage that's exact, not inferred
Because a deterministic compiler writes every query from an approved plan — not an AI guessing SQL — the path from raw data to KPI is known exactly. Lineage isn't reverse-engineered from logs; it's a property of how the model is built.
Source-to-KPI in one line
Why lineage is the foundation of trust
When a KPI is challenged — by a customer, an auditor, or your own team — lineage is the answer. Sluice lets you follow any number back to the exact rows it came from and confirm the total equals their sum. That's what makes the data defensible, and what separates it from an AI that just prints a plausible figure.
Frequently asked
- How is Sluice's lineage exact rather than estimated?
- A deterministic compiler writes every query from an approved plan, so the path from raw rows to each KPI is known precisely — not inferred from query logs after the fact.
- Can I trace a single KPI back to raw rows?
- Yes. Every KPI is a known aggregation of known source rows, and the total reconciles to their sum, so you can follow any number back to source.
- Does lineage cover PII-masked columns?
- Yes. Masking is part of the Silver transformation and is recorded in the lineage, so you can see where and how a column was masked.
Trace any number back to source.
See exact, end-to-end lineage on your own data — from raw rows to KPI.