White-label docs: live branding, no rebuild
Rebrand in a minute
Everything visual, in one place
Is this multi-tenant, or one brand per deployment?
Safe by default
Built for the right hands
Rebrand in a minute DSR Docs ships ready to look like your product, not ours. Logo, colors, fonts, and footer are all editable from a single admin panel — and changes hot-apply through CSS variables , so the site re-skins instantly. No rebuild, no restart, no redeploy. Because the brand is data on disk — not compiled in — a color change ships in seconds instead of a release cycle no build step, no redeploy, no engineering ticket per visual tweak. And because DSR Docs is self-hosted, that identity is per deployment and lives on your infrastructure — you're skinning your own container, not renting a look from someone else's SaaS. The theme you're reading right now is that same engine applied to us; swap the three brand colors and it would be your product, top to bottom. Open the editor in one tab and the docs in another, and watch the whole site change color as you type. Everything visual, in one place You set It updates --- --- Site name Header wordmark and browser tab Logo & favicon Header mark and the tab icon Brand color Buttons, active nav, links, accents — everywhere Text & background Body copy, headings, panels, chrome Fonts Separate families for body, headings, and code Footer Footer text plus your Privacy and Support links One deployment, your identity — top to bottom, in a couple of clicks. Is this multi-tenant, or one brand per deployment? Branding is per deployment, not per request a running instance carries one identity at a time, so you don't serve Client A's brand and Client B's brand from the same URL. If you run a white-label developer portal for several clients, the standard pattern is one lightweight instance per brand, each with its own config and domain. See Ship a white-label developer portal for the full multi-tenant model, the WCAG-contrast behavior, and the deployment walkthrough. Safe by default Logo and favicon uploads accept the usual image formats and are sanitized on the way in any SVG is run through DOMPurify, which strips scripts, event handlers, and URLs, then stores the cleaned file (an SVG that sanitization leaves empty is rejected). Your brand assets land clean, every time. Built for the right hands Branding is an admin capability, kept separate from day-to-day content editing. Editors own the words; admins own the deployment's identity. Reset to the baseline at any time with a single button. [!IMPORTANT] Want this on your own documentation? Write to docs@dsr-corporation.com. Ask about migration, licensing, or anything this page didn't cover.