Go live

Everything starts in Development. Going live publishes one release, a signed snapshot of your approved content, forms, chatbots and search settings, to Production. Your live website then reads only that release.

Before you start

• Your website is connected and Studio shows it In sync with the active contract (Connect a Next.js website).
• Every page you want live is published in Development and checked with Preview on website.
• You know who approves releases: an organization admin, a site admin or a reviewer/publisher.
• You have your Production domain and access to its DNS.

Go live in six steps

1. Verify your domain. In Studio open Security and the card Domain verification. Add your Production domain, create the DNS TXT record it shows, then click Check again. Production can only use a verified domain.

2. Build a release. Open Releases, click New release, give it a Name and an optional Note for the publisher, review What changes in Production and click Build release.

3. Check the gates. Atlas checks that your website build is in sync with the contract, that nothing has publish problems, that the website is healthy and that a backup ran in the last 24 hours. All gates pass means you can continue.

4. Approve and publish. A person with approval rights clicks Approve and publish. Atlas may ask for a second confirmation on their phone. The release becomes the Live release.

5. Turn on Production. A site admin clicks Turn on Production. The button stays disabled until a live release exists.

6. Point your live deployment at Production. Under Releases, create a Production delivery token (New token, then Create token). In your live hosting, set the Production environment id and that token, then deploy as you normally do.

Check the live website

• Pages load from Atlas and look the same as in Development.
• A test enquiry through a form arrives in Forms & leads → Leads → Live website.
• Lead emails arrive. To stop them without touching forms, set Live website to “emails paused” under Integrations → Email.
• The chatbot answers on the live site, if you use one.
• robots.txt, sitemap.xml and llms.txt are served from your domain (Search and AI answers).

After go-live

• Publishing changes: edit and publish in Development, then build and approve a new release. Nothing reaches the live site until a release is approved.
• Rolling back: in Releases, roll back to an earlier release. This needs the rollback permission and is recorded in the audit log.
• Turning Production off: Turn off Production stops the live website from reading content, forms and chatbots. Keep your website’s built-in fallback in place for this case.

Development and ProductionWhat each environment serves and who can approve.Preview, publish and roll backDrafts, revisions and how changes reach your website.