Blog · Licence guides
White-label branding vs software ownership
Updated 5 September 2026 · Based on our Software Licence & Services model
White labelling puts your name, logo and domain on the product. It does not transfer ownership of the underlying LMS White software.
What this means for you
Within your plan, LMS White can brand the Platform with your authorised name, logo, colours, domain and app identity. That is white labelling.
White labelling changes branding and deployment identity. It does not transfer ownership of the underlying LMS White software. You must have the rights to the brand assets you provide.
Why branding ≠ buying the engine
Car analogies are overused, but accurate here: putting your academy’s livery on a vehicle does not make you the manufacturer. The same pattern appears in white-label banking apps, CRMs and learning platforms worldwide.
Examples
- Learners see “Your Academy” on login — the learning engine is still LMS White IP.
- You own the trademark dispute risk for logos you supply; LMS White does not become the trademark owner of your brand.
- Custom modules built for you are typically licensed for use in your Deployment; reusable platform improvements remain LMS White IP unless a signed assignment says otherwise.
What LMS White controls: the software platform being branded.
What you control: your trademarks, content and how your institution presents itself — provided you have the rights to those assets.