MigrationPilot

About MigrationPilot

MigrationPilot analyses PostgreSQL migrations for the operations that will take a lock and stall production, and it does the analysis locally and deterministically using PostgreSQL's own parser rather than regexes over SQL text. It ships 112 rules covering lock acquisition, missing lock and statement timeouts, non-concurrent index creation, unvalidated check constraints, column type changes and dependent objects, each producing a risk score, an explanation of why the rule exists and a safe rewrite. Twenty rules auto-fix; ten more print a plan when the fix needs choreography rather than a substitution. Fifteen of the 112 read table sizes, write traffic and replication state from a live database when given a connection string. It runs as a CLI, a GitHub Action that comments on pull requests, SARIF output, an MCP server and a VS Code extension, and there is a browser playground that runs the real engine client-side with nothing leaving the page. The vendor publishes a benchmark against Squawk and pgfence on 56 labelled migrations — 30 of 33 hazards named against Squawk's 20 and pgfence's 25, at a 5.9% false-positive rate — and names every file it missed. The linter is MIT licensed and free forever. The paid tier's three artifacts — the enforced policy block, the failing CI run and the JSONL audit trail — are all shown on the pricing page as real output rather than mockups, which is an unusually concrete way to justify the gap between a free linter and a paid control.

Key Features

Tags