Protected databases
Name the production databases you guard and assign each stored connection to one — several shadow or replica connections per database. Nothing is read from a connection string; the name is all we hold. 1 on Startup, 5 on Team, unlimited on Scale.
A protected database is a name: the production system a set of migrations is meant to reach. Each stored connection is assigned to one, so several shadow or replica connections can stand in for the same production database and the run log and Insights roll up by what was protected rather than by which replica happened to answer.
Nothing is read from a connection string to create one. The name is all the service holds. It is the unit paid plans scale on — one on Startup, five on Team, unlimited on Scale — because it is the unit that maps to what a team is actually guarding.
The CLI is open source and needs no account: npx bolvrk check migration.sql