Backups and Restore

The Platform → Backups tab (and the per-site Sites → <site> → Backups shortcut) lets admins take, download, delete and restore backups. All backups — for every site plus the platform — appear in a single table sorted by creation date.

What each backup contains

  • Site backup (created against a specific site) — contains:
    • Templates (templates/<templateId>.json)
    • Pages, laid out hierarchically by slug (pages/<parent-slug>/<child-slug>.json)
    • Site settings, including the site's theme and breakpoints (settings/site-settings.json)
    • Assets used by the site, copied from the asset store (assets/<relative-path>)
  • Platform backup — contains platform-level settings only: design variables, component definitions, page types and platform breakpoints. Does not contain any sites, templates, pages or assets.

Creating a backup

  1. Open Platform → Backups.
  2. Click Create Backup.
  3. Choose the target:
    • a specific site (backs up templates, pages, settings, theme and assets for that site), or
    • Platform settings only (backs up platform-level settings).
  4. The backup appears in the table with an In Progress badge. The table auto-refreshes every 15 seconds; the badge switches to Complete when the zip is ready.

Downloading, re-installing and deleting

For each completed backup the table exposes:

  • Download — a short-lived pre-signed URL to the zip.
  • Re-install (site backups only) — opens the restore dialog with the backup's origin site pre-selected. You can pick any site as the restore target, so a backup made for one site can be applied to another.
  • Delete — removes the DynamoDB record and the S3 object.

Failed backups can also be deleted; the failure message is shown inline.

Restoring from an uploaded file

  1. Click Restore at the top of the page.
  2. Pick the site to restore into.
  3. Choose the backup zip file.
  4. Confirm — the target site's templates, pages and settings (including theme) are replaced from the backup.

Assets in the backup (the zip's assets/ folder) are written into the target site's asset library at the same paths: a file that doesn't exist yet is added, and a file that already exists at that path is overwritten with the backup's version. Assets in the library that aren't in the backup are left untouched. Restored assets are also copied to the live site straight away, so images and downloads work without waiting for the next publish.