A different tool per database
Postgres changes go through one pipeline, MySQL through another, and the document stores through none at all.
Use case · Multi-database fleets
One change workflow across every database you run.
Postgres for the app, ClickHouse for analytics, MongoDB for documents, Snowflake for the warehouse — every engine with its own tools, scripts, and habits. Shipyard puts one governed workflow across all of them.
The problem
Every engine has grown its own process.
Inconsistent review standards
The engines with tooling get reviews. The rest get whatever the person on call remembers to do.
No single view of change
When something breaks, there is no one place that shows what changed across the fleet — just scattered histories.
How Shipyard helps
The same governed path, whatever the engine.
Shipyard catalogs 22 database engines and applies the same propose–validate–review–release lifecycle across your fleet.
22 engines, one model
Relational, warehouse, and NoSQL systems — from PostgreSQL, MySQL, and SQL Server to ClickHouse, Snowflake, BigQuery, and MongoDB — organized as project → environment → database.
Engine-aware validation
Validation rules understand each engine’s dialect and risks, with capabilities gated per engine so nothing is silently unsupported.
One dashboard for all change
A needs-your-action feed, activity trends, and per-database change counts — across every project and engine.
Query anything, read-only
Query Studio speaks SQL and constrained read-only commands for document stores, so the whole fleet is explorable from one place.
How it works
From first connection to governed changes.
Map the fleet
Create projects and environments, then register each database — whatever the engine.
Set policy once
Approval rules apply per project, so Postgres and MongoDB changes meet the same bar.
Propose changes anywhere
Migrations are validated with engine-aware rules and reviewed in one consistent flow.
Watch it all from one screen
The dashboard shows pending approvals, releases, and activity across the entire fleet.
Stop running a different process per engine.
One governed workflow across 22 database engines — self-hosted or managed.