White-label knowledge base: the complete guide

What is a white-label knowledge base?

A white-label knowledge base is a help center that runs entirely under your brand — your domain, your logo, your colors, your typography — with no visible mention of the platform powering it. Your customers see help.yourbrand.com, not yourbrand.somekbtool.io. There is no "Powered by" badge in the footer, no third-party favicon in the browser tab, and no redirect through someone else's subdomain.

For SaaS companies running multiple brands, this matters enormously. Each brand needs its own documentation portal that looks and feels native. A shared "Powered by..." footer breaks the illusion and signals to customers that the company cut corners. Most users expect a help center to match the design and domain of the product they are using. When it doesn't, trust drops — and so does self-service adoption.

White-label goes beyond cosmetics. When your help portal lives on your own custom domain, all the SEO authority from inbound links, search traffic, and page engagement stays with your brand rather than leaking to a third-party platform. That distinction alone makes white-label a strategic decision, not just a design preference.

Why most KB tools charge extra for white-label

The industry treats white-label as a premium feature. Vendors know that branding matters to customers, so they gate it behind their highest tiers:

Intercom requires the Expert plan ($132/seat/month) to remove branding and use custom CSS. On lower plans, the Intercom logo stays visible in the help center widget and article pages.
Zendesk gates custom branding behind Suite Enterprise ($169/agent/month). Their Professional plan allows some color changes, but full brand removal — including the Zendesk footer — requires Enterprise.
Document360 includes white-label on Business plans ($249/month), but multi-brand portals require their Enterprise tier with custom pricing.
KnowledgeOwl includes white-label on all plans — but charges per-author ($95/month per additional author) and has no multi-brand support.

This means a SaaS company with 5 brands and 2 editors could be paying $264–528/month on Intercom just for knowledge base white-label. And that is for a single brand — multiply by 5 for multi-brand, and costs quickly exceed $1,000/month for what amounts to logo removal and a DNS record.

The reason vendors price it this way is straightforward: white-label customers are sticky. Once your domain, branding, and content are live under your own URL, migration costs are high. Vendors capture that lock-in and price accordingly.

The multi-brand problem

Most knowledge base tools assume you have one brand. If you run multiple brands (white-label products, agency clients, partner portals), you face three bad options:

Pay per brand — Separate subscriptions for each brand. 5 brands × $132/seat = $660/month just for Intercom. If you compare Zendesk costs, it is even steeper at $845/month for 5 agents.
Copy-paste content — Duplicate articles across separate accounts. Content drifts within weeks. Your billing FAQ says one thing on Brand A and something slightly different on Brand C. Customers notice.
Skip white-label — Use a shared portal with generic branding. Looks unprofessional and confuses customers who see a third-party domain when they expect your help center.

None of these scale. By the time you reach 10 brands, the operational overhead of managing separate accounts — separate logins, separate content updates, separate billing — consumes hours every week. Teams that manage multi-brand documentation from a single source consistently report 4× faster content updates compared to the copy-paste approach.

How Multibase solves this

Multibase was built specifically for the multi-brand use case:

One account, unlimited portals — Write content once, publish to any combination of branded portals. No duplicate articles, no content drift.
White-label on all paid plans — Custom domain, logo, colors, CSS overrides from $49/month. Not gated behind an enterprise tier.
Unlimited team members — No per-seat charges. Add editors, reviewers, and contributors freely. A 10-person documentation team costs the same as a solo writer.
AI-powered answers — Readers get direct answers instead of article lists, with source citations. Each portal's AI only references that portal's content, so brand separation is maintained.
Reusable snippets — Shared content blocks (pricing tables, legal disclaimers, onboarding steps) that update across all portals when you edit them once.
Built-in analytics — See which articles perform, which searches return no results, and where your documentation has gaps — per portal or across all portals.

Setting up a white-label portal

Setting up a branded portal in Multibase takes about 20 minutes:

Create the portal — Give it a name and assign it to your brand. Choose its default language (Multibase supports multilingual content with 45+ languages out of the box).
Connect your domain — Add a CNAME record pointing help.yourbrand.com to Multibase. SSL certificates are provisioned automatically. No manual certificate management required.
Upload branding — Logo, favicon, primary color, accent color, font selection. Optionally add custom CSS for full design control — override headers, sidebars, search bars, and article layouts.
Assign content — Select which articles and categories appear on this portal. Use selective publishing to share core content across portals and create portal-specific overrides where needed.
Configure AI answers — Enable AI search for the portal. The AI model indexes only this portal's content, so answers never leak information from other brands.
Publish — Your branded help center is live on help.yourbrand.com with full SSL and zero third-party branding.

Every portal is fully independent — different domains, different branding, different navigation, different language settings — but all powered by the same content library. Write a billing FAQ once, publish it to all 5 portals, and update it in one place when pricing changes.

What to look for in a white-label KB platform

When evaluating platforms, check these specifics — many vendors advertise "white-label" but deliver only partial branding control:

Custom domain — CNAME mapping to your own domain, not a subdomain of the tool. help.yourbrand.com is white-label; yourbrand.kbtool.io is not. Verify that SSL is included automatically.
Full brand removal — No "Powered by" footer, no platform branding anywhere — including search results pages, 404 pages, and error states. Some tools remove branding from article pages but leave it in the widget or search overlay.
Custom CSS — Override any style, not just colors and logo. You should be able to change typography, spacing, sidebar layout, and header structure. If the vendor limits you to a color picker and logo upload, that is not full white-label.
Per-portal theming — Each brand gets its own look, not a shared template with color swaps. Verify that you can have completely different layouts, navigation structures, and CSS per portal.
Custom fonts — Upload your brand's typeface or reference Google Fonts. Default system fonts signal generic tooling.
No enterprise gates — White-label available on plans under $100/month. If you need to "contact sales" for basic branding control, expect $500+/month pricing.
Gap detection — The platform should tell you which topics are missing or underperforming, so your white-label portal does not just look professional but actually helps customers self-serve.

SEO benefits of white-label

One of the most overlooked advantages of a white-label knowledge base is the SEO impact. When your help center lives on your own domain — help.yourbrand.com or docs.yourbrand.com — every piece of content you publish builds domain authority for your brand, not for a third-party platform.

Here is what changes when you move from yourbrand.somekbtool.io to your own custom domain:

Domain authority consolidation — Backlinks to your help articles strengthen your root domain. If your help center is on someone else's subdomain, those links benefit them instead of you.
Branded search results — Google displays your domain in search results. Customers searching for "YourBrand billing help" see help.yourbrand.com instead of a third-party URL. Click-through rates improve because users trust familiar domains.
Internal linking power — You can cross-link between your marketing site, product docs, and blog on the same domain family. This creates a stronger internal link graph that search engines reward.
Indexed long-tail content — Help articles are natural long-tail keyword magnets. Queries like "how to reset password in YourBrand" or "YourBrand API rate limits" drive organic traffic directly to your domain.
No SEO risk from platform changes — If your KB vendor changes their URL structure, gets penalized, or shuts down, your domain and rankings are unaffected when you own the URL.

Companies that move their help center from a third-party subdomain to a white-label custom domain typically see a 15–30% increase in organic help center traffic within 3–6 months, simply because domain authority is no longer split.

Common white-label mistakes

Even teams that invest in white-label branding often leave gaps that undermine the professional appearance:

Forgetting error pages — Your 404 page, search-no-results page, and maintenance page should all carry your branding. Default error pages with the platform's logo are an instant tell.
Ignoring email notifications — If your KB sends email digests or article update notifications, those emails must also be branded. Check whether the platform lets you customize email templates and sender addresses.
Mismatched mobile experience — Test your branded portal on mobile. Some platforms only apply custom CSS to desktop views, and the mobile layout reverts to default styling.
Skipping favicon and Open Graph images — When someone shares a help article on Slack or social media, the preview card should show your brand's image and favicon, not the platform's default.
Using the platform's default search placeholder — Small details like "Search our help center" using a generic phrase instead of your brand name break immersion. Customize every visible string.
Not setting up redirects — If you are migrating from another tool, set up 301 redirects from old URLs to new ones. Losing existing search rankings defeats the SEO benefit of white-label.

Pricing comparison

| Feature | Multibase Growth | Intercom Expert | Zendesk Enterprise | Document360 Business | |---------|-----------------|-----------------|-------------------|---------------------| | Monthly cost | $49 | $132/seat | $169/agent | $249 | | White-label | ✅ Included | ✅ Expert only | ✅ Enterprise only | ✅ Business only | | Multi-brand portals | 3 portals | 1 per workspace | Enterprise only | 1 per project | | Unlimited team | ✅ | ❌ Per-seat | ❌ Per-agent | ❌ Per-account | | AI answers | ✅ Included | $0.99/resolution | $1.50/resolution | Add-on pricing | | Custom domain | ✅ All plans | ✅ Expert only | ✅ Enterprise only | ✅ Business only | | Custom CSS | ✅ Full override | ✅ Expert only | ✅ Enterprise only | ✅ Limited | | Multilingual | ✅ 45+ languages | ✅ (manual) | ✅ (add-on) | ✅ (limited) |

Bottom line

White-label shouldn't be an enterprise feature. If you're running multiple brands and paying $200+/month just to remove someone else's logo from your help center, you're overpaying — and you're giving away SEO authority in the process.

Multibase includes full white-label — custom domain, logo, colors, CSS, zero platform branding — on every paid plan starting at $49/month. No per-seat charges. No enterprise gates. Your help center looks like yours because it is yours.