What happens when you click Publish

Publishing should feel like nothing. One click, a few seconds, and your changes are live. Behind that click is a sequence designed so that a mistake never reaches your visitors — and so that, if something does go wrong, you're one click away from the previous version.

1. Validate

We check the whole configuration before anything moves: required fields, component schemas, domain status and connected integrations. If a booking page depends on a calendar that's been disconnected, you'll hear about it now — not from a customer.

2. Snapshot

We create a new, immutable deployment version. The previous version isn't overwritten; it's preserved exactly as it was, ready to restore.

3. Render

Your website is the result of a simple equation: template version plus your configuration. The renderer that builds your live site is the same one that powers the preview, so what you approved is exactly what ships.

4. Go live

Your domain switches to the new version in a single step. There's no in-between state where half the pages are new and half are old. Cached pages are refreshed at the edge so visitors everywhere see the update.

5. Watch, and roll back if needed

Every deployment is monitored. If you change your mind — or something looks off — pick any earlier version and restore it. Restoring creates a new version rather than erasing history, so you never lose the path that got you here.

Why one shared platform

All Micronuage sites run on the same managed runtime. We don't maintain thousands of separate codebases, which is exactly why improvements to speed and security reach every published site at once — including yours, without you lifting a finger.