# Connect a Vercel domain

> Connect a Vercel domain with one click.

Source: https://docs.customdomain.ai/docs/providers/vercel

**Setup type: One-click (sign-in).** You install the CustomDomain™ integration on your Vercel team in a popup. No records to copy; no password is shared with the app.

Vercel's sign-in is the CustomDomain™ integration: install it on the Vercel team that owns the domain, and the records are written for you. A Vercel access token works too. Vercel is also on the Domain Connect list, but it serves none of our one-click templates yet, so one-click setup is not offered.

## What you'll need

* A domain whose DNS is managed at Vercel.
* Access to your app's CustomDomain™ dashboard (it shows the exact target for your account).

## The records

CustomDomain™ gives you the authoritative records for **your** account in the dashboard, typically a `CNAME` (or apex `A`/`ALIAS`) pointing your domain at the edge. Use the values shown there; the shape is always the same, the target is per-account. There is no separate ownership TXT to add on this path: control is proven by the rail itself, or by the records appearing in your own authoritative DNS. See [Setup types](/docs/concepts/ownership-and-setup-types#control-is-proven-by-the-rail).

## Setting it up on Vercel

1. Enter the domain in the connect flow (the console, or the widget inside the product you're connecting to). It detects Vercel and offers **Install CustomDomain™ on Vercel**.
2. A Vercel window opens. Install the integration on the team that owns the domain.
3. The records apply automatically; you're returned to the app, which usually verifies them within seconds and goes live.

## Vercel specifics

* The integration's token reaches only the team that installed it, and it drives Vercel's DNS API. You can remove the integration in Vercel once the domain is connected.
* If you deploy the app itself on Vercel, connecting a customer's domain is still a DNS operation at wherever that customer's domain resolves, not a Vercel project setting.
* Vercel's Domain Connect served none of our 18 templates when checked on 2026-09-28. Its one-click setup also requires our return link, which every template we publish now carries, so it can be offered once Vercel onboards them.

## How you know it worked

CustomDomain™ polls public DNS and issues the TLS certificate automatically. When the dashboard shows the domain **live**, HTTPS is serving. Drift monitoring then watches the records so a later change at the provider doesn't silently break the domain.

## FAQ

### I host on Vercel, is this different from adding a domain to my Vercel project?

Yes. This connects an end-user's own domain to your app with automatic HTTPS at the edge, wherever that domain's DNS is hosted. Adding a domain to your Vercel project only covers domains you control.

## Related

* [All DNS providers](/docs/providers), the full connection catalog.
* [How custom domains work](/docs/getting-started/overview)
