From OpenLineage events to a governed lineage model

The Solidatus OpenLineage integration is a connector that ingests automated lineage events from tools like Apache Spark, Apache Airflow, and dbt, then processes them inside the Solidatus platform. Rather than display raw events, Solidatus consolidates them into a stable, versioned lineage model, connects them to systems OpenLineage does not instrument, and enriches them with business glossary terms, ownership, and governance policy. The result is a single, governed view of how data moves across both modern and legacy systems, managed under version control for audit and impact analysis.

No. Solidatus supports OpenLineage as an open standard and works alongside it. OpenLineage captures automated, event-based lineage from modern data tools, and because it is neutrally governed by the LF AI & Data Foundation, it keeps your lineage portable across tools. Solidatus ingests those events and adds the layer enterprises need on top: cross-system modeling, business and governance context, version control, and point-in-time history. You keep the openness and flexibility of the standard and gain a complete, governed model of your data ecosystem.

Recurring jobs can emit thousands of OpenLineage events for the same data flow. Solidatus harmonizes that stream into a single, stable model of the underlying flow instead of storing every run as separate lineage. It consolidates repeated job executions into one versioned representation while preserving a link back to the runtime history, so the picture stays clear without losing detail. Events that carry only table-level information can be flagged for enrichment, so teams know where to add column-level detail or business context.

OpenLineage is an event-emission standard for technical lineage that describes what ran inside instrumented tools. Solidatus adds the capabilities a regulated enterprise needs around that: coverage of legacy, mainframe, and manual systems the standard does not instrument; business glossary, ownership, and policy context; Git-like version control with branching and visual diffs; point-in-time history for audit; and design-time impact analysis. It also makes the full model queryable through REST APIs. Together these turn a technical event stream into a governed, auditable map of the whole data ecosystem.

Solidatus can ingest OpenLineage events from any producer that emits them in the standard format. Apache Spark has the most mature OpenLineage support today, with integrations for tools such as Airflow and dbt as adoption grows. Because OpenLineage is an open standard, coverage grows as more tools in your stack adopt it. For systems that do not publish OpenLineage, such as mainframes or custom applications, Solidatus provides modeling tools to capture that lineage and stitch it to the automated events.

Regulations such as BCBS 239 and DORA expect organizations to show how data flows and is controlled, not only at present but at past points in time. A runtime event log alone cannot demonstrate that. Solidatus keeps an immutable version history of the entire lineage model, so governance teams can reconstruct how data moved and was governed at any chosen moment. Combined with business context and end-to-end coverage across modern and legacy systems, this gives auditors a complete, point-in-time view rather than a partial technical snapshot.

It is a Solidatus Integration: a deep connector you configure against your existing OpenLineage event stream to ingest, harmonize, and model lineage. For more complex environments, Solidatus also offers Solution services that pair the technology with discovery, implementation support, and ongoing assistance. Many organizations start with the integration and add solution services as they extend coverage to mainframes, Microsoft Purview, or other systems that need deeper configuration.