Ad-hoc SQL in production
Someone pastes a statement into a prod console at 6pm. There is no review, no record, and no way to know what actually ran.
Use case · Migration approvals
Stop unreviewed SQL from reaching production.
Application code gets pull requests, tests, and CI. Database changes deserve the same bar. Shipyard puts every schema change behind validation, review, and explicit approval — before a single statement runs.
The problem
Schema changes are the riskiest deploys you ship.
Review happens in Slack
A screenshot of a query and a thumbs-up emoji is not an approval process. Context scatters and accountability evaporates.
One bad ALTER, hours of downtime
A blocking index build or destructive statement slips through because nothing checked the SQL before it hit the database.
How Shipyard helps
Every change becomes a reviewable migration.
Shipyard gives database changes the same lifecycle your application code already has — proposed, validated, reviewed, approved, released.
Migrations as changesets
Propose schema changes as ordered, multi-statement migrations targeting one database — with a title and context reviewers can actually evaluate.
Pre-flight validation
Engine-aware rules check every statement before review. Destructive patterns and risky operations are flagged early, with thresholds you control.
Approval policy per project
Decide who can approve, who can release, how many distinct approvals are required, and whether authors may approve their own work.
Release now — or on schedule
Designated releasers apply approved migrations through a dedicated write connection, immediately or scheduled for a quiet window.
How it works
From first connection to governed changes.
Connect your databases
Add read and write connections per database, organized by project and environment.
Set the approval bar
Configure reviewers, releasers, required approval count, and self-approval policy per project.
Propose and review
Engineers draft migrations, validation runs automatically, and reviewers discuss in threaded comments.
Apply with confidence
Approved changes are released through the controlled write connection, with the full history recorded.
Give database changes a real review process.
Set up your first governed migration in minutes — self-hosted or managed.