---
title: "Maintenance mode"
description: "Show visitors a page instead of the app, for planned work or a risky deploy."
canonical_url: "https://docs.lightdrop.cloud/guides/maintenance"
---
# Maintenance mode

> Show visitors a page instead of the app, for planned work or a risky deploy.

While an app is in maintenance, the runtime answers in its place: visitors get a page with a `503`
and `Retry-After`, so search engines keep the app listed and clients know when to try again. The
owner, members and admins still get the app, to check it before everyone else does.

```bash
wervt maintenance my-app on                # until you turn it off
wervt maintenance my-app on --for 30m      # ends by itself, also 2h or 1d
wervt maintenance my-app on --from 2026-12-01T22:00 --until 2026-12-01T23:30
wervt maintenance my-app off               # ends it, or cancels a planned one
wervt maintenance my-app                   # what's going on
```

Times without a zone are read in your machine's time zone. In the dashboard it's under
**Maintenance** in the app's settings, and in [MCP](https://docs.lightdrop.cloud/guides/mcp) `maintenance.get` and
`maintenance.update`.

A window ends on time without anything running: the runtime compares the clock on every request,
so a stopped control plane can't keep an app down.

## The page

Without any setup, visitors get a short page in their language (English or German) with the app's
name, and its logo and color from [`wervt.brand`](https://docs.lightdrop.cloud/api/module). With an end time, the page says when
the app is expected back, in the visitor's time zone. Texts stay when maintenance ends.

```bash
wervt maintenance my-app --title 'Back soon' --message 'New servers tonight.'
wervt maintenance my-app --color '#2f5bff'
wervt maintenance my-app --link https://status.example.com --link-label 'Status page'
wervt maintenance my-app --message ''      # back to the default text
```

The dashboard shows a preview while you type. On a planned window the page only appears once it
starts, so you can prepare it ahead.

## What it covers

<table>
<thead>
  <tr>
    <th>
      Request
    </th>
    
    <th>
      During maintenance
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      A page visit
    </td>
    
    <td>
      The page, <code>
        503
      </code>
    </td>
  </tr>
  
  <tr>
    <td>
      API calls (<code>
        /api/*
      </code>
      
      , <code>
        /mcp
      </code>
      
      , anything not HTML)
    </td>
    
    <td>
      <code>
        503
      </code>
      
       with <code>
        { error, maintenance: true, until }
      </code>
    </td>
  </tr>
  
  <tr>
    <td>
      Static files
    </td>
    
    <td>
      <code>
        503
      </code>
      
      , the app's files aren't served either
    </td>
  </tr>
  
  <tr>
    <td>
      Private apps, not signed in
    </td>
    
    <td>
      The login as usual: the page never shows to outsiders
    </td>
  </tr>
  
  <tr>
    <td>
      Owner, members and admins
    </td>
    
    <td>
      The app
    </td>
  </tr>
  
  <tr>
    <td>
      Tasks and boot checks
    </td>
    
    <td>
      Keep running, they don't come through the internet
    </td>
  </tr>
  
  <tr>
    <td>
      Previews
    </td>
    
    <td>
      Not affected: a preview has its own maintenance mode
    </td>
  </tr>
</tbody>
</table>

The page offers people who aren't signed in a link to the login, which is how the team gets past it
on a public app. For curl or Playwright, use [`wervt token`](https://docs.lightdrop.cloud/guides/deploys#tokens). People with
access who aren't on the team (the allow-list, invited people) get the page like anyone else.

Realtime connections that are already open stay open until they end: maintenance stops new requests.

The login app itself has no maintenance mode: it's how the team gets in.

## During a deploy

A deploy switches releases at once, so most don't need this. For one whose migration would break the
running release, keep visitors out until the new one runs:

```bash
wervt deploy --maintenance
```

The page shows once the bundle has passed its checks, from before the migrations until the deploy
ends, failed or not: a failed deploy leaves the old release running. If a deploy dies halfway, the
page goes away by itself after 15 minutes. Maintenance you turned on yourself isn't touched.


## Sitemap

See the full [sitemap](https://docs.lightdrop.cloud/sitemap.md) for all pages.
