What happens on deploy
The first successful ZIP deployment creates Release 1 and sets it as the Space current Release. Later ZIP uploads create the next Space-local Release number.
The stable hosted URL points to the active Space content. Release-scoped URLs are for inspecting a selected historical Release and remain immutable.
Deploy an update
The current website stays live until deployment. Each source replaces the complete Live project; HTML mode deploys only root index.html, so other existing assets are not retained. Settings-only saves will not send pending source.
- Open the Space editor, select Source, then choose NEW DEPLOY beside Version. The Spaces list also offers a compact Deploy new version dialog that sends only source and publishing options, not Space settings.
- Choose ZIP package, Files & folders, or HTML and prepare the replacement project.
- Choose Deploy new version to deploy the prepared source. Wait for the Release to become ready, then verify the hosted URL.
- Choose Releases beside Version, or Deployed Releases in the Spaces list, to open the dedicated history page. Releases lists retained snapshots; Activity shows this Space deployment and restore history only, not the account-wide Activity log.
Tips and limits
- A Release number is the user-facing version for that Space. Database record IDs are internal and should not be used as release labels.
- Do not edit a Release directory to update a site. Upload another ZIP or use Live Workspace where appropriate.
Restore a ready Release
Restore copies a ready historical snapshot into mutable Live files without changing the snapshot or creating another Release. Live files may have changed since the current Release baseline.
- Open Deployed Releases for the Space.
- Choose Restore to Live & edit on a ready Release.
- Confirm replacement of all current Live files. The editor opens after successful restore; then check the stable hosted URL.
Retained history and storage
Community and Free accounts retain up to 2 Releases per Space. Active Premium or Advanced accounts retain up to 10, including Free-mode Spaces. The current version counts toward the limit.
A successful new deployment removes the oldest non-current versions beyond the allowance. Failed deployments, restores and Live edits do not remove history. Existing excess history remains until a successful new deployment.
After a valid paid Premium or Advanced period expires, the 10-Release allowance remains for 30 days. This is retention grace, not continued hosting or API access. After grace, the next successful deployment applies the 2-Release limit. Immediate revocation does not grant grace.
Dedicated-mode storage charges include all retained ready Release files at the server-owned storage rate, prorated daily. Free-mode Spaces remain unmetered. Keep source files and long-term backups locally.
Evicted Release URLs may remain in CDN or browser caches; removing history does not guarantee immediate cache erasure.