The database step should look like the rest of the pipeline
You already automated services. Schema still arrives as a ticket and a shared password. Migratrix models promotion once, binds GitHub or GitLab if you want SQL in Git, and runs the Executor next to the database so the control plane never holds the password.
Executor, pipelines, Git, not another CD product
Outbound-only Executor
TLS to Migratrix to register. Bind 0.0.0.0:4002, set a public URL you control. No inbound hole required for registration. Credentials encrypted on that host.
Pipelines are modelled once
DEV → QA → PROD with per-environment approvals and generated rollback. Manual or GitOps source. Auto-start first environment is optional.
Keep application CI
Migratrix does not ask you to move service deploys. It is the missing database promotion product beside GitHub Actions or GitLab CI.
MCP is confirmation-gated
Assistants can list and inspect. Mutating tools require confirm: true. Same objects as the UI. Compare, Conversion Studio, and Drift stay in the product today.