The Difference Between a Vercel Subdomain and a Real Home

AI with AI Labs had been sitting on a Vercel subdomain for a while. The homepage worked. The theme toggle worked. The Cowork page worked. Everything about it was functional. It just wasn't home yet.

A subdomain is a fine place to build. It's not a place to actually launch from. So I closed that gap: added aiwithailabs.com and www.aiwithailabs.com inside Vercel, then went over to Northwest Registered Agent, where the domain lives, to update the DNS records.

I want to name the exact sentence I kept in my head while doing this, because it's the part worth repeating to anyone about to do the same thing: one wrong DNS record and you can knock out your own email while chasing a website launch. That's not a hypothetical. It's the actual risk sitting in the same settings panel as the change you're trying to make, one field away from the one you meant to touch.

Once the records verified, I updated the environment variable pointing at the domain and redeployed under the real one instead of the Vercel default.

While I was already in the DNS and deployment weeds, I documented the design system properly, since it hadn't been written down in one place yet. Violet for primary actions. Lime and coral for the free and paid tags. Electric blue for links. A hero gradient running orange to pink to violet. Small thing to do while already in there, and it meant the next build session had a real reference instead of me eyeballing old screenshots for the right shade of purple.

The DNS setup, step by step

This pairs directly with the DNS story from getting the site live in the first place: same category of risk, same kind of care required, just one step further down the path from "it works" to "it's actually mine."

If you're still running your own project off a platform subdomain, here's the question worth sitting with: what is still living on localhost, or on someone else's URL, that deserves its own home?