Your deployment and its receipts

Your Atlas runs a specific release, identified by the digest of its files. The status page shows which release is serving you and when it changed.

A release changes only through a verified switch: the new files are checked against their manifest, staged beside the current release, and tested before a single byte is served. If the tests after the switch fail, the previous release is restored automatically. Each switch leaves a receipt — what was served before, what is served now, who fired it, when — and receipts cannot be edited.

Configuration changes that affect you are announced three working days ahead, except genuine security emergencies, which are explained afterwards.