Pipeline Passports
Issue a shareable trust warrant when checks pass. Auto-revoke on silent failure or KPI drift — the artifact execs and auditors can actually open.
Free for 2 pipelines — catch silent failures, issue Pipeline Passports, and prove data is trustworthy when Airflow only proves the job ran.
DataXPipe
The pipeline catalog and trust runtime that catches silent failures when orchestration succeeds but data is stale or drifted. Import dbt or Airflow. Issue a Pipeline Passport stakeholders can trust.
No credit card · Passports · PR blast radius · Consumer contracts
Airflow task: orders_daily_sync → SUCCESS ✓
Freshness check: mart.executive_kpis → FAIL (stale 38h)
KPI drift: revenue_daily → FAIL (+42% vs baseline)
Passport ppt_8f2a → REVOKED (check_failure)
warrant was active until 09:15 · owner analytics-eng
Blast radius:
raw.orders → mart.orders_daily → mart.executive_kpis
↳ 3 downstream dashboards · 1 consumer contract at risk
Share link disabled until checks pass and passport re-issues.Silent failures
Green Airflow, stale or drifted data — caught before the board pack
Passports
Shareable trust warrants with SLA expiry and revoke-on-fail
PR blast radius
Downstream, contracts, and passports at risk before merge
dbt manifests, Airflow DAGs, and warehouse metadata become catalog entries with checks and lineage — one contract, not four tools.
Issue a shareable trust warrant when checks pass. Auto-revoke on silent failure or KPI drift — the artifact execs and auditors can actually open.
Diff a pipeline spec in CI and see downstream datasets, consumer contracts, and passports at risk before merge — commented on the pull request.
Producers write the pipe. Consumers write the promise — max staleness, row floors, KPI checks — with compatibility status against live producers.
Catch wrong-but-green failures: kpi_baseline, row_count_drift, and distribution_drift against rolling baselines — not just freshness.
Register pipelines, datasets, and connections in one contract. Import dbt or Airflow — don't start from blank YAML.
Freshness and quality checks tied to runs. Alert when orchestrators succeed but data is stale — before stakeholders open the dashboard.
Outcomes
Customers don't buy metadata. They buy fewer incidents, faster debugging, and proof for compliance.
Before the dashboard breaks
Orchestrator green, warehouse stale — or worse, KPI drift. Freshness and semantic checks revoke the Passport before stakeholders open the board pack.
See who you wake up
PR blast-radius preview lists downstream datasets, consumer contracts, and passports at risk — commented on the pull request.
Pipeline Passport
One contract generates, observes, and warrants. Consumers declare promises; producers honor them — without four disconnected tools.
The five-minute question
“Why not dbt + Airflow + Great Expectations?”
Because you maintain four disconnected systems. DataXPipe is one contract with a live trust runtime — Passports, consumer contracts, and CI impact — so Day 2 operations get easier, not harder.
15-minute proof
The aha moment isn't writing YAML. It's catching a silent failure with lineage and checks before executives notice.
Import a dbt manifest, paste an Airflow DAG, or discover tables from Postgres — no greenfield YAML marathon.
Start from your messy reality, not a blank spec.
DataXPipe builds freshness, drift checks, and lineage from one contract — tied to the tables that matter.
One source of truth for observe + govern.
When orchestration is green but mart.executive_kpis is stale (or drifted), the Passport revokes with blast radius.
AI explains the failure and what to check upstream.
Re-issue a Pipeline Passport after recovery. Share the link with finance — or wire consumer contracts and CI impact next.
Alerts go to email/Slack with check context.
Trusted by data platform teams
Design partners use DataXPipe to catch silent failures, bootstrap catalog coverage from dbt, and onboard engineers with clear roles.
“We caught a stale executive dashboard before the Monday review — Airflow was green, the passport was revoked, and Slack had the blast radius in one message.”
“PR impact comments show which consumer contracts break before we merge. We stopped guessing who to page from dbt DAG diffs.”
“Finance declares staleness in a consumer contract; we issue a passport when KPIs land. Auditors ask for the share link, not a Slack archaeology tour.”
Because you maintain four disconnected systems. DataXPipe is one contract that generates artifacts, registers metadata, and records check results.
| Need | Typical scattered stack | DataXPipe |
|---|---|---|
| Silent failures (green Airflow, stale data) | Task logs + manual SQL | Freshness checks + Passport revoke |
| Prove data is trustworthy | Slack screenshots | Shareable Pipeline Passport |
| PR impact before merge | Hope + tribal knowledge | Blast-radius report in CI |
| Consumer vs producer SLAs | Email threads | Consumer contracts + compatibility |
| Wrong but green KPIs | Found by executives | KPI / distribution drift checks |
| Lineage & ownership | Spreadsheets + dbt docs | Catalog API + import from dbt/Airflow |
Vision
Not another catalog to configure — a platform that imports what you already run, issues Pipeline Passports, previews blast radius in CI, and keeps producers honest against consumer contracts. One contract replaces scattered Airflow glue, quality scripts, and wiki docs.
dbt manifests, Airflow DAGs, and warehouse discovery — not greenfield YAML homework.
Freshness, KPI drift, lineage blast radius, and shareable Pipeline Passports.
Producer specs + consumer promises with PR impact analysis before merge.
Roadmap
We ship in the open. Early access users shape what lands next.
Available today
Silent failures, passports & PR blast radius
Import dbt/Airflow, catch green-but-stale failures, issue Pipeline Passports, and preview impact in CI.
Freshness and volume checks that fail when Airflow is green but data is stale.
Shareable trust warrants with SLA expiry, auto-issue on pass, revoke on fail.
POST /specs/impact + GitHub Action comments for downstream, contracts, passports.
Consumers declare staleness/row expectations; compatibility checks vs producers.
kpi_baseline, row_count_drift, and distribution_drift — wrong but green catches.
Bootstrap lineage and default checks from manifest.json or DAG source.
Stale demo → explain → passport → register in one session.
Q3 2026
Deeper runtime & authoring
AI-assisted spec drafting and richer hosted API surfaces for Day 2 teams.
api.dataxpipe.com — register pipelines and query runs from day one.
Failed checks routed to email and Slack incoming webhooks in Settings.
Click any dataset — see upstream/downstream blast radius visually.
Describe a pipeline in plain English; get a reviewable YAML contract.
Validate + impact on PR; register from protected branches.
2026 & beyond
AI control plane at scale
From assisted authoring to autonomous suggestions — always with human review before production.
Connect Snowflake/BigQuery — suggest contracts, owners, and freshness SLAs.
Suggested backfills, reruns, and owner escalations when checks fail.
Vetted specs for common warehouse and orchestration patterns.
SAML/OIDC, immutable audit logs, SOC 2 readiness.
Shape the roadmap
Request a workspace, tell us your stack (Airflow, dbt, Snowflake, BigQuery), and get priority when self-serve API access opens.
A repeatable workflow from declarative specs to observable production pipelines.
Author a YAML or JSON spec with sources, targets, lineage edges, and quality checks. DataXPipe validates it against a JSON Schema before anything runs.
Get Airflow DAGs, SQL transforms, runnable check scripts, and metadata bundles. Generated DAGs notify the catalog on every run.
Register pipelines in the catalog API, query lineage for any dataset, and review check results tied to each run — all from one place.
Two pipelines on Free forever. Team from $99/mo when you need more connections, retention, and support — transparent pricing, no sales call.