Skip to main content
Reference

Backup & Restore

Back up control plane state and restore it, with a tested restore path.

Everything the control plane persists lives in its storage backend, so backing up the control plane means backing up that backend. The engine itself is stateless between restarts and needs no separate backup.

What you must be able to restore:

  • The storage backend. Actor state, namespaces, and runner configuration.
  • Your configuration. The config file or environment variables, including the admin token. Losing the admin token locks you out of the dashboard and the API.

By backend

Test the restore

A backup you have never restored is not a backup. Restore into a scratch environment on a schedule and confirm:

  1. The control plane starts and reports healthy on /health.
  2. The dashboard loads and your namespaces are present.
  3. A worker connects and appears under Runners.
  4. An actor created before the backup still resolves and reads its state.

Next steps