---
title: "Academy Article"
canonical_url: "https://academy.laioutr.com/en/artikel/compare-and-roll-back-deployments"
locale: en
meta:
  "og:title": "Academy Article"
---

[Go to home](https://academy.laioutr.com/en)

- [Hosting and operations](https://academy.laioutr.com/en/bereiche/hosting-and-operations)

- [Deployment](https://academy.laioutr.com/en/leitfaeden/deployment)

- [Compare and roll back deployments](https://academy.laioutr.com/en/artikel/compare-and-roll-back-deployments)

# Compare and roll back deployments

Every deployment has its own address, so two versions can be compared side by side. A rollback puts an already built earlier production deployment live again within seconds, without a new build.

## Before you start

<dl>

<dt>Plan</dt>
<dd>Laioutr Cloud</dd>

<dt>Role</dt>
<dd>Access to the project in Cockpit with permission to deploy</dd>

<dt>Duration</dt>
<dd>5 min</dd></dl>

### Prerequisites

- At least one replaced production deployment from the last 24 hours

Last reviewed on October 15, 2026

When something does not work as expected after a deployment, a **rollback** returns production to the previous state. Laioutr puts the already built image of an earlier deployment live again and builds nothing. This takes seconds and depends neither on package sources nor on build time.

For a rollback without a rebuild, Laioutr keeps the last two replaced production deployments for 24 hours. Older states can only be produced with a new deployment. Rotating the project's content preview token withdraws these replaced deployments immediately.

For comparison, every deployment has its own address under `laioutr.app`. The current and an earlier version can therefore be opened side by side, together with status, duration and build log from the detail view.

A rollback swaps the delivered build with its app versions and built-in configuration. It is not versioning of individual content: CMS entries and media belong to the project and stay unchanged.

## Step by step

1. 1 ### Step 1: Filter production deployments Open **Deployments** and select the production environment in the filter. The running deployment carries the **Current** badge.
2. 2 ### Step 2: Open two versions Open the detail views of the current and the previous deployment and compare status, duration, provider and who triggered them.
3. 3 ### Step 3: Compare side by side Open the URLs of both deployments in two browser windows and compare the affected pages. The build log shows what went differently in the newer build.
4. 4 ### Step 4: Roll back Trigger the rollback on the earlier deployment. Laioutr makes its built image the current production deployment again.
5. 5 ### Step 5: Fix the cause Fix the error in the newer version and then start a new deployment.

## Check the result

In the overview, the earlier deployment carries the Current badge and the live domain serves its version. Opening the previously broken pages confirms it.

## Frequently asked questions

How far back can a rollback go?

Without a rebuild, to the last two replaced production deployments, each for 24 hours. Older states need a new deployment.

Does a rollback also restore content?

No. CMS entries and media belong to the project and are managed separately. A rollback swaps the delivered build, not individual content versions.

Why does a deployment address show a password page?

Deployment addresses are protected by Laioutr Cloud password protection by default. The version is reachable with the project password.

## Related

- [Start and check a deployment](https://academy.laioutr.com/en/artikel/start-and-check-a-deployment)5 min

  A deployment rebuilds the storefront of an environment and puts changes to apps, versions and configuration live. It is started in Cockpit under Deployments with Deploy; the status and build log show whether it worked.
- [Understanding the main, dev and stage environments](https://academy.laioutr.com/en/artikel/understanding-main-dev-and-stage-environments)5 min

  Every project starts with the main environment, which is the live storefront. Further environments such as stage or dev run beside it as separate copies with their own address, pages, apps and deployments until their work is promoted to main.
- [Read storefront logs](https://academy.laioutr.com/en/artikel/read-storefront-logs)6 min

  Under Logs, Cockpit shows what the storefront of each environment on Laioutr Cloud writes, plus an access log. Each line's level comes from the console method that was called, and a trace finds all lines of one request.
- [Password-protect the storefront until launch](https://academy.laioutr.com/en/artikel/password-protect-the-storefront-until-launch)5 min

  Laioutr Cloud password protection puts a password page in front of individual storefront hostnames. Previews are protected by default, production and custom domains are switched on one by one, and bypass secrets let tests and Studio through.

## Learn it in a lesson

- [Check the deployment status](https://academy.laioutr.com/en/lektionen/foundations-deployment-status)7 min
- [Environments and deployment](https://academy.laioutr.com/en/lektionen/developer-environments-and-deployment)12 min
- [Start and check a deployment](https://academy.laioutr.com/en/lektionen/go-live-start-and-check-a-deployment)7 min

## [Deployment](https://academy.laioutr.com/en/leitfaeden/deployment)

Search this guide

1. [Understanding the main, dev and stage environments](https://academy.laioutr.com/en/artikel/understanding-main-dev-and-stage-environments)5 min
2. [Start and check a deployment](https://academy.laioutr.com/en/artikel/start-and-check-a-deployment)5 min
3. [Compare and roll back deployments](https://academy.laioutr.com/en/artikel/compare-and-roll-back-deployments)5 min
4. [Read storefront logs](https://academy.laioutr.com/en/artikel/read-storefront-logs)6 min
5. [Bring Your Own Server: host the storefront in-house](https://academy.laioutr.com/en/artikel/bring-your-own-server-host-the-storefront-in-house)7 min In preparation

## Structured Data

```json
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@id": "https://academy.laioutr.com/#website",
      "@type": "WebSite",
      "inLanguage": "en",
      "name": "Default",
      "url": "https://academy.laioutr.com/",
      "translationOfWork": {
        "@id": "https://academy.laioutr.com/#website"
      }
    },
    {
      "@id": "https://academy.laioutr.com/en/artikel/compare-and-roll-back-deployments#webpage",
      "name": "Academy Article",
      "url": "https://academy.laioutr.com/en/artikel/compare-and-roll-back-deployments",
      "@type": [
        "WebPage",
        "FAQPage"
      ],
      "breadcrumb": {
        "@id": "https://academy.laioutr.com/en/artikel/compare-and-roll-back-deployments#breadcrumb"
      },
      "isPartOf": {
        "@id": "https://academy.laioutr.com/#website"
      },
      "mainEntity": [
        {
          "@id": "https://academy.laioutr.com/en/artikel/compare-and-roll-back-deployments#/schema/question/1"
        },
        {
          "@id": "https://academy.laioutr.com/en/artikel/compare-and-roll-back-deployments#/schema/question/2"
        },
        {
          "@id": "https://academy.laioutr.com/en/artikel/compare-and-roll-back-deployments#/schema/question/3"
        }
      ],
      "potentialAction": [
        {
          "@type": "ReadAction",
          "target": [
            "https://academy.laioutr.com/en/artikel/compare-and-roll-back-deployments"
          ]
        }
      ]
    },
    {
      "@id": "https://academy.laioutr.com/en/artikel/compare-and-roll-back-deployments#breadcrumb",
      "@type": "BreadcrumbList",
      "itemListElement": [
        {
          "@type": "ListItem",
          "name": "Home",
          "item": "https://academy.laioutr.com/en",
          "position": 1
        },
        {
          "@type": "ListItem",
          "name": "Hosting and operations",
          "item": "https://academy.laioutr.com/en/bereiche/hosting-and-operations",
          "position": 2
        },
        {
          "@type": "ListItem",
          "name": "Deployment",
          "item": "https://academy.laioutr.com/en/leitfaeden/deployment",
          "position": 3
        },
        {
          "@type": "ListItem",
          "name": "Compare and roll back deployments",
          "item": "https://academy.laioutr.com/en/artikel/compare-and-roll-back-deployments",
          "position": 4
        }
      ]
    },
    {
      "@id": "https://academy.laioutr.com/en/artikel/compare-and-roll-back-deployments#/schema/question/1",
      "@type": "Question",
      "inLanguage": "en",
      "name": "How far back can a rollback go?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>Without a rebuild, to the last two replaced production deployments, each for 24 hours. Older states need a new deployment.</p>"
      }
    },
    {
      "@id": "https://academy.laioutr.com/en/artikel/compare-and-roll-back-deployments#/schema/question/2",
      "@type": "Question",
      "inLanguage": "en",
      "name": "Does a rollback also restore content?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>No. CMS entries and media belong to the project and are managed separately. A rollback swaps the delivered build, not individual content versions.</p>"
      }
    },
    {
      "@id": "https://academy.laioutr.com/en/artikel/compare-and-roll-back-deployments#/schema/question/3",
      "@type": "Question",
      "inLanguage": "en",
      "name": "Why does a deployment address show a password page?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "<p>Deployment addresses are protected by Laioutr Cloud password protection by default. The version is reachable with the project password.</p>"
      }
    }
  ]
}
```