Pricing
One licence per organisation, renewed annually. Everyone who works on your migrations is covered: no per-seat counts, no usage metering, no data collection.
Initial pricing hypothesis — subject to validation
$290 per organisation per year is the intended price. No purchase has tested it. There is no checkout, no payment processor connected, no licence issued and no customer. The number is published early so the model is clear, not because anything can be bought today.
| Evaluation | Organisation licence | |
|---|---|---|
| Price | free | $290 / organisation / year (hypothesis) |
| Duration | 30 days from the first run | 12 months, renewable |
| Who | one per GitHub owner — organisation or personal account | one per organisation |
| Product | identical — all rules, all outputs, annotations, configuration, suppressions | |
| Releases | the current release | every release published while the licence is active |
| Rule upkeep | MySQL online-DDL rules maintained against the manual as MySQL changes | |
| How it is delivered | automatically, inside GitHub Actions — nothing to copy | a signed key you set as the license input or PRESIFT_LICENSE |
| Where it works | GitHub Actions only | GitHub Actions and the command line |
| After it ends | the check stops that day | 30-day grace period, then the check stops |
| How you would buy | — | through a merchant of record — not live |
What you would be paying for
Presift running in your pull requests and staying correct: the online-DDL matrix, the destructive-change rules and the remediation advice maintained against the MySQL manual as releases change. The check is deliberately small, offline in the sense that matters — your SQL never leaves your runner — and boring to operate.
What you would not be paying for
No dashboard, no hosted analysis service, no account, no telemetry. Presift never sees your schema, your data or your traffic — only the statements in your migration files. See what is actually collected.
Honest limits
Presift does not guarantee zero downtime, and a clean run does not mean a migration is safe: it
analyses statements, not your live database. It reads .sql migrations — not Liquibase
XML/YAML, framework DSL migrations, PostgreSQL or SQL Server — and runs on Linux x86_64 runners today.
Start the 30-day evaluation Tell us it would be worth paying for