Shared credentials everywhere
One prod password lives in a vault note half the team can open. Nobody knows who ran what, and rotating it breaks everything.
Use case · Safe team access
People need to look at production data every day — debugging, support, analytics. Shipyard gives them a read-only path that can never mutate data, so access stops being a standoff between speed and safety.
The problem
One prod password lives in a vault note half the team can open. Nobody knows who ran what, and rotating it breaks everything.
Engineers connect with clients that happily execute writes. One missing WHERE clause and you are restoring from backup.
The useful queries live in someone’s scratch file or an old Slack thread. Every investigation starts from scratch.
How Shipyard helps
Shipyard separates read from write at the connection level, so browsing and querying can never touch your data.
Each database gets separate read and write connections. Schema pulls and queries use the read connection — writes only happen via approved migrations.
Run read-only queries with table or vertical views. Engine-aware validation rejects anything write-shaped before it executes.
Save queries with names, tags, and descriptions, and share them with the team via links — your tribal SQL, kept in one place.
Viewers browse and query, editors propose changes, admins manage access — every action tied to a real user, not a shared login.
How it works
Add a read connection
Point Shipyard at a read-only credential for each database. Passwords are write-only once stored.
Invite the team
Give each person a role — viewer, editor, or admin — from the in-app Users console.
Query safely
The team explores schemas and runs SELECT-only queries in Query Studio across 22 engines.
Build a shared library
Useful queries get saved, tagged, and shared, so investigations start from knowledge instead of zero.
Read-only access, individual accountability, and a shared query library — in one tool.