Preview privately, publish deliberately and restore retained files.
An inspection prepares evidence. A private preview lets you review built files. Publishing selects a checked release for visitors, and restoring selects a retained successful release without rebuilding.
Create a private preview
Inspect your website, then choose Prepare private preview. Create a release link lasting one hour, one day or seven days. The full bearer link is shown once; anyone with that link can view the release until it expires or you revoke it. It is not a password-protected website or an account login.
Review pages, links, styling and browser interactions on that address. Shared preview origins have sandbox restrictions, so behavior that depends on cookies or storage needs testing on your verified custom domain too.
Publish and verify the result
Choose Confirm & publish, or Publish preview for an existing preview, and confirm the exact release. Deployment repeats relevant checks and makes an HTTP request to the candidate page before selecting it. Open the returned live address and test the features that matter to your users.
A failed candidate leaves the selected release in place. Read the error code and reference ID before retrying. An HTTP response check does not verify every asset, third-party API or client-side interaction.
Restore a successful release
Open a retained successful release and choose Restore release. Confirm the target. Its retained files become the selected website and the action appears in Activity. A failed release is not a restore target. Restoring a project that is paused does not automatically resume it; check its state and resume explicitly when ready.
Retirement and storage
An owner or admin can retire an unused release. This revokes preview links and frees a release slot. The extracted files remain recoverable for seven days and still count toward storage until cleanup. The original uploaded ZIP and history remain. The selected live release cannot be retired.
Original uploads have a separate removal flow in Usage & plans → Stored uploads. Removal requires the relevant permissions, filename confirmation and account verification, and can be cancelled within seven days. A needed live or retained artifact cannot be removed. Download a copy before scheduling removal.
Is release history a complete backup?
No. Retained static files are a publishing recovery path. They do not back up an external database, API or customer runtime. Account record exports also do not include a complete website-file backup. Keep your own source, built output and any external data backup.
Explore the product and guides
Access is invitation-only. No payments are collected during the private beta. Sign in to your invited workspace.