Dawiso Data Catalog: Review, Pricing & Features

    Everything you need to evaluate Dawiso for data catalog: what it is, my review, pricing, features, integrations and the best alternatives.

    By Ari Bajo - data engineer turned writer.

    Updated on November 19, 2026

    Product
    Dawiso
    Category
    Enterprise data governance
    Pricing
    From €445/month (5 seats)
    Deployment
    SaaS, self-hosted, hybrid, data residency
    On this page

    What is Dawiso?

    Dawiso is a data catalog and business context layer from Prague: it scans metadata from 40+ connectors, links it to a glossary, owners and lineage, and serves that context to people and AI agents over MCP.

    Dawiso review

    Dawiso is the best data catalog tool for European enterprises in regulated industries (banking, insurance, energy, public sector) that want a configurable catalog with EU hosting or self-hosting and published per-seat prices.

    — Ari Bajo, Founder of toolsfordata.com

    Strengths

    • A published entry price (€445 a month for 5 seats) with unlimited connectors, rare among enterprise governance tools.
    • Data products follow open standards (ODPS, ODCS) and export back out.
    • EU company with EU hosting by default, and a self-hosted option.

    Caveats

    • Access provisioning and masking are part of the Data Product Platform, in public preview since October 2026.
    • No built-in data quality engine: checks run in tools such as Soda or dbt.
    • No webhooks or Python SDK documented.

    Fun facts

    Dawiso was founded in Prague in 2019, after Société Générale's Prague team needed a metadata platform.

    Dawiso joined the Databricks MCP Marketplace in May 2026.

    Dawiso shipped its Data Product Platform, with access provisioning, in public preview in October 2026.

    Dawiso pricing

    Dawiso Standard starts at €445 a month for 5 seats, with unlimited connectors. Corporate and Enterprise prices aren't published.

    Checked November 12, 2026 on the pricing page.

    Dawiso features

    Dawiso appears in my lists of the best data catalog and data lineage tools. It supports 44 of the 70 tracked data governance features.

    Dawiso data catalog

    Dawiso lets each company shape its own metamodel from low-code packages, with 40+ scanners, AI search, and descriptions written back to Databricks and Tableau.

    Compare: data catalog tools

    • Automated Metadata Harvesting: Scanners for 40+ sources (Snowflake, Databricks, BigQuery, SQL Server, Oracle, Power BI, Tableau, dbt, Airflow and more) extract metadata on a schedule, from the Dawiso cloud or from the on-premises Integration Runtime (docs).

    • Search & Discovery: Full-text search with faceted filters, relational operators and recommended objects; results show application, object type, path and workflow state (docs).

    • AI-Powered Search: AI Search takes a plain-language request, searches across objects, attributes and relations, and returns matching results with context (docs).

    • Custom Fields & Templates: Low-code JSON packages define custom object types, attribute types, relation types and page templates, so teams add their own fields to any asset type (docs).

    • Asset Certification: Workflows move objects through Draft, Review, Approved and Expired states set by stewards, and data products carry a Certified flag shown as a chip in the Data Market (docs).

    • Business Glossary: Business Glossary app holds business domains, terms, indicators and rules with synonyms and acronyms, steward approval workflows, and automatic mention links wherever a term appears in other objects (docs).

    • Metadata Propagation: PII Level and Confidentiality set on columns and tables roll up to the output ports and data products built on them, with the most sensitive value winning (docs).

    • Usage & Popularity Statistics: The Adoption dashboard lists the most visited catalog objects and a SQL view exposes object visits, but no per-asset query frequency from the source platforms is documented (docs).

    Dawiso data lineage

    Dawiso shows system, table and column lineage from scanners, dbt, SQL parsing (an enterprise add-on) or manual mapping, down to individual Power BI visuals.

    Compare: data lineage tools

    • Table-Level Lineage: Table-level flows connect tables, views, reports and other objects and are the default lineage view (docs).

    • Column-Level Lineage: Column-level flows trace data between columns and report attributes, ingested from platforms such as BigQuery and Databricks or derived by SQL parsing (docs).

    • End-to-End Lineage: Lineage links source databases, ETL tools such as Azure Data Factory and Airflow, dbt, and BI tools down to individual Power BI visuals (website).

    • Impact Analysis: Column-level lineage is used for impact studies, and the MCP tools and data product Consumed by view list the downstream dependencies of an object (docs).

    • Automated Lineage Extraction: Lineage is extracted automatically by platform scanners, from dbt and pipeline tools, and by parsing SQL scripts for BigQuery, Oracle, PostgreSQL, Snowflake, SQL Server and Teradata, though SQL parsing is off by default and offered to enterprise clients after evaluation (docs).

    • OpenLineage Support: The lineage sources are platform scanners, dbt, SQL parsing and manual input; no OpenLineage ingestion is documented, and Airflow lineage is read from its REST API (docs).

    Dawiso data stewardship

    • Critical Data Elements: Schema properties in a data contract carry a critical data element flag alongside required, unique and classification fields (docs).

    • Review & Approval Workflows: Default, basic and checklist workflows route objects from Draft to Review to Approved, with multi-user approval and custom transitions per role (docs).

    • Metadata Automation: Admin-defined automation rules run on events or schedules and set attributes, change workflow states, send notifications or sync objects (docs).

    • Governance Campaigns: Bulk edit and MCP bulk operations exist, but no campaign feature for running a governance push across a set of assets is documented (docs).

    • Governance Scorecards: Fullness scores measure documentation completeness per object; no questionnaire-based maturity scorecard is documented (docs).

    Dawiso data classification

    • Sensitive Data Discovery: AI agents scan the catalog and raise PII classification findings for attributes they judge to be personal data, which stewards approve or decline (docs).

    • Data Policy: Dawiso documents that PII and confidentiality labels are descriptive and do not block access; access enforcement comes from Access Gate, part of the Data Product Platform still in public preview (October 2026) (docs).

    • Native Policy Enforcement: Access Gate provisions approved, time-limited grants in the platform where the data lives, but the Data Product Platform it belongs to is in public preview (October 2026) (website).

    • Data Masking: Access Gate masks sensitive columns on sources that support column masking when it provisions access, but it is in public preview (October 2026) (website).

    Dawiso AI features

    Ask Dawiso answers questions in the app and in Slack, AI drafts descriptions, and agents propose fixes for steward approval. A 29-tool MCP server is listed in the Databricks MCP Marketplace.

    • AI Chat Assistant: Ask Dawiso AI answers questions about the catalog in a chat panel that knows the current page, cites objects and respects the user's permissions; it is in early adoption with billing not yet started (docs).

    • AI Documentation Generation: Descriptions are drafted by an LLM during metadata ingestion with configurable prompts per attribute type, and carry a banner until a user reviews them (docs).

    • Agentic Metadata Enrichment: Agent Studio agents scan the catalog and propose missing descriptions, owners, PII classifications, relations and new terms as findings that stewards approve in bulk or one by one (docs).

    Dawiso data compliance

    • Audit Trail: The activities changelog records every change to an object with previous and new values, and the Change_Log SQL view exposes those events for reporting (docs).

    • Compliance Reporting: Dashboards and the SQL API can report on governance metadata, but no regulator-facing evidence pack or compliance report is documented (docs).

    • Regulatory Framework Mapping: Dawiso markets AI Act risk assessments and BCBS 239 lineage use, but no general feature mapping assets and controls to regulations is documented (website).

    • ROPA: Blog content covers GDPR Article 30 through lineage and PII tracking, but no processing activities register is documented (website).

    • Data Activity Monitoring: Dawiso catalogs metadata and does not monitor queries against the source systems (docs).

    • Data Retention Policies: No retention rules for archiving or deleting data assets are documented; retention appears only for Dawiso's own AI chat data (docs).

    • Data Subject Rights: No DSAR or deletion request handling is documented (docs).

    Dawiso collaboration

    • Discussions & Annotations: Users post comments tagged Comment, Issue or Question on any object and reply in threads in the Activities section (docs).

    • Ticketing Integrations: Data Market checkout can raise access requests in Jira Service Management or ServiceNow, and Jira issues can be embedded and looked up on object pages (docs).

    • Alert Notifications: Notifications arrive in-app and by email; the Slack bot only answers questions, and Microsoft Teams support is planned (docs).

    Dawiso data marketplace

    Data products follow open standards (ODPS, ODCS), with a Data Market where checkout goes to Access Gate, Jira Service Management or ServiceNow.

    • Self-Service Access Requests: Consumers add data products to a cart and check out with a reason, duration and use case, routed to Access Gate, Jira Service Management or ServiceNow (docs).

    • Data Products: Data Product Catalog and Data Product Standard apps describe products with owners, ports, ODCS data contracts, SLAs and versioning, published to the Data Market (docs).

    • Data Mesh Support: Data products belong to business domains with their own owners, use Data Mesh input and output ports, and are discovered across spaces in the Data Market (docs).

    • Subscription Management: My Access tracks each consumer's requests and grants, but producers announce breaking changes manually; no automatic notices to consumers are documented (docs).

    Dawiso data quality

    • Data Profiling: Light: scanners pull column statistics such as distinct values, null counts and low/high values where the source exposes them (e.g. Oracle), shown as a histogram with mean and median (docs).

    • Data Contracts: Data contracts follow the Open Data Contract Standard with schema, quality, terms and access details, are versioned, approved by stewards, and exportable to ODCS (docs).

    • SQL Table Tests: Quality checks are documented in data contracts and name an external engine such as Soda, Great Expectations, Monte Carlo or dbt; Dawiso does not run them (docs).

    • Data Health Scores: No composite quality score is documented; the fullness score measures documentation completeness, not data quality (docs).

    • Anomaly Detection: No anomaly detection on data values or volumes is documented (docs).

    Dawiso AI governance

    • AI Asset Inventory: AI use cases and models are documented in a central list with their purpose, the data they rely on and their validation status (website).

    • AI Lineage: Data provenance links AI systems to the data that feeds them, including its sensitivity, through the same lineage graph (website).

    • AI Regulatory Compliance: Predefined assessments evaluate each AI use case against the EU AI Act on data sensitivity, transparency and human oversight to set a risk level (website).

    • AI Model Health Score: AI systems carry a validation status, but no composite model trust score is documented (website).

    • AI Agent Access Governance: MCP tools and the AI chat only return metadata the connecting user may see, with role-scoped tools, but no policy check on agent retrieval of the underlying data is documented (docs).

    Dawiso workflows

    • REST / GraphQL API: A versioned REST API with Swagger docs supports CRUD on objects, attributes, relations and workflows; a separate SQL API serves reporting (docs).

    • dbt Integration: The dbt connector ingests projects, jobs, models, sources, exposures, tests and statistics, and dbt is a lineage source (docs).

    • Python SDK: Programmatic access is through the REST, SQL and MCP interfaces; no pip-installable Python SDK is documented (docs).

    • Webhooks: Automation actions send in-app and email notifications or call an Azure Data Factory pipeline; no generic outbound webhooks are documented (docs).

    Dawiso data context layer

    • MCP Server: The MCP server exposes 29 role-scoped read and write tools for search, lineage, object updates, comments and permissions, with an admin allowlist; it is included from the Corporate plan (docs).

    • Knowledge Graph: Knowledge graphs show business terms, documents, dashboards, systems and people as nodes with ownership, reference and synonym edges, expandable up to ten levels (docs).

    • Semantic Models: Data products export as Open Semantic Interchange YAML with tables, columns and foreign-key relationships, which can be turned into Snowflake semantic views (docs).

    • Unstructured Data Catalog: A live SharePoint connection scans and ingests documents, and Word files can be imported from shared drives, as catalog objects with owners, tags, lifecycle states and contributor or viewer roles (website).

    • Verified Queries: Ask Dawiso AI answers from a catalog index and live catalog lookups; it does not generate SQL and no store of approved question-to-SQL pairs is documented (docs).

    • Semantic Layer Interop: The OSI export carries tables, columns and relationships but no metric definitions, and no import of dbt, Snowflake, Databricks or BI semantic models is documented (docs).

    Not covered: Master data management

    Dawiso integrations

    Dawiso connects to Snowflake, Databricks, BigQuery, Redshift, dbt and Airflow, and to Jira, ServiceNow, Slack and Microsoft Teams for governance workflows. Dawiso lists 42 integrations in total.

    Dawiso deployment options

    Dawiso runs as SaaS on Azure (EU regions by default), self-hosted on Kubernetes on the Enterprise plan, or hybrid with a scanner behind your firewall.

    • SaaS Deployment: Dawiso cloud is a fully managed SaaS hosted on Microsoft Azure, with updates handled by Dawiso (docs).

    • Self-Hosted Deployment: Self-hosted Dawiso runs in the customer's Kubernetes cluster from Dawiso's Helm chart and images; on-premises is an Enterprise plan option (docs).

    • Hybrid Deployment: The Dawiso Integration Runtime scans sources behind the firewall, lets teams review the extracted files, and sends them to the Dawiso cloud over HTTPS (docs).

    • Data Residency: The cloud service runs in EU Azure regions by default, and can run in another location agreed in the customer's contract, with backups kept in the same place (docs).

    Dawiso security

    Dawiso supports SSO through Entra ID or OpenID Connect, roles with space and object permissions and an audit log, with ISO 27001, ISO 27018 and SOC 2 Type 2.

    • SSO: Supports Microsoft Entra SSO and any OpenID Connect identity provider, plus LDAP and Kerberos (docs).

    • RBAC: Viewer, Contributor, Space admin and Admin roles combine with read and write permissions per space and object, documented in a full permissions matrix (docs).

    • Audit Log: The application audit log of system and user activity is append-only; no user or tenant admin can change or delete entries (docs).

    • Compliance Certifications: Holds ISO/IEC 27001:2022 and ISO/IEC 27018:2019 certification and a SOC 2 Type 2 report (docs).

    • SCIM Provisioning: Users and groups sync on a schedule from Microsoft Entra ID or LDAP; SCIM is not documented (docs).

    Dawiso alternatives

    The closest Dawiso alternatives and most popular competitors are Collibra, Alation, Atlan, OvalEdge, DataGalaxy and OpenMetadata. They share Dawiso's main use cases and features, from the closest match down. The Dawiso alternatives page compares their pricing, deployment and features, and says when to choose each one instead.

    Choose Dawiso for a configurable catalog with EU hosting and a published price. For a larger governance program with policy enforcement, consider Collibra or Atlan.

    1. 1. CollibraDawiso vs Collibra
    2. 2. AlationDawiso vs Alation
    3. 3. AtlanDawiso vs Atlan
    4. 4. OvalEdgeDawiso vs OvalEdge
    5. 5. DataGalaxyDawiso vs DataGalaxy
    6. 6. OpenMetadataDawiso vs OpenMetadata
    Compare the 6 best Dawiso alternatives

    Dawiso FAQ

    Is Dawiso open source?

    No. Dawiso is proprietary software with no open-source edition.

    How much does Dawiso cost?

    Dawiso Standard starts at €445 a month for 5 seats, with unlimited connectors. Corporate and Enterprise prices aren't published.

    Which data platforms does Dawiso integrate with?

    Dawiso connects to Snowflake, Databricks, BigQuery, Redshift, dbt and Airflow, and to Jira, ServiceNow, Slack and Microsoft Teams for governance workflows.

    Can Dawiso be deployed on-premise?

    Yes. Dawiso runs as SaaS on Azure (EU regions by default), self-hosted on Kubernetes on the Enterprise plan, or hybrid with a scanner behind your firewall.

    What are the best Dawiso alternatives and competitors?

    The closest alternatives are Collibra, Alation, Atlan, OvalEdge, DataGalaxy and OpenMetadata. The Dawiso alternatives page compares their features and pricing and says when to choose each one over Dawiso.

    Browse all 102 tool profiles, grouped by category.

    Evaluating data tools in 2026?

    I curate the most comprehensive lists of data tools, up-to-date comparison tables, and actionable market guides for data teams. More useful than a Gartner report. More reliable than asking AI. Next up: Data FinOps.