Operate your app: logs, rollbacks, backups, domains

After the first deploy, you run your app from the dashboard or the ox CLI. Each page below covers one job, such as reading logs, rolling back a bad release, restoring a backup, changing a variable, adding a domain, or trying a change on staging first.

Running an app

Each page shows how to do the job in the dashboard and with the CLI, what you will see, and what to do when it does not work.

• LogsView your app's logs live in the dashboard or with ox logs: filter by severity and process, search with a regex, pick a time range, and download them.
• Roll backRoll back a deployment to a kept release without a rebuild. The live release serves until the old one passes its health check. What happens to your data.
• Backups and restoreox backs up your app's databases every day with nothing to turn on. Back up now, keep copies in your S3 bucket, download a backup, and restore it safely.
• Backups and leavingWhere your backups live, what is not backed up, how much data you can lose, what pauses when ox is down, and how to leave ox with your data.
• VariablesSet environment variables and secrets in the dashboard or with ox vars, reference one in another, see the keys ox provides and hides, restore old ones.
• Staging and previewsTurn on a preview deployment per branch and a staging copy, each with its own database, on your own server. Limits, passwords and promote to production.
• ServicesSee every service your app uses on one card: status, size, backups and its connection URL, then browse Postgres, Redis, NATS or ClickHouse data, read-only.
• Domains and HTTPSAdd a custom domain to your app: create the A record, add the name in ox, and Caddy gets and renews the HTTPS certificate. What each domain status means.
• Tested deploysTurn on tested deploys: an AI tester uses each pull request's preview like a user, signs in, writes checks and holds production while one is red.

When something fails, Troubleshooting lists the messages ox prints and their fixes.