---
name: deploy-to-render-checklist
description: "A pre-launch checklist for a Render service covering service type, build and start commands, health checks and environment, so the first deploy goes green. Use when an app is being put on Render for the first time and its service type, commands, health check and environment need confirming. Do not use for comparing platforms or tuning application performance. Related topics: devops, coding."
---

# Deploy to Render Checklist

A pre-launch checklist for a Render service covering service type, build and start commands, health checks and environment, so the first deploy goes green.

## When to use

Use this skill when an app is being put on Render for the first time and its service type, commands, health check and environment need confirming. Do not use it for comparing platforms or tuning application performance.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. Confirm the service type matches the app and that the server binds to the PORT variable on all interfaces.
3. Verify build and start commands run from a clean checkout and keep installation out of the start step.
4. Define a lightweight health check path and describe what it must verify.
5. Set out database connection, backup and migration handling so concurrent instances cannot collide.
6. List environment names and platform caveats, then give a first-deploy test plan with a go or no-go line.

## Inputs

- **App description** (longer free text)
- **Service type** (choose one: Web service, Static site, Background worker, Cron job, Private service)
- **Build and start commands** (free text, e.g. "Both as run locally")
- **Health check path** (free text, e.g. "Route that returns 200 when healthy or none yet")
- **Databases or caches** (choose any: Postgres, Key Value store, Disk, None)
- **Environment variable names** (longer free text)

## Output

A checklist covering service, commands, health check, data and environment, with a first-deploy test plan and a go or no-go line.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### Deploy to Render Checklist

Prepare this app for a Render deploy.

- App description: {{App description}}
- Service type: {{Service type}}
- Build and start commands: {{Build and start commands}}
- Health check path: {{Health check path}}
- Databases or caches: {{Databases or caches}}
- Environment variable names: {{Environment variable names}}

Check in this order. Service: confirm the type matches how the app is used, and that a web service listens on the port Render provides via the PORT variable on 0.0.0.0, not localhost. Commands: build should install and compile, start should only run, and both must work from a clean checkout. Health: define a lightweight endpoint that checks dependencies without heavy queries, and set it so Render only routes traffic to ready instances. Data: use the internal connection string for databases in the same region, enable backups, and never run migrations inside the start command of several instances at once. Environment: list names with a note on which need to be synced from the dashboard, and flag free-tier sleep and cold start behaviour. Close with a first-deploy test plan and a go or no-go line.

## Pitfalls

- Binding to localhost, so the service builds fine and then never receives traffic.
- Running database migrations in the start command on several instances, which races and corrupts the schema.
- Choosing a free instance for something that needs to answer instantly, then blaming the app for cold starts.