“White-label” is used loosely enough that two vendors can both claim it and mean very different things. One puts your logo in the corner of their app. The other ships an app under your name, on your domain, that a student could use for a year without learning the vendor exists. Where a platform sits on that spectrum decides whether your students think they are learning with you or with someone else.
This guide sets out what genuinely carries your brand, what usually does not, and the questions worth asking before you sign.
What white-labeling an LMS actually means
White-labeling an LMS means the platform is delivered under your brand rather than the vendor’s: your logo, colours, domain and app-store listing, with vendor branding removed from what learners see. The vendor still builds and hosts the software. You own the relationship, the brand and the learner data.
The five layers where branding either shows or does not
Most comparisons stop at “you can add your logo”. It is more useful to look layer by layer, because that is where vendors differ.
- Web platform — logo, colours and a custom domain are brandable on any genuine white-label platform. Ask whether you get your own domain or a subdomain of theirs.
- Mobile apps — app name, icon, splash screen and store listing carry your brand. The store developer account is the question that matters: yours or the vendor’s?
- Email — sender name, templates and reply-to are usually yours. The sending infrastructure is typically shared, so ask whether a “via” line appears in the header.
- Payments — checkout appearance and invoice branding are configurable. Ask whose name lands on the student’s bank statement.
- Certificates — design, signature and seal should be fully yours, not a fixed template with a logo dropped in.
Your brand, everywhere
Logo, colours and name across web and apps — with no vendor branding visible to students. This is the baseline, and the easiest part for any vendor to deliver.
Your own domain
Learners visit your address, not a shared subdomain. It builds trust, looks professional, and means the search equity you build over time accrues to your domain rather than the vendor’s.
Apps in your name
Android and iOS apps published under your developer identity, on the stores, as your brand. There is a real trade-off here worth understanding: publishing under the vendor’s developer account is faster to launch, while publishing under your own means you keep the listing, the reviews and the install base if you ever move.
Your data
Student and payment data belong to you and are exportable — you are never locked in. Ask for the export format before you sign, not after. “You can export” and “you can export something you can actually use” are different promises.
No revenue sharing
You keep what you earn. A true platform charges for the software, not a cut of your fees. If you are weighing models, the difference compounds: a percentage of revenue grows with your success, while a subscription does not. We cover the arithmetic in our guide to comparing total cost rather than subscription price.
Where “white-label” usually stops
Three places a vendor’s name commonly survives, across the industry generally: the app-store developer account, transactional email headers, and the payment descriptor on a card statement. None is automatically a dealbreaker — but you should know which apply before launch rather than discover them from a student.
White-label or a marketplace listing?
White-labeling is one of two routes. The other is listing on a marketplace, which trades brand control for built-in discovery. If you have not settled that question yet, start with white-label LMS versus a course marketplace — it is a different decision from the one on this page, and worth making first.
Questions to ask a vendor before signing
- Whose developer account will the apps be published under?
- Do I get my own domain, or a subdomain of yours?
- What name appears on the student’s payment descriptor?
- Can I export learner and payment data, and in what format?
- What happens to my branded app if I cancel?
- Is there a revenue share on top of the subscription?
Bring that list to any vendor you are evaluating, including us. A platform that answers all six plainly is telling you something useful; one that deflects on the developer account is telling you something too.
Frequently asked questions
Does white-label mean the vendor’s name appears nowhere? Not usually. Expect it to survive in infrastructure layers such as the developer account or email headers. Ask specifically rather than assuming.
Can I use my own domain? On a genuine white-label platform, yes. A subdomain of the vendor’s domain is not white-label.
Do I keep the app if I switch vendors? Only if it was published under your own developer account.
Is white-label more expensive? It is often a higher subscription tier, but compare it against revenue-share models before concluding it costs more.
If you run an institute rather than a solo practice, the branding questions above play out slightly differently across branches and batches — see branded apps for coaching institutes.