Data lineage - on-premise architecture
Typical {openAudit} deployment for automated flow mapping, usage analysis, and dead-branch detection.
Filter by keyword or click a technology.
Typical {openAudit} deployment for automated flow mapping, usage analysis, and dead-branch detection.
Typical {openAudit} deployment in SaaS mode for automated flow mapping, usage analysis, and dead-branch detection.
Automated publication of data lineage, dependencies, and usage to the leading Data Catalog solutions on the market.
Containerized architecture enabling secure extraction, anonymization, and processing of the metadata used by {openAudit}.
Native protocols and interfaces (JDBC, ODBC, REST API, SDK, exports) used to collect metadata from databases, ETL tools, and data visualization tools.
Automated conversion of legacy ETL processes into open, portable SQL pipelines.
Migrating legacy ETL platforms to dbt using data lineage, usage analysis, and automated SQL model generation.
Reverse engineering of the read and write connectors of legacy ETL platforms (DataStage, Talend, Informatica, BODS, SSIS...) ahead of a migration to open SQL.
Running migrated ETL processes as SQL in an open, serverless container orchestrated by Airflow, with no dependency on the original ETL platform.
Automated analysis of SAP BusinessObjects, universe simplification, and migration to Power BI with business intelligence preserved.
Automated analysis of SAP BusinessObjects, universe simplification, and migration to Looker with business intelligence preserved.
Automated migration of IBM Cognos estates to Power BI, with reconstruction of the semantic layer and recovery of reports.
Externalize calculations, indicators, and business rules from SAP BO, Cognos, Power BI, or Spotfire into an open SQL and semantic layer: {oa-lake}.
{oa-lake}: a multi-source SQL interoperability layer with a built-in semantic layer, to define business objects and KPIs once for every BI tool.