Production Checklist

Use this checklist before pointing real users at your Atlasflow project. Each item links to the guide with full details.

# Application

• Your app listens on port 3000 and binds to 0.0.0.0, not 127.0.0.1. See Container requirements.
• GET / returns a 2xx status quickly and doesn't redirect to a login page. This is the health check path.
• Your app starts fast enough to pass health checks. Defer heavy initialization where possible.
• Your Dockerfile (or auto-detected build) produces a small, production-only image. See Builds.

# Configuration

• Runtime environment variables (database URLs, API keys) are set on the project. See Environment variables.
• Build environment variables (private registry tokens, build flags) are set separately from runtime values.
• The default branch is the branch you intend to deploy from. See Configuration.
• The root directory and Dockerfile path point at the right app if you're in a monorepo.

# Domains and routing

• A custom domain is added and verified.
• DNS records (A or CNAME plus the TXT ownership record) are in place. See DNS configuration.
• Any www to apex (or apex to www) redirect is configured.

# Observability

• You know where to find build logs and runtime logs when something breaks.
• You've reviewed CPU and memory metrics to right-size your workload.

# Billing

• Your workspace has an active subscription. Deployments require one.
• You understand the usage-based pricing and how included credits apply.

# Reliability

• For higher availability, consider the Team plan, which runs two deployment replicas and supports multi-region deployments.

# Next steps

• Troubleshooting: fix common build and runtime issues.
• FAQ: quick answers to common questions.