FAQ

No. Verification runs on your machine, or on a runner you control. File paths and diff statistics are uploaded as metadata so the dashboard can show what changed; the contents of your files are not, unless you explicitly turn that on.

Yes — private runners execute verification on hardware you control, for code that cannot leave your network. A fully self-hosted distribution is on the roadmap and is not built yet; we would rather say so now than have it come up in your security review.

Yes. Every verification run is kept with its evidence — what was checked, what passed or failed, the commands that ran, and when. It is a record of what was actually checked, not a policy document describing what is supposed to happen. Retention is currently unlimited: nothing is deleted on a schedule.

No. Agents work exactly as they do now — ShipSure checks the result after the agent stops. You find out when something broke instead of finding out in production.

All of them. ShipSure never hooks into an agent’s internals — it watches the filesystem and runs your project’s own commands, so Claude Code, Cursor, Copilot, Codex and anything that has not shipped yet are checked identically.

No. ShipSure works on a plain local folder. Git sharpens regression detection because there is a commit to compare against, but a hosted repo is not required.