---
title: Production Checklist
description: What to confirm before sending production traffic to your Atlasflow deployment.
order: 1
---

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](/docs/guides/container-requirements.md).
- [ ] `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](/docs/concepts/builds.md).

## Configuration

- [ ] **Runtime** environment variables (database URLs, API keys) are set on the project. See [Environment variables](/docs/guides/environment-variables.md).
- [ ] **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](/docs/guides/configuration.md).
- [ ] The **root directory** and **Dockerfile path** point at the right app if you're in a [monorepo](/docs/guides/monorepos.md).

## Domains and routing

- [ ] A [custom domain](/docs/networking/custom-domains.md) is added and verified.
- [ ] DNS records (A or CNAME plus the TXT ownership record) are in place. See [DNS configuration](/docs/networking/dns-configuration.md).
- [ ] Any `www` to apex (or apex to `www`) [redirect](/docs/networking/redirects.md) is configured.

## Observability

- [ ] You know where to find [build logs](/docs/observability/build-logs.md) and [runtime logs](/docs/observability/runtime-logs.md) when something breaks.
- [ ] You've reviewed [CPU and memory metrics](/docs/observability/metrics.md) to right-size your workload.

## Billing

- [ ] Your workspace has an [active subscription](/docs/billing/plans.md). Deployments require one.
- [ ] You understand the [usage-based pricing](/docs/billing/usage-and-credits.md) and how included credits apply.

## Reliability

- [ ] For higher availability, consider the **Team** plan, which runs [two deployment replicas](/docs/billing/plans.md) and supports [multi-region](/docs/networking/regions.md) deployments.

## Next steps

- [Troubleshooting](/docs/resources/troubleshooting.md): fix common build and runtime issues.
- [FAQ](/docs/resources/faq.md): quick answers to common questions.