Platform Integrations
Makoto is a specification â the same DBOM format works on any pipeline platform. These pages explore how Makoto attestations could be emitted natively from common data tools. All integrations are conceptual: real 9-platform coverage is the goal, not the current state.
Supported Platforms
Apache Airflow
DAG-driven orchestration â emit DBOMs at every task boundary.
Orchestratordbt
Transform attestations per model run â emitted from post-hook macros.
TransformationsApache Spark
Stage-level attestations via SparkListener â works on EMR, Databricks, OSS.
Distributed ComputeApache Kafka
Producer/Consumer Interceptors â stream-window attestations per partition.
StreamingSnowflake
Stored procedures + Tasks emit DBOMs on every load and transform.
WarehouseDatabricks
Unity Catalog + Job event hooks â DBOMs for every notebook and job run.
LakehouseDagster
Asset materialization metadata is already half a DBOM â finish the job with a signed envelope.
OrchestratorPrefect
Flow + task state hooks turn Prefect into a DBOM publisher.
OrchestratorExpanso
Edge-to-cloud DPL pipelines with native Makoto processors.
Edge PipelinesCommon Integration Patterns
Most platforms expose at least one of these surfaces â Makoto plugs into whichever is most natural:
| Pattern | Where Makoto attaches | Used by |
|---|---|---|
| Lifecycle hook | on_success / on_completion callbacks fire after each task | Airflow, Prefect, Dagster |
| Custom operator/asset | Drop-in subclass that wraps existing primitives | Airflow, Dagster, Databricks |
| Interceptor / SMT | Per-message hook on producer/consumer or connector | Kafka, Kafka Connect |
| Macro / post-hook | SQL-templating language injects attestation into transforms | dbt, Snowflake |
| Listener / event subscriber | Catalog or platform fires events on materialization | Spark, Databricks, Unity Catalog |
| IO manager / result serializer | Hash on write, verify on read | Dagster, Prefect |
Bring Your Own Platform
Don't see your platform? The Makoto spec is platform-agnostic by design. The pattern table above covers most cases â if your pipeline can produce a content digest and sign a DSSE envelope, it can ship a DBOM.