Preview and production deployment

Preview is intentionally easy; production is intentionally gated and evidence-backed. A labeled preview is the version used for visual review and quality checks. Production requires the same version's quality check, launch approval, deployment manifest, runtime smoke, and recorded production URL.

CURRENT PRODUCT CAPABILITIES2026-08-14

Managed preview

Shipsite can publish a project-scoped preview before you connect a domain, GitHub, or Cloudflare. The preview is labeled as not live and is the version used for visual review and quality-check evidence.

Studio Preview tab with a private access-governance note while the labeled preview is still connecting. — Preview is labeled private and not treated as live. The connecting frame is real until a completed build publishes an isolated preview.

Shipsite-managed production

The default platform mode can promote the checked static bundle to Shipsite-managed Cloudflare after the quality check and your production approval. Source versions remain exportable; the deployment receipt records the exact approved version.

Launch check panel stating the current candidate can be published after every required item passed. — Passing checks is not a silent publish. Production still needs you to promote the named candidate.

Your Cloudflare account

Own-Cloudflare mode requires a verified, target-scoped token. Shipsite renders the approved site into the owner's Worker, binds the selected domain, applies the supported security baseline, and records partial evidence when an account plan cannot apply a setting. Large OpenNext sites use the repository delivery path rather than the compact static Worker bundle.

Connect Cloudflare

Release order and rollback

Production requires the exact-version quality-check result, launch approval, deployment manifest, runtime smoke, and recorded production URL. Rollback points to an immutable prior version; new source and production stay separate until the release succeeds.