Archiving a site, and bringing it back

Everything. An archived site is not hidden, it is inert, and the key behaves as though it never existed:

• The widget does not load. The boot call answers 404, and the launcher is drawn only after that call succeeds, so nothing appears on the page at all.
• Nothing is answered. Every question is refused before it reaches the model, so an archived site cannot use up your requests or reach any of your tools.
• Nothing is recorded. No conversations, no ratings, no audit rows.
• The sandbox twin goes with it, so the test key stops working too.

Demos and recordings. The moment your key is on screen in a video, a screenshot or a conference talk, it is readable by everybody who ever watches, and unlike a leaked secret you cannot rotate it out of a file somebody else is hosting.

The domain pinning already means a stranger cannot use your key from their own site: it only answers on origins you have verified. Archiving is the stronger version, for when you would rather the key simply do nothing at all.

So the loop is: build the demo site, record it, archive it. If you need the same demo again next month, restore it, and everything is where you left it.

Archiving is on the site's Settings tab, at the bottom. It asks you to type the site's name, because it takes a live assistant off every page it is on.

Restoring is on the sites list, under Archived. One button, and the key works again immediately.

Both are worth knowing before you archive something you will definitely want back.

• Your plan's site limit. An archived site does not count against it, which is the point, so if you created another site in the meantime the slot may be taken. Archive or remove that one first.
• A domain somebody else has claimed. An archived site releases its verified domains, so another site can take them. If that has happened, the restore is refused and names the domain and the site holding it, rather than quietly bringing your site back without the domain it needs to answer on.