White-label domain
A custom domain served by a SaaS in a way that completely hides the SaaS's name from end-users. The certificate, the HTTP headers, and the UI all read as the customer's brand.
White-label means the underlying product is invisible. A SaaS that supports white-label domains lets a customer use their own domain in a way where the end-user has no signal that the SaaS exists.
What "white-label" means at each layer
| Layer | Not white-label | White-label |
|---|---|---|
| URL | acme.yourapp.com | hello.acme.com |
| TLS cert | Issued for yourapp.com | Issued for acme.com |
HTML <title> | "Acme on YourApp" | "Acme" |
| Powered-by footer | "Built with YourApp" | (removed) |
Email From: | acme@yourapp.com | hello@acme.com |
A custom-domain API gets you the first two for free. The rest is your responsibility (theming, footer toggles, configurable email sender).
Why customers ask for it
Three reasons:
- They have their own brand and want to project it.
- Their customers are confused or skeptical when a third-party brand appears.
- Legal or procurement at their company requires it (especially in regulated industries).
White-label is most often a paid-tier feature in SaaS pricing, but the underlying domain pipeline is the same as for any custom domain. The differentiation is in your UI toggles, not the infrastructure.