About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
Direct answer: On a hosted ISV delivery model, customers and partners typically can change customer-visible brand surfaces—login page artwork, product name in headers, notification email templates, PDF letterheads, custom subdomains with valid TLS—and cannot realistically rebrand low-level platform chrome, mobile app store listings, shared multi-tenant footers, or underlying infrastructure names without engineering programmes you should price separately.
Why it matters
White-label promises win vertical markets: an accountant’s practice management appears to clients as the practice’s own portal. Overselling branding flexibility creates rework when the customer discovers the mobile app still shows your ISV name, error pages reveal the hoster’s domain, or API docs reference your public SaaS hostname.
Hosted delivery couples application, DNS, certificates and email authentication (SPF, DKIM). A brand change is a multi-owner mini-project, not a CSS tweak. Product managers need a brandable surface catalogue so sales stops inventing per-deal miracles.
How it works
Usually brandable (with work)
- Web UI: logo, colour palette, favicon, login background, optional white-label domain (
app.customer.com.auorcustomer.yourproduct.com.au). - Customer-facing emails: From name, reply-to, template HTML, embedded logos—provided you control sending infrastructure or delegate authenticated domains.
- Generated documents: invoices, reports, certificates—template engines per tenant.
- Help links: redirect to customer KB or cobranded support portal.
- Some API error messages and webhook user agents—low value but occasionally requested.
Usually partial or expensive
- Native mobile apps: store listing identity often stays ISV unless you ship separate binaries (flavour builds).
- Deep links and OAuth redirect URIs: each redirect URI you use must be registered on the application; custom hostnames are added to that registration subject to platform limits, not a separate concern from app identity.
- Third-party embedded widgets (maps, payments): vendor terms may require their badge.
- Browser tab titles on first load before tenant resolution—edge cases in multi-tenant routing.
Usually not brandable without platform change
- Shared multi-tenant URLs where path alone selects tenant (
vendor.com/t/acme)—customers still see your domain in the address bar unless you add custom domain mapping. - Infrastructure hostnames visible in certificate details, mail headers, or diagnostic traces.
- Underlying hypervisor, backup or monitoring brand names in contracts and status pages you operate as ISV.
TLS and hostname discipline
Custom domains need certificate issuance and renewal owned clearly (ISV automation vs customer DNS admin). Mismatched names break SSO redirect flows customers already tested on the default hostname.
What to choose and why
Publish three commercial tiers:
| Tier | Typical scope | Customer effort |
|---|---|---|
| Cobrand | Logo + colours in app | Upload assets |
| Domain alias | Custom hostname + TLS | DNS CNAME + validation |
| Full white-label programme | Separate apps, email domain, support desk | Project fee + ongoing renewal |
Maintain a surface owner column: product, marketing, hosting provider, customer IT. Sales quotes only surfaces with owners and lead times.
Read next
Related articles you may want next.
- HostingWhat partners need to see that end customers should notGive partners the oversight they need while protecting each customer’s data through tenant boundaries, limited permissions and clear support access rules.Read article
- HostingTelling end customers about planned maintenance on a hosted ISV serviceGive customers clear maintenance notices with local times, expected impact, preparation steps and completion updates, including a practical path for urgent security work.Read article
- HostingTime zones and financial calendars when Australian customers share a hosted stackDesign time zones, daylight saving and financial calendars for Australian customers so scheduled work and reports use the intended business dates.Read article
Risks and limits
- Phishing optics: look-alike domains without clear authentication educate users badly; enforce MFA and teach URL verification.
- Email white-label still needs SPF, DKIM and DMARC design: DMARC pass requires an authenticated identifier (SPF or DKIM) that aligns with the From domain; the recipient’s policy then decides delivery, quarantine or rejection—missing DKIM alone does not automatically mean “spam.”
- Accessibility contrast checks still apply when customers choose loud colours.
- For custom domains, the ISV must document which certificate issuance and renewal steps are actually automated.
- Not legal advice on trademark or reseller representation.
Sources
- Redirect URI (reply URL) restrictions and limitations — Microsoft Learn; accessed 2026-11-16 — registered redirect URIs and hostname limits for Entra app registrations.
- How to add a redirect URI to your application — Microsoft Learn; accessed 2026-11-16 — where tokens are sent after authentication (companion to reply URL restrictions).
- RFC 7489 — DMARC — IETF; accessed 2026-11-16 — identifier alignment and domain-level mail authentication policy.
- Transport Layer Security (TLS) — MDN; accessed 2026-11-16 — HTTPS and certificate naming expectations.
Related reading
- What partners need to see that end customers should not
- Time zones and financial calendars when Australian customers share a hosted stack
- Telling end customers about planned maintenance on a hosted ISV service
- Software vendor hosting (related service context)
Learning notes
- White-label is DNS, mail and identity—not only logos.
- Publish what cannot change to protect sales margins.
- Mobile apps are the usual surprise in “full white-label.”
- Custom domains need renewal ownership like any production dependency.
- Tiered branding packages beat bespoke promises per deal.
This article was originally published on .