A non-blocking provisioning step that attaches <slug>.<root> to the deployment project. The platform's wildcard DNS already routes every subdomain to the host; this step attaches the specific name so a certificate is issued for it. It is idempotent on re-run and never blocks the rest of provisioning.
Also called: subdomain provisioning · SSL certificate setup · no DNS work
- 1ensureDomain() attaches the subdomain; if the host says it already exists, verification confirms it's on this project and that counts as success.
- 2A missing root-domain setting or API token records an explicit skip note naming what to set.
- 3The step is excluded from the critical gate, so a transient host failure never blocks the account going live.
- 4The result note distinguishes 'registered + verified' from 'registered, certificate issuing'.
The comment states both the mechanism and why it isn't critical: 'The platform's wildcard *.<root> Cloudflare CNAME already routes every subdomain to Vercel; this attaches THIS subdomain to the project so Vercel issues its cert.' And: 'Non-critical (NOT in the provisioned gate): a missing VERCEL_API_TOKEN or a transient failure never blocks provisioning — the owner can add it in Vercel and retry.' Making a third-party API call part of the critical path would mean an outage at the host blocks a paying customer's account from existing.
- Manual DNS and certificate setup per customer doesn't scale and is easy to forget.
- A third-party API failure shouldn't block an account from going live.
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →