Back to home

    Integration

    Hand your ETL stack a hash‑chained, audit‑ready spec

    Magellan emits the governed mapping artifacts your existing ETL/ELT tools already accept — every export carries the ULID and ledger entry it was generated from, so the transformation that runs in Informatica, dbt, or Glue is the one an auditor can trace back to a signed decision.

    Compare integrations

    Each adapter emits the artifact your existing runtime already accepts, writes a provenance trail to the ULID-keyed audit ledger, and slots into the CI/CD platforms listed below. Hash-equality between the committed artifact and the signed Magellan export is the same check across every row.

    Informatica & Talend

    Artifact format

    • PowerCenter XML (9.x, 10.x)
    • Talend .item / .properties

    Ledger entries

    ArtifactExportedArtifactImportedApproverReleaseSignedReleasePromoted

    CI/CD pairings

    GitHub ActionsGitLab CIAzure PipelinesJenkins
    dbt & Modern Data Stack

    Artifact format

    • schema.yml
    • models/*.sql (Snowflake · BigQuery · Redshift · Databricks · Postgres)
    • tests/*.sql

    Ledger entries

    ArtifactExportedApproverReleaseSignedQualityGateEvaluated

    CI/CD pairings

    GitHub ActionsGitLab CIdbt Cloud jobs
    NiFi · ADF · Glue

    Artifact format

    • NiFi flow template XML
    • ADF ARM templates (linked services · datasets · data flows)
    • Glue Studio JSON + PySpark / Spark SQL

    Ledger entries

    ArtifactExportedArtifactImportedApproverReleaseSigned

    CI/CD pairings

    GitHub ActionsAzure PipelinesAWS CodePipeline
    CI/CD Pipelines

    Artifact format

    • API client (no artifact emitted)
    • Hash-equality assertion against committed artifact

    Ledger entries

    ReleasePromotedQualityGateEvaluatedPipelineEventReceivedPipelineEventEmitted

    CI/CD pairings

    GitHub ActionsGitLab CIAzure PipelinesJenkinsCircleCI

    Informatica & Talend

    Export governed mappings as Informatica PowerCenter XML or Talend .item definitions. Each export filename and embedded comment carries the source ULID and ApproverReleaseSigned entry hash, so an auditor can prove the transformation running in production matches the version a Magellan Approver actually signed.

    Read more

    dbt & Modern Data Stack

    Generate schema.yml plus dbt model SQL from a signed Magellan mapping version. The generated header pins the ULID range and SHA‑256 chain head, so dbt build against a stale spec fails CI before it ever touches the warehouse.

    Read more

    NiFi, Azure Data Factory & AWS Glue

    Emit NiFi flow templates, Azure Data Factory linked-service JSON, and AWS Glue job scripts — each artifact embeds the source mapping ULID and is regenerable byte-for-byte from the ledger, so a change in the runtime that didn't originate in Magellan is immediately detectable.

    Read more

    CI/CD Pipelines

    A GitHub Actions or GitLab CI step calls the Magellan API with the target environment's pinned mapping ULID. The job fails if the artifact in the repo doesn't hash-match the signed ledger entry, blocking promotion of any transformation that wasn't approved under role-at-time-of-action RBAC.

    Read more