Skip to main content
Use this runbook to coordinate the final admin-side checks before opening a new deployment to external users.

Scope of this runbook

This runbook assumes:
  • core implementation work is already complete
  • provider credentials are available or about to be applied
  • operators are validating readiness, not designing features from scratch

1. Freeze scope

Before the release window:
  • stop adding non-critical features
  • identify the single payment provider or provider set you will support at launch
  • identify the social login providers you will support at launch
  • define who owns production credentials and rollback decisions

2. Finalize admin configuration

In /admin, review:
  • products and plans
  • one-time products if enabled
  • discounts
  • payment providers
  • email providers
  • OAuth providers
  • verification providers
  • general settings
  • legal pages settings
  • invoice settings
  • referral settings
  • Open Graph settings

3. Finalize public content

Verify:
  • homepage copy and links
  • FAQ content
  • blog content if used for launch
  • roadmap visibility
  • announcements
  • terms of service
  • privacy policy

4. Validate critical user flows

Test with a production-like environment:
  • registration
  • email verification
  • social login
  • 2FA if enabled
  • subscription checkout
  • one-time purchase checkout
  • payment webhook delivery
  • invoice generation
  • dashboard access
  • admin access

5. Validate infrastructure

  • database backups are configured
  • Redis is running if queues depend on it
  • Horizon or queue workers are running
  • mail delivery is verified
  • HTTPS is enforced
  • public callback URLs are correct

6. Validate observability

  • logs are accessible
  • failed jobs are monitored
  • payment failures can be diagnosed
  • support staff know where to inspect users, subscriptions, orders, and transactions

7. Go-live decision

Only publish when:
  • launch-critical flows all pass
  • provider credentials are confirmed
  • legal content is ready
  • no placeholder branding remains
  • owners agree on support coverage for the first launch window
Last modified on March 30, 2026