Dawiso Data Products
Data Products Your Teams Can
Create, Take and Use Today
From data product definition to access, provisioning, and compliance evidence - in one platform. Your data, available to people and AI, governed from the first click.
The full data product lifecycle.
In one platform.
Define
Seven steps in the wizard, with every field explained as it asks for it.
Publish
The product goes to the Data Market with its owner and its contract attached.
Request
A consumer adds it to the Data Cart and says how long they need it for.
Approve
The owner approves, or the request clears automatically when nothing sensitive is involved.
Provision
Dawiso grants the access in your own data platform and masks what policy says to mask.
Expire
When the period ends, the access goes. No cleanup task for anyone.
Every step leaves an audit record: who asked, who approved, what was granted, when it ended.
One platform from definition to granted access
Data products your team builds itself
Everything you need to know, on the product page
See it in action
Watch the Data Product Platform run the full lifecycle - define, offer, shop, provision, and govern - end to end.
Everyone gets
what they actually need.
The same platform serves your data consumers, your data owners, and your compliance team - without context switching.
- Request access in seconds, not days
- AI agents query via MCP - no catalog UI needed
- Full visibility on access status and expiry
- Approve or reject requests with one click
- Set policies, SLAs, and expiry rules upfront
- Full ownership graph and downstream visibility
- Automated audit trail for every access event
- Access review campaigns with documented outcomes
- One-click incident response package
One access event.
Evidence for all
your regulations.
A single access request, one approval, one audit record that simultaneously satisfies NIS2, ISO 27001, SOC 2, GDPR, and DORA requirements. No duplicate workflows. No separate compliance tooling required.
If you use Dawiso,
you're halfway there.
Data Product Platform is not a separate product. It's built directly on the Dawiso engine you already have - the workflow system, automation rules, MCP Server, and REST API are all shipped and production-proven.
The new work is the experience layer: the marketplace, the access orchestration, the provisioning connectors, and the compliance evidence outputs.
See how Dawiso Data Product Platform works in your environment. We'll show you a live demo in 30 minutes.
Workflow Engine
States, transitions, multi-user approval chains
MCP Server
AI agents query and request access programmatically
AI-Assisted Features
Auto-definition, enrichment, BYO-LLM
Data Marketplace
Browse, filter, and find published data products - consumer-facing
Access Requests (Gate)
Request, approve, and track access to data products
Auto-Provisioning
Databricks, Snowflake, Fabric, BigQuery
Compliance Evidence Layer (Track)
Audit exports, review campaigns, SIEM/ITSM integrations
The Data Products Suite
Four products, one governed platform. Each solves a specific piece of the data product lifecycle.
Data Product Platform
End-to-end governance from definition to access.
Data Marketplace
Browse, request, and access trusted data products.
Access & Provisioning
Auto-provision into Databricks, Snowflake, Fabric, and more.
Compliance Evidence
Audit trails for NIS2, ISO 27001, SOC 2, GDPR, DORA.
Frequently Asked Questions
Still need help? Contact us, and we'll get back to you quickly.
What makes something a data product rather than just a dataset?
A dataset is the data. A data product is the data plus the things that make it safe for someone else to reuse: a description, the items it is built from, a maturity level, a classification such as internal use only, and a named person behind it. Dawiso keeps those together and gives the product a lifecycle state, so a consumer can tell a published product from something still taking shape.
How is the data product catalog organized?
Around three object types: domains, data products and contracts. Domains group products by the part of the business that owns them, products are the units people consume, and contracts sit between a producer and a consumer. That shape is what stops a catalog becoming a flat list nobody can navigate.
What does a data contract actually document?
How data flows between two data products and under what terms it may be used, with a clear producer and consumer on either side. So a contract is the written answer to "who is allowed to depend on this, and what did we promise them", which is the thing that usually lives in somebody's memory until they leave.
How do people find a data product worth using?
Through the Data Market, which is a browsable market of the published products rather than a search box over raw tables. You can filter by platform, by size and by data product maturity, and it surfaces recommendations, so the usual "is there already something like this" question gets answered in the tool instead of on Slack.
How do we see what a data product is built from?
Data product lineage maps the relations between products: which ones are built from others, and which ones depend on them. Read downstream to see who breaks if you change something, and upstream to see what a number you distrust is actually made of. See interactive data lineage for the wider picture across the estate.
Which systems does Dawiso connect to, and what does it read from them?
Dawiso connects to warehouses, lakes, BI and pipeline tools to read metadata - structures, definitions and relationships - not the business data itself. Databricks, Snowflake, Power BI and Keboola are documented examples, and on-premises sources are reached through the Dawiso Integration Runtime. Worth being precise here, because reading metadata out of a platform is a different thing from granting someone access inside it. The full list is on the connectors page.
Do we buy this separately if we already use Dawiso?
It is not a separate product. It runs on the Dawiso engine you already have, which is where the workflow system, the automation rules and the API live. What the platform adds is the experience layer over that engine. See pricing for how plans are structured, and ask us what is switched on for your tenant before you plan around any single capability.