Stored connections
For zero-setup CI: sealed-box encrypted connection strings, opened per-check, read-only, catalogs only. 2 on Startup, 8 on Team, 25 on Scale, custom on Enterprise.
A stored connection lets the GitHub Action run with live-schema context without the runner reaching your database. The connection string is sealed-box encrypted at rest with a key the API process holds, opened only for the duration of a check, and used for catalog reads alone. Pass its id as the Action’s connection-id input and every pull request check is refined against the real schema.
Use a replica or a shadow database, and the read-only role from the setup guide. The health check flags a connection whose role is a superuser, owns tables or holds a write grant, because Bolvrk never needs one.
Health
Stored connections are reached every fifteen minutes and on every use. The Connections page shows the last result, and a check page warns when the connection its context came from has since gone unreachable — so a stale snapshot never reads as a fresh one.
The CLI is open source and needs no account: npx bolvrk check migration.sql