CLOUD · ALPHA 12 · OPT-IN HISTORY
Keep track of what changed.
Ship Check starts with evidence where you build. The Cloud pilot is designed to help you follow a project over time — without collecting your source code.
Open my projects →01 / WHAT IT KEEPS
Useful history. Your source stays with you.
The initial Cloud boundary accepts only deliberately synced assurance metadata. It does not store application source, full findings, credentials or evidence excerpts.
Checks stay in your environment
Run Ship Check locally or in your own CI runner. The public playground remains a separate, temporary scan service.
Only summary metadata is synced
Coverage, counts, ruleset provenance and changes. No raw source or full scan reports.
Opt in, with a retention choice
Connected projects specify their retention period; scoped API tokens can be expired or revoked.
A timeline rather than a safety score
Project history shows scan coverage and changes — it never pretends the whole app is safe.
02 / PILOT STATUS
Built for ongoing understanding.
Cloud sign-in, a browsable project timeline and scheduled vulnerability alerts are not available through this pilot landing page yet. The metadata API and optional CI sync are foundations for those features.
Until the hosted database and authentication have been verified end-to-end, Cloud should not be treated as an active monitoring or alerting service.