SaaS deployment checklist: staging, env vars and rollbacks

Deployment is part of the product. If only the agency can ship, the client does not truly own the system.

Environments

• Local with docker-compose or documented native setup.
• Staging on the same host pattern as production.
• Production with separate database and secrets.

Pre-launch checklist

1. Environment variables documented (.env.example).
2. Database migrations run in CI or documented script.
3. Health check endpoint monitored.
4. Error tracking (Sentry or similar) wired.
5. Backups enabled and restore tested once.
6. Domain, SSL and redirect from www.

Handover packet

Repo access, hosting login, DNS notes, runbook for deploy and rollback, and who to call when Stripe or email breaks.

Use this as a working checklist inside your team first. When the same steps repeat every week and spreadsheets start breaking, that is usually the moment to scope one workflow, one user group, one measurable outcome and a fixed handover plan as an owned system. See the relevant Standen service · More guides · SaaS ops audit.