Unpublish & version rollback

Take a site offline

Published something you're not ready to show? The publish dialog has an unpublish action (with an inline confirmation — it's deliberate, not one accidental click). Unpublishing takes the live site down for real: the URL stops serving. Your project, chat history, versions, and working files are untouched, and you can publish again anytime.

If a publish is currently running, unpublish waits its turn — you'll get a clear message to let the deploy finish first, rather than a half-torn-down site.

Every build is a version

The version history panel lists every completed build with its diff stats — files changed, lines added and removed — plus timestamps. Bookmark the versions you might want back ("the design the client approved").

Two distinct actions, for two distinct needs:

• Restore rewinds your working project to that version. The preview reloads on that state and you keep building from there.
• Publish this version deploys that version's exact file set to your live URL — without changing your working files at all. Shipped a bad change on Friday evening? Put Thursday's version live, then fix at leisure.

Honesty note

Versions are backed by durable snapshots stored independently of the build sandbox. Very old versions from before a project's snapshot coverage may no longer be restorable once the sandbox is recycled — in that case opix tells you so explicitly instead of silently restoring something wrong.