Financial services
One platform for catalog, glossary, lineage and data products. Tell us what is on your desk and we will show you the part that matters.
What is on your desk this quarter?
What the regulator expects
BCBS 239 asks you to show how risk data is aggregated, with accuracy and completeness you can demonstrate on demand.
What breaks today
With Dawiso
370,000+ data tables in 30+ DWHs catalogued at KB What the regulator expects
DORA asks who is accountable for each system and change, and for a record you can show an examiner.
What breaks today
With Dawiso
~4,000 governed documents with approval paths at Raiffeisenbank What your AI team needs
Credit scoring and fraud models need documented inputs, definitions and lineage before they reach production.
What breaks today
With Dawiso
300+ data products in operation at KB What the programme needs
Moving from Teradata or Oracle to Databricks, Snowflake or Fabric starts with knowing what depends on what.
What breaks today
With Dawiso
3.4M+ objects across the environment at Kooperativa In production at banks and insurers across Europe
How it works
Metadata scan · 4 sources
Tables, columns, reports and SQL are picked up automatically, with no manual cataloguing.
Lineage · COREP C 02.00 row 0040
SELECT e.exposure_amt * w.risk_weight AS rwa_credit_sa FROM dwh.exposure e JOIN ref.risk_weights w ON ...
Column-level lineage parsed from your own SQL.
Business glossary · Credit risk
Exposure
The amount at risk for a counterparty at the reporting date, after credit conversion factors.
Default
A counterparty is in default when it is past due more than 90 days or unlikely to pay.
Change history · Definition of default
Regulation coverage
| Regulation | What it asks | Your evidence in Dawiso |
|---|---|---|
| BCBS 239 | Accurate, complete and traceable risk data aggregation | Column-level lineage from source to report, one glossary for risk terms |
| DORA | ICT risk management with clear accountability | Named owners, approval workflows and change history per asset |
| Basel IV | Documented data quality for risk calculations | Lineage of every input to the calculation, with definitions and owners |
| Solvency II | Data quality and traceability for insurers | Catalog, definitions and lineage for the data behind Solvency II reporting |
| GDPR | Know where personal data lives and why | Personal data classified in the catalog and followed through lineage |
Customer story
Komerční banka · KB Financial Group
Scanners for Teradata, Oracle, PostgreSQL, Cognos and Power BI, one glossary for the group, and documentation the business writes itself.
“We use Dawiso as a metadata platform that simplifies working with data, reports, and terms across the complex system of KB Financial Group.”
KB Financial Group
Go-live
You get automated data lineage, data quality integration, and a business glossary: the three pillars of BCBS 239 compliance. You map regulatory requirements to data assets, trace data from source to FINREP/COREP reports, and demonstrate governance controls to regulators on demand. Column-level lineage means you answer "where does this RWA figure come from?" in seconds.
Most financial institutions go live with Dawiso in 4-8 weeks, depending on the number of data sources. Our automated metadata scanning eliminates manual cataloging, and the SQL Parser automatically generates lineage from existing code. No large consulting engagement required - Komerční banka and Kooperativa both deployed Dawiso without multi-year projects.
Banks (commercial, private, and investment), insurers, reinsurers, asset managers, fintechs, and regulators. Clients range from Tier-1 banks in the Société Générale group to specialized reinsurers like VIG Re. Active across CEE, Nordics, Benelux, UK, DACH, and Latin America.
40+ connectors out of the box: Oracle, SQL Server, Snowflake, Databricks, SAP HANA, PostgreSQL, Power BI, Tableau, dbt, and major ETL tools. Also IFRS 9/17 engines, risk engines (Moody's, Wolters Kluwer), and regulatory reporting tools. The REST API and MCP server (available on Databricks Marketplace) enable custom integrations.
Yes. Many of our banking clients run Dawiso on-premise for regulatory and security reasons - including Komerční banka. We also offer SaaS and hybrid deployments. Your data metadata never leaves your infrastructure unless you choose otherwise.
Dawiso uses transparent per-user pricing with no per-connector or per-asset fees. Unlimited data sources and scanned objects included in every plan. Our TCO is lower than open-source alternatives (OpenMetadata, DataHub) in the first 2 years when you factor in implementation, maintenance, and support. See our pricing page for details, or book a demo for a custom quote.
Dawiso is on the Databricks MCP Marketplace alongside Collibra, Alation, and Atlan - one of only four data catalogs listed. We consistently win competitive evaluations against Purview, OpenMetadata, and DataHub, particularly in automated data lineage and SQL parsing. Our strength is in getting regulated institutions to value faster, with lower TCO and without the complexity of enterprise-only vendors.
SOC 2 Type II, ISO 27001, and ISO/IEC 27018 certified. On-premise, private cloud, and SaaS deployments. SSO/SAML/LDAP integration, role-based access control, and full audit logging. Built for institutions where security and compliance are non-negotiable.
A 30-minute session with our financial services team, built around your report, your stack and your regulator.