Building many sites at once

Sites → Bulk deploy. One recipe, many domains.

What you give it

A blueprint or a stack, the plan the sites are billed against, and the list of domains. The list can be pasted, so a spreadsheet column is a valid input.

What happens

The job runs in the background — you can close the tab. Each site is built independently, so one failure does not stop the rest, and each one gets its own result you can read afterwards.

When one fails

The job screen shows which site failed and why, in words rather than a stack trace. The usual causes are a domain that is not yet delegated to us and a plan that has run out of site allowance. Fix the cause and re-run just the failed ones — there is a control for that on the job, so you do not rebuild the successful ones.

What it counts against

Every site created counts against your plan's site allowance, immediately. If the list is longer than the allowance, the job tells you before it starts rather than half way through.

⚠️ Give it real domains. A bulk deploy against domains that do not resolve yet will build the sites correctly and leave every certificate pending, which looks like a failure and is not. Point the DNS first, or accept that the certificates arrive when it does.