Run and operate
Open the admin console
What this is- Open
/adminand sign in with an admin account. - Read the account, site, and usage lists before changing anything.
- For a client, request
GET /v1/admin/usagewith the admin key and inspectworkers.
Take down a site
What this is- Read
GET /v1/admin/sitesand identify the site’s ID. - Confirm the site, then send
POST /v1/admin/sites/{id}/suspend. - To undo the takedown, send
POST /v1/admin/sites/{id}/restore.
Check server health
What this is- Request
GET /healthzand check for HTTP 200. - If it fails, read the server’s startup logs and check database connectivity.
- On your own server, run
simple-host migrate -statusto check pending migrations.
Prepare an installation
What this is- Open Setup and choose the installation type.
- Fill in the server addresses and settings.
- Download the generated configuration and follow its commands on your own server.
Run your own copy
What this is- Follow the installation instructions for your server.
- Set this install’s address and apply its database schema or migrations before starting it.
- Open
/healthz, sign in, and publish a test site. Use the settings reference when changing limits or providers.
Prepare storage retirement notices
The operator’s migrate-rules --list-recipients --out recipients.json
command writes private recipient lists and sends nothing. Add --legacy-log
with collected legacy_storage_call lines to include sites that call older
saved-data routes without storing rows. Recompute before each approved send.
File buckets are excluded; event-held resources are listed separately.
Leave STORAGE_SWITCH_AT empty until the notice date is approved. It accepts
an RFC3339 UTC instant and requires STORAGE_RULES=on. Set it in the Compose
environment or Helm storageSwitchAt value, then restart. During the notice
period successful SQLite/KV preset saves return a warning. Wording may be
changed without rebuilding through DATA_DIR/storage-notice.json.
See Storage and backups.