Simulate any schema change before it ships.
Drop a column. Rename a table. Retype a key. The Flux Capacitor walks the live OpenMetadata lineage graph, scores every downstream entity, and drafts the migration plan, Slack message, and pull request, all before you push code.
Pick a change. Preview the blast radius.
OUTATIME walks the live OpenMetadata lineage graph, scores every dependent entity, and drafts the migration before a single line of SQL ships.
See breakage before it ships.
Pick a change. Any change.
Drop a column, rename a table, retype a primary key, deprecate a model. The Flux Capacitor accepts plain-English schema deltas or one of the curated presets.
- Drop / rename / retype / deprecate
- Live OpenMetadata graph or seeded demo
- Zero SQL required
DROP COLUMN orders.customer_regionRENAME TABLE payments → fct_paymentsALTER COLUMN orders.total NUMERIC(18,4)Walk the graph. Score every node.
A deterministic traversal scores every dependent dashboard, dbt model, ML feature, and table by severity, broken, degraded, touched, safe, with the exact reason each landed there.
- Upstream + downstream lineage walk
- Cost delta and SLA risk per change
- Reproducible and CI-safe (no LLM drift)
Ship the comms with the change.
OUTATIME drafts a per-team Slack message, a migration plan in execution order, and a PR description with the actual diff, so the merge announcement isn't an afterthought.
- Per-team Slack drafts (Diplomat agent)
- Ordered migration plan
- PR diff stub, ready to push
Heads up, orders.customer_region is dropping Tuesday…
churn_score_v3 lineage will need a join swap; details inside.
Tier-1 dashboards may render NULL for 1 hour during cutover.