FAQArchitecture & conceptsPart 1 of 3

What is the difference between multi-tenancy and white labelling?

4 min readUpdated May 2026
Quick answer

Multi-tenancy is about architecture. White labelling is about appearance. Multi-tenancy means many organisations share one platform with isolated data. White labelling means each organisation can make the platform look like their own. They often appear together but they are not the same thing, and conflating them leads to bad buying decisions.

The core difference in one line

Multi-tenancy: how the system is built underneath.

White labelling: how the system looks on top.

Side-by-side

Brand controlHighLowData isolationLowHighWhite-label onlyLooks like yours,data is shared underneath.Risk: data leakageRecommendedBothTenant isolation+ full white labelling.For training operatorsNeitherGeneric shared LMS,no isolation, no branding.Internal tool onlyMulti-tenant onlyStrong isolation,vendor's brand visible.Risk: client trust
Multi-tenancy and white labelling are independent dimensions. Training operators need both.
Multi-tenancyWhite labelling
What it isAn architectural modelA branding feature
What it controlsData, users, infrastructureVisual identity
Who benefitsOperators running multiple clients or brandsEnd users seeing their own brand
Typical elementsTenant isolation, shared codebase, role hierarchyLogos, colours, fonts, custom domain, email templates
Can exist without the other?Yes, a multi-tenant platform can have weak or no white labellingYes, a single-tenant platform can be fully white-labelled
Buyer question it answers"Can I run many clients on one system?""Can my learners see only my brand?"

Why the distinction matters when buying

Plenty of LMS vendors advertise white labelling without true multi-tenancy. What they actually offer is a single shared instance where you can change the logo per user group. There is no real tenant isolation, no separate admin, no separate user database. Reporting bleeds across "tenants." Permissions get tangled.

Other vendors offer multi-tenancy without strong white labelling. You get separate environments per tenant but every one of them has the vendor's name in the footer, the URL is a subdomain of the vendor's site, and email notifications come from the vendor's domain.

For training companies running courses for external clients, you need both. Without multi-tenancy, you cannot keep client data separate. Without white labelling, your client's learners see your vendor's brand instead of your client's brand, which breaks the trust your client paid you to build.

What full white labelling actually includes

Most LMS pages list white labelling as a feature without specifying scope. Ask vendors which of these they actually support per tenant:

White labelling capability checklist
  • Custom logo and favicon
  • Custom colour palette and typography
  • Custom domain or subdomain
  • Branded login and signup screens
  • Branded email notifications from your domain
  • Branded certificates with your logo and signature
  • Branded mobile app appearance
  • Custom legal pages (terms, privacy)

A vendor that offers three of these is not white-labelled. They have skinning.

Built for this

Multi-tenancy plus full white labelling on every tenant.

Blend-ed is a multi-tenant LMS built on Open edX with full white labelling on every tenant. Each tenant gets a custom subdomain, complete brand control, branded certificates and branded mobile experience. Learner data is isolated at the architecture layer.

For the architectural detail, see the full multi-tenant LMS guide.