Maintenance mode and suspending

You can take a web service offline in two ways. Maintenance mode keeps it running and shows visitors a maintenance page. Suspending stops it.

Maintenance mode

While maintenance mode is on, every request gets the maintenance page, on the service's appentic.app address and on its custom domains.

Use it while you migrate data or fix something and don't want visitors using the app, but still want it running, for example to use the shell.

1. Open the service's Settings.
2. Under Maintenance, turn on Maintenance mode.

It saves straight away and applies within a few seconds. While it's on, the service shows Maintenance instead of Live, and so does its project on the dashboard. Turn the toggle off to let visitors back in.

The service keeps running and keeps its memory, and its fee continues.

The Back-soon page toggle in the same section is different. It's a project setting that shows the maintenance page only while an app can't respond, for example during a restart. See Maintenance page.

Suspend a web service

Suspending stops the service and takes it offline. Its settings and deploys are kept.

1. Open the service's Settings.
2. In the Danger Zone, click Suspend service and confirm.

While a web service is suspended:

• it doesn't run and doesn't answer requests
• pushes to its branch don't deploy it, and you can't deploy, restart or roll it back
• its service fee pauses
• it still holds its memory on the machine, so it always fits when you resume it

A deploy that was queued or building when you suspended the service is cancelled.

Resume a web service

In the service's Settings, click Resume service in the Danger Zone and confirm. The service comes back online with the version it had.

Take a whole machine offline

Stopping a machine takes every service on it offline at once. A stopped machine is still billed, and so are its services.