LMS White

Blog · Licence guides

Source code and production delivery

Updated 5 September 2026 · Based on our Software Licence & Services model

Why a licence includes a production Deployment, not human-readable source code, build pipelines or private keys — and why reverse engineering is restricted.

What this means for you

You receive a configured Deployment — the compiled, bundled, minified or hosted form of LMS White for your institution. LMS White is not required to deliver human-readable source code, internal repositories, CI/CD pipelines, signing infrastructure, private keys or other proprietary development assets.

To the extent allowed by law, reverse engineering, decompiling or bypassing technical protections to derive LMS White source is not permitted.

Why production delivery works this way

Almost every commercial software vendor licences a runnable product, not a dump of their private codebase. Source, build systems and signing keys are the company’s core IP and security surface. Handing those out with every sale would destroy the product business and create uncontrolled forks.

Browser apps must send some client-side code to the browser to run. That does not mean LMS White claims every front-end file is cryptographically impossible to inspect — only that you are licensed to use the Deployment, not to extract proprietary logic as if you bought the company.

Examples

  • You get admin dashboards, learner apps and cloud projects configured for you — not a GitHub org of LMS White’s private repos.
  • Mobile signing certificates and store keys stay under controlled account models (yours on Enterprise; shared publishing rules on Pro where applicable).
  • Paying for a custom feature still licences that functionality in your Deployment; it does not automatically assign source ownership unless a separate IP assignment says so.

What LMS White controls: proprietary source, tooling and how Deployments are packaged.

What this is not: hiding “your” student data. Client Data and Client Content remain yours; the restriction is on LMS White platform IP.

Supporting references