Your source code stays on the laptop
ShipsuitAI never uploads your repository. Every byte that leaves goes through one auditable channel — the same one you can hand your security team.
- Developer machinerepository · keys · file paths
- One channelcounts · durations · versions
- ShipsuitAIrules · metering
everything that leaves
Enforced by design, not by policy
Not a policy — a property of the design. Every check runs locally, and your source code never leaves the machine.
Seven guarantees, at a glance
Enforced by schema, not by promise
An allowlist at the boundary — an unnamed field cannot be stored.
Your source code never leaves
The repository stays on the laptop — no file is ever uploaded.
Metadata only, and we list it
Counts, durations, versions — no source, no file paths.
Isolated per company, proven
One choke point, one test suite that has to stay green.
Per-developer tokens
Your own credential, revocable without touching anyone else's.
Your rules stay yours
Served per run, never written to disk — they leave with you.
An audit trail that outlives its subject
Append-only, and it survives the deletion of what it describes.
Enforced by schema, not by promise
The ingest boundary is an allowlist. A field we haven't named cannot be stored, however the payload changes.
Your source code never leaves
Reviews run against your code locally and send back findings, never the code itself.
Metadata only, and we list it
Counts, durations, model names, versions. No source, no file paths.
Isolated per company, proven
Every query is scoped by company at a single choke point — a test suite that must stay green proves it.
Per-developer tokens
Each person gets their own credential. Offboarding someone kills their access alone.
Your rules stay yours
Licensed rulesets are served per run and never written to a developer's disk.
An audit trail that outlives its subject
Every administrative action, recorded append-only. Entries survive even the deletion of the account they describe.