L28 · Publish · 4 min

Your own domain

In one sentence

Every Vercel project starts with a free .vercel.app address, and whenever you're ready you can attach your own custom domain—like myproject.app or myproject.com—by pointing its DNS records to Vercel, which issues your HTTPS security certificate automatically and redirects www.

Think of it like this

Think of the internet's phone book. Your app's building on Vercel stays in the exact same place; buying a custom domain simply registers a short, memorable name in the directory and forwards anyone who dials it straight to your front door.

How it works

The free <project-name>.vercel.app address DefinitionVercelThe service that turns your code on GitHub into a live site, with a Preview for every change.Open in the glossary → gives your app is a real, permanent DefinitionProductionThe live version of your app, the one everyone sees. It comes from `main`.Open in the glossary → link—you never have to buy a DefinitiondomainA web address people can type, like `agenticmakers.app`.Open in the glossary → just to learn or to share your project with friends. When you want a shorter, branded address (such as .app or .com), you register it for an annual fee through a domain registrar (like Cloudflare Registrar, Porkbun, Namecheap, or directly inside Vercel).

To connect a domain you bought elsewhere, open your project on Vercel → Settings → Domains, type your domain, and Vercel shows you two lines to copy into your registrar's DNS settings (the internet's address book): an A record for the root domain (example.com) and a CNAME record for www.example.com. Set one as primary and let Vercel redirect the other with a 301 permanent redirect so visitors and search engines always land on one canonical address.

Once the DNS records point to Vercel (which usually takes a few minutes), Vercel automatically issues and renews your HTTPS certificate—the encrypted connection every browser expects. Note that .app domains require HTTPS by default, which Vercel handles for you without any extra setup.

If your app uses Better Auth for logins or sets canonical links in code, remember to update your Production BETTER_AUTH_URL Definitionenvironment variableA named slot, like `TOKENTIDE_API_KEY`, that holds a setting or secret outside your code.Open in the glossary → in Vercel to your new https://... domain and trigger a fresh DefinitiondeployPutting a version of your app online.Open in the glossary → so sign-in cookies and redirects match the new address.

1 · Domain registrarDNS records (A & CNAME)Points your root domain and www to Vercel's servers in the internet address book.
2 · Vercel DomainsAutomatic HTTPS + 301Issues your SSL certificate automatically and redirects www to your primary address.
3 · App settingsBETTER_AUTH_URL updatedProduction environment variable updated and redeployed so logins match the new domain.
FIG. 1 · Point DNS to Vercel, let Vercel issue HTTPS and redirect www, then update BETTER_AUTH_URL if your app has logins.

What it looks like in your project

Buying a domain and editing DNS records happen in your browser, so your agent guides you click by click and waits for your “done”. Then your agent checks which environment variables or metadata URLs in your project reference the old .vercel.app address and helps you update them cleanly.

Copy for your agent

I want to connect my custom domain to our Vercel project. List every place in our code or Vercel environment variables (like BETTER_AUTH_URL) that needs the new domain, and guide me through the Vercel Domains and DNS steps one by one.

Quick check · 1 question

After connecting a custom domain to an app that has user logins, what setting in Vercel must you update so sign-in keeps working?

Go deeper

Where this fits on the PathPublish: your first live app

Last reviewed Nov 8, 2026