Vanity domain

A vanity domain is a domain, or subdomain, chosen for branding rather than technical need, such as links.acme.com instead of a provider's default URL. In SaaS, the terms vanity domain, custom domain, branded domain, and personalized domain describe the same feature: serving your product on a customer's own name.

One feature, many names

SaaS vocabulary never settled on a single term for letting customers put your product on their own domain. Different corners of the industry picked different words, and they all describe the same capability.

Term	Where you hear it	Emphasis
Vanity domain	Link shorteners, email tools, older developer docs	Appearance. The domain exists for branding, not technical necessity.
Custom domain	Site builders, docs tools, most modern SaaS	Ownership. The customer connects a domain they control.
Branded domain, branded URL	Marketing and link management platforms	Recognition. Links carry the brand and earn more trust.
Personalized domain	Consumer facing product copy	Friendliness. Same mechanics, softer language.
White label domain	Agencies and resellers	Invisibility. The platform's name disappears entirely.

You will also see bring your own domain (BYOD), which describes the same idea from the customer's point of view.

Vanity domain versus custom domain

If there is a nuance, it is this: vanity domain historically leaned toward subdomains set up purely for looks, like go.acme.com fronting a link shortener, while custom domain became the general term for connecting any domain a customer owns, subdomain or apex. In practice the industry uses the terms interchangeably, and product teams should treat them as the same feature with the same requirements.

The split survives mostly in search behavior and documentation. Marketers search for branded links and vanity URLs, developers search for custom domains. If you write docs for your own product, pick one term, use it consistently, and mention the synonyms once so every audience finds the page.

What serving a vanity domain actually takes

Whatever you call it, the mechanics are identical. The customer's DNS must point at your platform, usually a CNAME for subdomains and address records for apex domains. Ownership has to be verified before any traffic is served. A TLS certificate must be issued for the exact hostname and renewed on schedule. And your edge has to route each hostname to the right tenant. This is the stack described in custom domains for SaaS.

Offering vanity domains in your product

For creator platforms and link tools, the vanity domain is often the moment a customer commits, because their audience now sees the customer's brand instead of yours. Custom Domain provides the feature as an embeddable widget or a REST API: the customer connects their domain in one click, records are configured automatically across 63 supported DNS and registrar providers, and the domain is typically live with TLS in about 30 seconds. See Custom Domain for creator tools for how this looks inside a creator product.