Back up and restore

Backups capture a site’s persistent volume plus a database dump as a single compressed archive you can restore later.

Take a backup

From the panel, open the site’s Backups tab and create one — the volume and a database dump are compressed into a single archive.

The same is available headlessly through the API/CLI as part of your site’s lifecycle commands.

Restore

Pick a backup and restore it. The site is stopped, the volume and database are replaced from the archive, and the site is brought back up.

Caution

Restoring overwrites the current volume and database for that site. Take a fresh backup first if you might need the current state.

What’s included

• The site’s persistent volume(s).
• A dump of the site’s database (Postgres or MySQL).

Good practice

• Back up before a risky deploy or a pre_deploy migration hook.
• Back up before a topology migration if it touches stateful nodes.
• Keep archives off the host for disaster recovery.