Blog · Licence guides
Using LMS White after optional support ends
Updated 5 September 2026 · Based on our Software Licence & Services model
A fully paid perpetual licence can continue even if you stop buying optional support — you still maintain third-party services and future maintenance yourself or via new work orders.
What this means for you
You may continue using a fully paid Deployment after ending an optional support or commercial relationship with LMS White, subject to you maintaining required Third-Party Services, accounts, subscriptions, certificates, payments and technical dependencies.
Termination of optional support does not by itself revoke that perpetual deployment licence. You keep Client Data, Client Content, Client-controlled accounts and branding. LMS White keeps platform IP and source. Future OS/store maintenance may still be needed — as chargeable work or by another provider you engage.
LMS White will not arbitrarily disable a fully paid Client-controlled Deployment solely because you stop buying optional services, subject to technical dependencies and lawful requirements. Suspension can still apply for non-payment of LMS White invoices, unlawful use, security threats or government/marketplace orders.
Why perpetual use still needs cloud and maintenance
A licence is permission to use software. Cloud meters, Apple memberships and certificates are separate subscriptions. Stopping “support” does not freeze Android and iOS in time — which is why Maintenance Updates remain a real-world need even for perpetual licence holders.
Examples
- You pause a support retainer → learners can still study while your Firebase project stays paid and secured by you.
- Two years later iOS requires a new SDK → you request a Maintenance Update quotation or handle builds with another engineer under your licence terms.
What the licence protects: continued use of a fully paid Deployment for your institution.
What the licence does not freeze: vendor fees, store rules or the need for occasional compatibility work.