Solution
Know what data you have, who owns it and where it goes.
Governance that follows data through the pipelines, dashboards and models that use it.
The problem
What teams are dealing with.
- The catalogue describes the warehouse but not the spreadsheets, extracts and pipelines people really use.
- Nobody can say with confidence which reports contain sensitive fields.
- Policies exist as documents; enforcement depends on memory.
Why it stays unsolved
Existing approaches fragment the workflow.
- Governance tools observe the data stack from outside and learn about changes after they happen.
- Each tool enforces its own permissions, so one policy becomes many settings.
The DooHorizon solution
DooHorizon is designed so governance is a property of the platform, not a product beside it.
GovernanceDoo
Status: Coming SoonIs designed to hold the inventory, ownership, classification and policy.
About GovernanceDooFlowDoo
Status: AvailableSupplies lineage from the pipelines that actually move the data.
About FlowDooVizzDoo
Status: Public BetaApplies roles and sharing rules at the point of consumption.
About VizzDoo
Reference architecture
How the pieces are arranged.
- SourcesPipelinesDatasetsDashboards
- Catalog and lineage
- Policy
- Access
- Audit
Example business workflow
The same six steps for every asset.
- Register asset
- Assign owner
- Classify
- Apply policy
- Monitor
- Report
Business outcomes
What this lets you do.
- Answer “where did this number come from?” from lineage rather than interviews.
- Let access follow classification.
- Give every dataset a named owner.
- Produce evidence for a review from one place.
Governance and security
How it stays under control.
- Available today in the products: project roles, encrypted credentials, revocable share links and dataset lineage.
- GovernanceDoo, the shared control plane, is in development.
- No certification is claimed; see the Trust Center for the compliance roadmap.
Start with this use case.
Start with one use case. Expand across the ecosystem.