Go-Live Checklist

Content Freeze & Ingest

• Content freeze date set and communicated to all stakeholders
• All launch-day titles ingested, encoded, and QA'd
• Thumbnail and metadata complete for every published title
• Home page rails and featured content configured
• Geo restrictions validated per title

Technical Readiness

• Production environment deployed and stable
• CDN configured and tested under load
• DRM keys provisioned for all target platforms
• SSL certificates valid and auto-renewing
• Error pages (404, 500) configured
• Analytics event stream validated end-to-end

Payments & Entitlements

• Payment processor in live mode (not test mode)
• All pricing plans published and verified
• Entitlement checks confirmed across web, iOS, Android
• Trial period logic tested
• Cancellation flow tested end-to-end
• Receipt emails sending correctly

Rollout Sequencing by Device

• Web — launch first (fastest iteration cycle)
• iOS / Android — submitted and approved before launch date
• Smart TV / CTV — submitted with buffer for approval delays (budget 2–4 weeks)
• Phased rollout enabled on app stores where possible

Monitoring & Observability

• Uptime monitoring active (site + API endpoints)
• CDN error rate dashboard configured
• Playback error rate baseline set
• Payment failure rate alert configured
• On-call rota defined for launch week

Incident Runbook

• Incident severity levels defined (P1–P3)
• Escalation path documented (who gets paged and when)
• CDN / origin rollback procedure documented
• App store emergency update procedure documented
• Customer comms template ready (status page or email)

Rollback Plan

• Previous build artifacts retained and deployable
• Database rollback procedure tested
• Feature flags configured for high-risk features
• Rollback decision criteria defined (e.g. error rate thresholds)

Launch day rule: Your go-live is a rehearsed event, not a surprise. If you have not run a full dry-run of your monitoring and incident runbook, you are not ready to launch.