Start here
Production launch checklist
A practical gate before connecting customer traffic.
7 minute read · Updated September 2026Identity and access
- Verify every human account.
- Enable authenticator-based two-factor authentication for privileged members.
- Use the least-privileged organization role.
- Create separate application database roles instead of sharing owner credentials.
Data safety
- Confirm automated backups are healthy.
- Create and validate a restore point.
- Run a recovery drill and record the result.
- Test export and deletion workflows before customer launch.
Application readiness
- Require TLS in the connection string.
- Use connection pooling and bounded retry behavior.
- Run migrations with a deployment identity.
- Set storage, connection, and budget alerts.
- Subscribe the operations team to status and incident notifications.
Use the readiness dashboard
Console → Launch readiness evaluates live configuration and operational evidence. A green interface is not a substitute for a real restore, failover, and load exercise; attach those results to your release checklist.
Do not launch on assumptions
A backup is only proven when it has been restored and the restored data has been checked.
Was this guide useful?
Get helpIf anything is unclear or incorrect, tell the support team.