How it works

1. Connect.Install the HostSpry GitHub App on the repositories you choose, and, if your app uses Supabase, connect that account too. You authorise each connection on the provider itself; we never ask for a password.
2. Analyse.We inventory the repository: frameworks, a Dockerfile if there is one, database migrations, and the names of the environment variables the code reads — never their values.
3. Plan.Steps, checks, warnings and blockers are shown before anything is written. A blocker says what it is and why.
4. Authorise.Nothing is built on or written to your destination until you do.
5. Build and run.Frontend and backend are built without privileges and run in an isolated environment with its own database, reachable on a preview address.
6. Migrate the backend.Restore point first, then schema, users, data and files, each checked against the source.
7. Report.Verified, failed, or indeterminate — for every check.
8. Operate.Encrypted backups of the environment, restore with its own rollback point, and rollback of a release.

A tool that reports success it did not verify is worse than no tool, because it removes the suspicion that would have made someone check. So every check has three outcomes, not two: verified, failed, and could not tell. The third keeps a migration out of the unattended class — on purpose.