Circuit breakers
A revoked Passport pauses the Airflow DAG, cancels in-progress dbt Cloud runs, and disables Hightouch and Census syncs. Rerun unlocks when the Passport is active again.
Detect the silent failure, revoke the Passport, and stop Airflow, dbt Cloud, Hightouch, and Census. Prove it with an SLA report. Keep warehouse credentials in your VPC.
A revoked Passport pauses the Airflow DAG, cancels in-progress dbt Cloud runs, and disables Hightouch and Census syncs. Rerun unlocks when the Passport is active again.
Run checks inside your cluster. Warehouse credentials stay there. DataXPipe receives pass/fail and aggregates — not sample rows or SQL.
Silent failures caught, data uptime, mean time to detect, and freshness SLA compliance. A dollar figure appears only from a cost you enter.
Okta, Azure AD, and Google Workspace via OIDC, plus SAML. Viewer, Analytics Engineer, and Admin — so security review is a configuration, not a stall.
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.
Monte Carlo can fail an Airflow task if you insert their operator into the DAG. That operator fails open by default, so a timeout does not stop the pipeline. Elementary reports a failed dbt test and leaves the next job running.
DataXPipe arms a breaker on the dataset. When a check revokes the Passport — including after Airflow already reported success — the breaker pauses the DAG, cancels in-progress dbt Cloud runs, disables the Hightouch sync, and pauses Census. Rerun is locked until the Passport is active again. Slack links to that Passport. It does not rerun the job from the chat.
Security reviews stall when a vendor asks for warehouse credentials and sample rows. The DataXPipe agent runs in your Kubernetes cluster, executes the check locally, and uploads pass/fail plus aggregates such as delay minutes and row count.
The catalog, Passports, and circuit breakers stay in DataXPipe. Connection strings do not.
The report a finance partner can read: silent failures (a check failed while the orchestrator run was green), data uptime (share of the window a Passport was active), median time from a green run to the failed check, and the share of freshness checks that passed.
A dollar estimate appears only if an admin enters an assumed incident cost. There is no invented savings number.
Sign in with Okta, Azure AD, or Google Workspace. OIDC is built in. SAML 2.0 is available when the SAML library is installed on the API.
Viewer, Analytics Engineer, and Admin. Platform owners can configure SSO and agents. Client secrets are references to your secret store, not values saved in DataXPipe.
Issue a shareable trust warrant when checks pass. Auto-revoke on silent failure or KPI drift so execs and auditors never open a stale link.
Each passport captures SLA expiry, owner, lineage hash, and check summary — the artifact your board pack can link to.
Diff a proposed pipeline spec against the catalog and walk lineage multi-hop. See downstream datasets, consumer contracts, and passports at risk before merge.
GitHub Actions examples post the markdown report as a PR comment.
Dashboard and BI owners declare max staleness and row floors. Compatibility status compares those promises to producer freshness SLAs and active passports.
Broken contracts appear in PR blast-radius reports so merges don't wake Monday's board pack by surprise.
Wrong but green: freshness can pass while a metric drifts. kpi_baseline, row_count_drift, and distribution_drift compare against rolling baselines from prior passing runs.
Failures revoke passports and feed AI explanations that cite the last trusted warrant.
Freshness evaluation honors max_delay_minutes and threshold_hours server-side — status is derived, not caller-supplied.
Alert when orchestrators succeed but marts are stale, with lineage blast radius on the failure explanation.
Vision
Import what you already run. When a check fails, revoke the Pipeline Passport and pause the next hop — Airflow, dbt Cloud, Hightouch, or Census. Prove uptime to the people who approve the budget. Keep warehouse credentials in your VPC.
Freshness, volume, and KPI drift when the orchestrator is already green.
Circuit breakers on Passport revoke, then a rerun once the Passport is active.
Shareable Passports, an SLA report, and SSO roles for the security review.
Roadmap
We ship in the open. Early access users shape what lands next.
Available today
Detect, pause, and prove
A green run that fails a check revokes the Passport, pauses downstream jobs, and shows up on the SLA report.
Passport revoke pauses Airflow, cancels in-progress dbt Cloud runs, and disables Hightouch and Census.
Checks run in your cluster. Credentials stay there. Aggregates upload to the catalog.
Silent failures, data uptime, time to detect, and freshness SLA compliance.
OIDC and SAML. Viewer, Analytics Engineer, and Admin. Secrets stay as references.
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.
Dagster, Prefect, and Fivetran alongside Airflow and dbt Cloud.
Vetted specs for common warehouse and orchestration patterns.
Approve a rerun from Slack or Teams. Today the alert links to the Passport.
Shape the roadmap
Request a workspace, tell us your stack (Airflow, dbt, Snowflake, BigQuery), and get priority when self-serve API access opens.
Spin up the API locally, generate the example orders_sync pipeline, and register it in under five minutes.