Moodle LMS or Moodle Workplace: when the free edition is enough
For most teams that already run Moodle for training, the free GPL-3.0-or-later Moodle LMS is enough when the work is course delivery, assessment, cohort enrollment and reporting that the core product already handles, and when your team is willing to build or source any extra workflow as plugins. Moodle Workplace is worth evaluating when the corporate training load depends on tools the LMS does not cover out of the box, such as compliance-driven assignment workflows, hierarchical organization structures or manager-led programs at scale. Workplace is not open source, is licensed software available only through Moodle Premium Certified Partners and Service Providers, and is priced according to the hosting and services it requires, so it is a procurement decision as much as a technical one.
Before you open a conversation with a partner, write down the three or four workflows that drive your training operation and test each against the standard LMS. If every workflow is met by core features or a plugin you can maintain, the free edition carries lower licensing exposure. If one or more workflows require a proprietary feature, ask the partner in writing which Workplace components deliver it, what the licensing and hosting terms are, and whether your current Moodle site can be upgraded to Workplace. Moodle's Workplace page states that an existing standard site can be upgraded, but confirm the path, the prerequisites and any data migration steps for your version, since upgrade requirements depend on the release you run.
Treat the decision as a lock-in decision too. Once corporate workflows and custom data structures live inside a proprietary edition, moving back to the open LMS or to another platform becomes a migration project with its own cost, and you depend on a licensed vendor relationship for future updates. Ask for the exit terms in writing, including what data export is supported and whether plugins you built will still run on the open edition. Also confirm the support windows for the Moodle release you would be upgrading to, since the free LMS follows the Moodle LTS schedule, and check that your partner's plan matches it.
Which Moodle features are free and which are paid in Workplace
This table separates what Moodle documents as shared LMS functionality from the workplace training tools Moodle describes for Workplace. Where the public material is silent on a feature, the table says so, and those items belong on your questions for a Premium Certified Partner before you compare quotes.
| Capability | Moodle LMS (GPL-3.0) | Moodle Workplace (proprietary) |
|---|---|---|
| Core course authoring, enrolments and activities | Included. Core LMS features under GPL-3.0 with a free download for self-hosting. | Included as part of Workplace, which Moodle describes as combining LMS features with workplace training tools. |
| Workplace-specific training tools | Not described as part of the LMS distribution in Moodle's public material. | Moodle describes these as the reason Workplace exists. Confirm the exact tool list and what each one covers with a Premium Certified Partner. |
| Authentication plugins (LDAP, LTI, OAuth 2, Shibboleth, web services) | Shipped in core under the public/auth directory. | Not listed separately in Moodle's public Workplace material. Confirm each plugin, including LDAP and SAML2, against Workplace before you rely on it. |
| SAML2 single sign-on via the auth_saml2 plugin | Available as a third-party plugin from the Moodle Marketplace. Confirm version compatibility with your Moodle release. | Not stated in public Workplace material. Ask the partner whether it is supported, and whether plugin installs are covered in the price. |
| Plugin installation and custom code | Self-hosted sites can install plugins. Plugin types and APIs are documented by Moodle. | Confirm with the partner which plugin installs are permitted and who maintains custom code after upgrades. |
| Licence and source access | GPL-3.0 code, so you may inspect, modify and self-host it. | Proprietary and sold only through Moodle Premium Certified Partners and Service Providers. Moodle states it is not open source. |
| How the edition is priced | No licence fee for the software. Hosting, administration and any support contract are separate costs. | Priced by Moodle based on the hosting and services required, according to Moodle's Workplace page. Request a quote that itemises hosting and services. |
| Upgrade path from an existing Moodle site | Not applicable. This is the base platform. | Moodle states that a standard Moodle LMS site can be upgraded to Workplace. Confirm the upgrade steps, supported Moodle versions and any data migration with the partner. |
| Exit or switching cost | Lower dependence on a single vendor because the code is GPL-3.0 and can be self-hosted elsewhere. | Higher dependence on the licensed product and its partners. Ask in writing what happens to your data, plugins and customisations if you leave. |
How licensing, support and updates differ between the editions
Moodle LMS is free GPL software that you can run, modify and redistribute under published terms, with support windows set by Moodle's release policy. Moodle Workplace is proprietary, sold through certified partners, and governed by its own agreement, so the questions that matter sit in the contract as much as in the code.
GPL-3.0-or-later for Moodle LMS
Moodle LMS is licensed under GPL-3.0-or-later, so your team can run, study, modify and redistribute the code under the terms of that license. This matters when you plan custom plugins or theme changes that you may later share or hand to another provider. Check that any third-party plugin you add carries a license compatible with your plans, since plugin licenses are set by their authors.
Workplace is proprietary software
Moodle describes Moodle Workplace as not open source and licensed software, so the free GPL terms that cover Moodle LMS do not carry over. Code access, modification rights and any redistribution rights come from the Workplace agreement, which you should read before committing. Ask the partner in writing what you may change, share or keep after the contract ends.
Workplace sold only through partners
Workplace is available only through Moodle Premium Certified Partners and Service Providers, so the partner is your licensing channel and usually your first support contact. Pricing follows the hosting and services required, which means the quote reflects the partner's scope. Ask who holds the license, who handles renewals and what happens to your site if the partner relationship ends.
LTS windows for Moodle LMS
Moodle 5.3 is the current LTS release, with general support until October 4, 2027 and security support until October 1, 2029. Moodle 4.5 receives security support until October 4, 2027, so sites on it have a shorter runway. Plan your upgrade calendar around these dates and confirm the current status on the releases page before you commit to a version.
Workplace release and support terms
Public Moodle release windows describe Moodle LMS, so do not assume the same dates apply to Workplace. Ask the partner for the Workplace version you will run, its support end date, the security patch process and the upgrade path to later versions. Get these commitments in the contract, not only in a sales deck.
Who supports each edition
Moodle LMS has community support, documentation and a choice of hosting providers, including self-hosting by your own team or a Moodle Partner. Workplace support comes through the licensed partner under its service terms. Whichever you choose, name the party responsible for security patches, incident response and upgrades in writing, because that responsibility is what separates the two editions in practice.
What Moodle Workplace adds for corporate training
Moodle describes Workplace as an enterprise learning platform that combines Moodle LMS features with tools for workplace training. Treat that description as a starting point, not a feature list. Core Moodle already handles course building, enrolment, grading and completion tracking for one organization. Workplace only changes the decision when your training is run across many business units, with compliance-driven assignments, recurring certifications and central reporting that a single core site would have to be stretched to cover. If your catalog is a modest set of courses for one workforce, the core LMS may already meet the requirement. Write down which of these workflows you run today, how often, and for how many people before you compare the two.
Identity is where many corporate buyers expect a difference, but core Moodle already ships authentication plugins for manual accounts, email self-registration, external database, LDAP, LTI, OAuth 2, Shibboleth and web services. SAML2 single sign-on is available as a separate marketplace plugin. Before you assume Workplace is needed for directory integration, confirm which of these your identity provider requires and whether the Workplace edition changes how user records, departments or reporting lines are synchronized. Ask the partner to show the synchronization path with your own directory structure, using a test tenant that mirrors your organizational hierarchy.
Because Workplace is licensed software and not open source, its capabilities, support terms and price are set by the vendor and its partner, not by the GPL code you can inspect in core. The vendor states that pricing depends on the hosting and services required, and that Workplace is available only through Moodle Premium Certified Partners and Service Providers. Request a demo or written feature list from a certified partner, and ask them to map each capability to your catalog size, compliance reporting needs and number of organizational units. DeployOpen is not a Moodle Premium Certified Partner, so that confirmation must come from the vendor's channel. The vendor also states that a standard Moodle LMS site can be upgraded to Workplace, so ask what that upgrade reverses if you later leave.
What Workplace costs compared with a free Moodle LMS site
This table separates what the free Moodle LMS costs to run from what Moodle Workplace adds, showing who gets paid for each part and whether it recurs. Use it to build a question list for partner quotes, because no Workplace price list is published and the final figure depends on hosting and services scoped by a partner.
| Cost component | Moodle LMS (self-hosted, GPL-3.0) | Moodle Workplace (partner-quoted) |
|---|---|---|
| Software licence | Free to download and use under GPL-3.0 or later | Proprietary licence, sold only through Moodle Premium Certified Partners and Service Providers |
| Hosting | Paid to your cloud, data center or hosting provider, sized by your own infrastructure | Priced on the hosting and services required, as scoped in the partner quote, per Moodle's Workplace page |
| Initial setup and configuration | Paid to your staff or an implementation partner, usually one-time | Included in or priced separately by the partner, so confirm it in writing |
| Upgrades and major releases | Paid to your staff or a partner, recurring with each release cycle | Ask whether upgrades are included, how often they occur and whether they are billed separately |
| Plugin and integration work | Paid to developers for custom plugins or integrations you need | Ask which Workplace features cover your needs and which require custom work billed on top |
| Support | Paid to a Moodle Partner or internal team, typically recurring | Ask what support tier is included, its response terms and whether it recurs annually |
| Migration from an existing Moodle site | Your own staff time, or a partner for the move between versions | Ask whether upgrading an existing Moodle site to Workplace is a one-time fee and what it covers |
| Exit or switching cost | Low licence exit cost, but data export and reconfiguration effort remain | Ask about data export formats, notice periods and any fees for leaving the partner or product |
Upgrading an existing Moodle site to Workplace and what it locks in
This sequence moves an existing Moodle site toward Workplace with a clear baseline, a scoped migration, a tested cutover and a return path if the project stops. It also shows where contract terms decide how much freedom you keep afterward.
Confirm the current Moodle version and requirements
Record the Moodle version the site runs today, the PHP version, the database engine and version, and the web server document root. Moodle's 5.1 release notes say sites must be on Moodle 4.2.3 or later to upgrade to that release, and the 5.3 release notes say sites must run Moodle 4.4 or later to upgrade to 5.3. From Moodle 5.1 onward the document root must point to the /public directory, so check that setting now. The step is done when you have a written inventory of versions, plugins and server configuration that a partner can review. Ask your current host or internal team to confirm each item, because the inventory drives every later estimate.
Confirm Workplace is the right edition
Before engaging anyone, document which corporate training needs drive the move, such as compliance tracking, hierarchies, or certification workflows, and confirm which of them the LMS you run now cannot meet. Moodle describes Workplace as built for workplace training, and states it is not open source. Ask Moodle or a Moodle Premium Certified Partner to show, in writing, which Workplace features map to your requirements. The step is done when your requirement list is signed off by the business owner and the gaps are named.
Engage a Moodle Premium Certified Partner
Workplace is available only through Moodle Premium Certified Partners and Service Providers, so the partner is your sole route to licensed software. Request written answers on the licensing model, how pricing is set (Moodle's Workplace page says it depends on the hosting and services required), who hosts the environment, and who carries upgrade responsibility. Compare at least two partners on the same written questions. The step is done when you hold comparable written proposals and a named contact for the migration.
Scope the migration and its exclusions
Agree a written scope covering the upgrade of the core Moodle version, the migration of courses, users, enrolments, grades, custom themes and third-party plugins, and the parts that will be rebuilt rather than moved. List every plugin on the current site and mark whether a Workplace-compatible version exists, is replaced, or is dropped. Also confirm who owns test data, backups and the integrations with HR or single sign-on systems. The step is done when the scope document lists deliverables, exclusions and acceptance tests that both sides have signed.
Build a staging copy and test the upgrade
Restore a copy of the production database and files into a separate environment, run the upgrade there, and test course access, enrolment sync, reporting, authentication and each custom plugin. Test the web server configuration for the /public document root and confirm that no directory listings or errors appear. Repeat the rehearsal until the runbook runs without manual fixes. The step is done when the rehearsal passes every acceptance test in the scope document and the runbook records the exact steps and timings observed.
Cut over with a rollback plan
Schedule the production cutover in a maintenance window agreed in writing. Take a full database and file backup immediately before the change, freeze content edits, run the upgrade from the runbook, and reconnect authentication and integrations in a fixed order. Keep the pre-upgrade environment intact until acceptance is signed. The step is done when users can sign in, grades and enrolments match the pre-cutover snapshot, and the rollback procedure has been rehearsed at least once.
Plan the return path before signing the contract
Moving back to a plain Moodle LMS, changing partners, or self-hosting the upgrade all depend on contract terms that Workplace is licensed software. Ask in writing whether you receive a license you can run yourself, what happens to your data and configuration on termination, which export formats are provided, and whether a standard Moodle LMS site can be restored from your backups. Check that Moodle's upgrade path from a standard LMS to Workplace is one-way in your contract terms. The step is done when legal and the technical owner have reviewed these answers and accepted or negotiated them.
Document the lock-in and review it yearly
Record every dependency created by the move: the licensing terms, the partner who supports the install, the Workplace-specific data structures, and any plugin only available through that partner. Set a recurring review, at least when Moodle publishes a new LTS release or your partner contract renews, to confirm the exit path still works. Keep an exported copy of course content and user records in open formats. The step is done when the lock-in register exists, has a named owner, and is scheduled for review.
Questions buyers ask before choosing Moodle Workplace
What does Moodle Workplace cost, and how is the quote built?
Moodle Workplace is not open source, and Moodle states that it is priced based on the hosting and services required, so there is no public list price to compare against the free GPL Moodle LMS. The quote is built from the hosting footprint, the number of users, the services you need from the partner (installation, configuration, integrations, training and support) and the license itself, which is sold only through Moodle Premium Certified Partners and Service Providers. Ask each partner to split the quote into one-time items (setup, upgrade from your current site, integrations) and recurring items (license, hosting, support), and to state which Moodle release the quote covers. Compare the same scope across partners before comparing totals.
How long does an upgrade from Moodle LMS to Workplace take?
The supplied facts do not give a duration, so ask partners for a written timeline tied to your environment. The effort depends mainly on the size of your current site (courses, users, custom themes and plugins), your database and PHP stack, whether your web server already points to the /public directory that Moodle 5.1 and later require, and how much of the corporate training model you plan to configure during the move. Ask for the upgrade steps, the test environment plan, the rollback approach and which items the partner will not cover. Request the timeline in writing before work begins, as part of a fixed scope.
What does Workplace need from our own team?
Expect to need people who own the business decisions and people who own the platform. On the business side, you need a named owner for the training catalog, compliance course rules, reporting needs and user onboarding. On the technical side, you need staff who manage the web server, PHP, the database, backups, certificates, identity integration and deployments in your own infrastructure. Your team will also review the partner's upgrade plan and test results. Confirm with each partner which of these tasks they run for you under a retainer and which stay with your staff.
Can our own Moodle admins run Workplace after go-live?
Often yes for day-to-day tasks, but confirm the scope before you assume it. Admins who already run Moodle LMS will recognize the core administration, while Workplace adds corporate features that need separate configuration and testing. Ask the vendor and partner which Workplace administration tasks are documented for your staff, which require partner involvement, and how security patches and point releases are applied. A practical test is whether your admins can complete a Workplace upgrade in a staging copy without outside help. If they cannot, budget for a support arrangement with a partner.
How do we avoid lock-in with Moodle Workplace?
Lock-in comes from the license, the partner relationship and any Workplace-specific data or customizations, so plan for an exit before you sign. Moodle Workplace is not open source and is available only through Moodle Premium Certified Partners and Service Providers, so changing partners or leaving the edition is a real project, not a configuration change. Ask for contract terms covering license continuity, data export in standard formats, a documented list of Workplace-only features you rely on, and the cost of moving back to Moodle LMS. Keep your course content, user records and reporting exports in a form you can read without the platform.
Can the free Moodle LMS be extended with plugins instead of buying Workplace?
It depends on which corporate features you need, so map them before deciding. Moodle core ships authentication plugins for manual accounts, email self-registration, external database, LDAP, LTI, OAuth 2, Shibboleth and web services, and the Moodle plugin types documentation describes how additional plugins are structured. Check whether a community plugin covers each requirement, such as SAML2 single sign-on, which is available from the Moodle plugin marketplace. Then confirm that each plugin is maintained for your Moodle release. Features that the Workplace page presents as part of the edition should be tested directly against the LMS with plugins, since plugin support and maintenance become your responsibility.
What should we confirm about Moodle's release support before signing?
Confirm which Moodle release your Workplace edition is built on and how its support window lines up with your plans. Moodle 5.3 is a long-term support release with general support until October 4, 2027 and security support until October 1, 2029, according to the Moodle releases page. Moodle 4.5 LTS receives security support until October 4, 2027. Ask the partner how Workplace point releases and major upgrades are scheduled, who performs them, and whether the quote includes them. Shorter support windows mean more frequent upgrade projects, so include them in your total cost of ownership.
What does a Moodle 5.3 requirement mean for hosting?
Moodle 5.3 requires 64-bit PHP 8.3 or later, and supports PostgreSQL 17, MariaDB 11.4, MySQL 8.0 and Microsoft SQL Server 2019 as minimum versions, while Oracle Database is no longer supported from Moodle 5.0. Confirm with the partner whether those minimums apply to the Workplace build you are quoted, and whether your current database and PHP versions need upgrading first. Also check that your web server points to the /public directory, as the Moodle 5.1 release notes require. Hosting changes can add cost and effort to the upgrade, so ask the partner to include them in the written scope.
Where the free Moodle LMS still fits enterprise training
The GPL edition is enough when the training need is mostly course delivery, enrolment, assessment and completion tracking, and when the identity source can be reached through what core already ships. Moodle core includes authentication plugins for manual accounts, email self-registration, an external database, LDAP, LTI, OAuth 2, Shibboleth and web services. A team with an Active Directory or an OAuth 2 identity provider can often start there. Confirm this against your own directory design before you assume it. SAML 2 is not in the core list. It comes from the *SAML2 Single sign on* plugin on the Moodle Marketplace, so you would need to review and maintain that plugin yourself.
The licence gives your organization the freedoms that matter for internal use. Moodle is released under GPL-3.0-or-later, so you can run, modify and redistribute the code, subject to the licence terms, without a per-seat fee from Moodle HQ. The large plugin ecosystem is built on documented plugin types, which lets you add activities, blocks, authentication methods and reports without changing core. Before you adopt any plugin, check its licence, its maintenance history and its compatibility with the Moodle version you plan to run. An unmaintained plugin is a cost you carry, whichever edition you choose.
The free edition fits when your team can own hosting and upgrades. That means running a supported PHP and database stack, applying point releases, keeping plugins current and maintaining backups and monitoring. Moodle 5.3 is the long-term support release, with security support until 1 October 2029, and Moodle 4.5 LTS receives security support until 4 October 2027. From Moodle 5.1, the web server document root must point to the public directory. Upgrading also has minimum-version rules, so plan the path from your current release. The effort you accept in exchange is recurring staff time, and you should confirm who on your team or with a service provider will carry it.
How DeployOpen scopes, delivers and supports either Moodle edition
DeployOpen works on self-hosted Moodle LMS inside your own cloud accounts, data centers or air-gapped networks. The cards below cover how an engagement is scoped, built, handed over and kept current, and what you must confirm about Moodle Workplace before any of that work starts.
Fixed-scope planning and written quotes
Most engagements are fixed-scope, with scope, deliverables and timelines agreed in writing before work starts. DeployOpen does not publish a price list, so a quote follows from that written scope. Ask for the quote to list which Moodle release and PHP and database versions are assumed, which plugins are in scope, and which items are excluded. This is the point where an open-source LMS and a licensed Workplace build diverge most, because Workplace pricing depends on the hosting and services required.
Hosting, hardening and backup
DeployOpen builds the Moodle LMS stack in the client's own infrastructure, including the web server, PHP, database and backup routines. From Moodle 5.1, the web server document root must point to the new /public directory, so the hardening baseline should be set against that layout from the start. Confirm who owns the database backups, restore testing and the retention period for uploaded course files.
Integration and identity wiring
Moodle core ships authentication plugins for LDAP, LTI, OAuth 2, Shibboleth and web services, and SAML 2 is available through a marketplace plugin. DeployOpen can connect these to your directory and identity provider and document the mapping of roles and cohorts. For Workplace, confirm with the Premium Certified Partner which integrations are included in the license and which are custom work.
Customization and plugin governance
Customization covers theme changes, plugin selection and custom code, and each plugin adds a maintenance obligation at every Moodle upgrade. Ask for a plugin inventory with version compatibility per release, and for a rule on which custom code is allowed. For Workplace, confirm whether Workplace features can be extended in the same way, since the edition is proprietary and not open source.
Upgrades, documentation and ongoing support
Upgrades follow Moodle's release calendar, and the support window of the chosen release determines how often you must move. Ongoing support, upgrades and continuous testing are available as retainers after handover. Ask for runbooks, configuration records and an upgrade plan that names the target release and its security support end date.
Confirm the Workplace contract holder
Moodle Workplace is licensed software available only through Moodle Premium Certified Partners and Service Providers. DeployOpen is not an official Moodle partner unless that is confirmed in writing, so the reader must establish who holds the Workplace contract, who invoices for licenses and hosting, and who provides first-line support. Ask the partner for the license terms in writing before the scope is signed.
