Skip to main content
Technology & EngineeringDesign Systems29 lines

White-Label Multi-Tenant Frontend

Serve tenant-specific branding with safe hostname resolution, validated token overrides and tenant-isolated HTML, assets and cache entries.

Quick Summary9 lines
Define how a known tenant selects its branding and whether each surface is public or account-specific. Resolve a normalized domain or route through a server-owned allowlist that maps to an immutable tenant ID. Do not grant membership or choose a theme by trusting an arbitrary incoming header. Confirm who is authorized to attach a custom domain and configure a documented safe response for an unknown host. Authentication remains a separate check even when a branded public landing page is allowed.

## Key Points

- [Design Tokens Community Group specifications](https://www.w3.org/community/design-tokens/)
- [IETF HTTP caching standard](https://www.rfc-editor.org/rfc/rfc9111.html)
- [WCAG 2.2 contrast requirements](https://www.w3.org/TR/WCAG22/?KBOpenTab=undefined)
skilldb get design-systems-skills/white-label-frontendFull skill: 29 lines
Paste into your CLAUDE.md or agent config

White-Label Multi-Tenant Frontend

Define how a known tenant selects its branding and whether each surface is public or account-specific. Resolve a normalized domain or route through a server-owned allowlist that maps to an immutable tenant ID. Do not grant membership or choose a theme by trusting an arbitrary incoming header. Confirm who is authorized to attach a custom domain and configure a documented safe response for an unknown host. Authentication remains a separate check even when a branded public landing page is allowed.

Build a constrained theme contract

Keep stable semantic token roles such as background, text, interactive accent and focus ring. Resolve a tenant's validated overrides on top of the common baseline. Use a reviewed fallback for missing or invalid values and check color contrast for the actual foreground/background pair. Treat logos and fonts as reviewed assets with defined formats, sizes and delivery origin. Tenant customization should not become an injection path for arbitrary HTML, CSS or script. Generate readable fallback text if an asset fails.

Make server rendering and hydration use the same tenant and theme revision. Check tenant switches across navigations, signed-out states, preview routes and missing assets. Ensure locale, appearance preferences and tenant theme precedence remain deterministic. Do not load another tenant's fallback as a shortcut.

Test identity and caches separately

Key publicly cacheable documents and theme assets by the relevant tenant identity, domain and revision where applicable. Confirm how the actual CDN normalizes request keys. Keep account-specific pages out of shared public caches. Do not assume that a header will isolate responses unless the cache configuration actually includes it. Purge or invalidate the intended tenant's revision without disrupting unrelated tenants.

Warm tenant A's page, then request the same path on tenant B's domain and as an unknown host. Repeat with both themes updated and across a client-side tenant switch. Require correct theme and assets, absence of the other tenant's identifiers and stable fallback. Attempt a forged host or tenant selector in an authorized fixture and verify that neither membership nor the resolved theme is improperly changed. Record the rendered HTML and cache behavior, not just an internal theme ID.

References and rights

Original SkillDB instructions under LicenseRef-SkillDB-Content. References were checked 2026-11-13 and used for technical verification.

Install this skill directly: skilldb add design-systems-skills

Get CLI access →