ShipSure
Sign in

FAQ

The questions people actually ask, answered without marketing.

Every time a connected agent finishes editing a project ShipSure is watching. Runs you trigger yourself with `shipsure verify` count too.

No. Your agent works exactly as it does now — ShipSure watches the folder and checks the result after it stops. You keep shipping at the same speed; you just find out when something broke instead of finding out in production.

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

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

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

Not covered here? Email support@shipsure.space, or read the docs.