What does Moodle give you for free?
Moodle is open source under the GPL and has been in continuous development since 2002. That longevity buys things that are expensive to rebuild and easy to underestimate when you are looking at a feature comparison.
It ships with a course and activity model that maps onto how most institutions already teach, a gradebook with weighting and aggregation rules that took years to get right, quiz types with question banks and randomisation, and support for the interoperability standards — SCORM, LTI, xAPI — that let third-party content and tools plug in without a bespoke integration each time.
It also brings a plugin ecosystem and, crucially, a labour market. You can hire someone who already knows Moodle. You cannot hire someone who already knows the LMS you are about to commission.
Where does Moodle stop fitting?
The pattern is consistent: Moodle handles the teaching well and the institution's surrounding processes poorly, because those processes are specific to you and Moodle is designed to be general.
- Admissions, fees, and attendance living in a separate ERP, so a student exists twice and the two records drift
- Non-course learning models — cohort programmes, competency frameworks, apprenticeships, or coaching batches with test series rather than semesters
- Parent and guardian access as a first-class role, which is central to K-12 and marginal in Moodle's model
- Board or university reporting formats that need data Moodle records in a shape the report does not expect
- A mobile experience that is your product rather than a companion to a desktop site
- AI-assisted evaluation wired into the grading workflow rather than bolted on beside it
How do the two options compare over five years?
The comparison people run is licence cost against build cost, and it is the wrong one — Moodle's licence cost is zero and it still is not free.
| Moodle | Custom LMS | |
|---|---|---|
| Licence | None (GPL) | None — you own it |
| Year-one cost | Hosting, setup, theming, plugin work, training | Full build cost, front-loaded |
| Ongoing cost | Hosting, upgrades, plugin compatibility after each release | Hosting and the features you choose to add |
| Time to first cohort | Weeks | Months |
| Fit to your process | Good where standard, awkward where not | Exact, and exactly as good as the discovery behind it |
| Upgrade risk | Customisations can break on major releases | You control the release; nothing changes underneath you |
| Talent availability | Broad | Whoever you build it with |
| Exit position | Standard data, portable | Depends entirely on how it was built |
What is the customisation trap?
The most expensive outcome is not choosing wrong. It is choosing Moodle and then customising it past the point where it is still Moodle.
Every core modification is a change you must re-apply, re-test, and sometimes re-invent at each major release, forever. Teams that cross roughly the 30% mark — where a third of the behaviour that matters comes from custom code — usually discover they now carry the maintenance burden of a custom LMS and the upgrade burden of a forked open-source project at the same time.
The discipline that keeps this from happening is simple to state and hard to hold: extend through plugins and the documented APIs, never by editing core. If a requirement cannot be met that way, treat it as evidence about the fit of the platform rather than as a reason to reach for the core files.
Is there a middle path?
Often, and it is underused. Moodle speaks LTI, which means it can act as a tool provider or consumer alongside software you own.
A workable split: keep Moodle for course delivery, assessment, and content — the parts where it is genuinely excellent and where standards compliance matters — and build the institution-specific layer as your own application. Admissions, fees, attendance, parent portals, and reporting live in your system; the two connect over LTI and a defined data contract.
You get the gradebook and quiz engine you would otherwise spend a year rebuilding, and the enrolment and fee workflow that Moodle was never going to fit. The cost is one integration to design carefully and maintain, which is a much smaller commitment than either extreme.