The hidden cost of a free LMS — hosting, setup, theming, integrations, upgrades, and admin time — and why owned Moodle still wins over five years.
Got an LMS decision on your plate?
45-minute call. Plain-English audit. Fixed-price quote if there's a fit, or a "no" if there isn't. No deck. No pitch.
Moodle's license is free, but the real bill is hosting, build, theming, and support — and it still beats per-seat SaaS at scale.
Every line item in an LMS budget over five years, compared across rented SaaS and a platform you own outright.
The half-FTE hiding in your LMS budget — what it costs, and how the right platform cuts it.
The hidden cost of a free LMS is the gap between "free to download" and "free to run" — and for open-source platforms like Moodle, that gap is the entire budget. The license genuinely costs nothing; you can download Moodle today and pay no one for the software. But software that no one hosts, configures, themes, integrates, upgrades, or administers does not train anyone. Those line items are real money, and pretending they are zero is how L&D and IT leaders end up with a budget that misses by six figures over five years.
This is not an argument against free open-source software — it is an argument for costing it honestly. This guide walks the real line items behind a "free" LMS: hosting, implementation and configuration, theming, integrations, maintenance and upgrades, and internal admin time. Then it makes the balanced case: those costs are real, but a well-run owned Moodle is still typically cheaper over five years than per-seat SaaS at scale — and you own it outright. Because Aquilon builds platforms organizations own, the honest framing is the one we lead with: free to license, not free to run.
Moodle, the most widely used open-source LMS, is free in a specific and real sense: it is released under an open-source license, so there is no per-user fee and no subscription to use the software itself. That is a genuine advantage, and it is the reason the per-seat math eventually favors ownership. But "free to license" is not "free to run," and conflating the two is the single most expensive mistake in an open-source LMS budget.
Every LMS — free-licensed or not — needs a server to run on, someone to set it up, a design that reflects your organization, connections to your other systems, ongoing patching, and people to operate it day to day. A SaaS subscription bundles all of that into one recurring invoice, which is why it feels simpler even when it costs more. With a free-licensed platform, those costs are unbundled and visible. Unbundled is not the same as absent. Our full LMS total cost of ownership breakdown puts every category in one model; here we focus on the ones the word "free" hides.
Here is where the money actually goes on a "free" LMS, with rough shape so you can build an honest model.
Free software still needs somewhere to live. A self-hosted Moodle runs on cloud infrastructure you pay for — compute, storage, backups, a CDN for content delivery, and monitoring. This is a modest but real ongoing line that scales with how many people use the platform and how much video and content it serves. The upside of owning it is control: it is your cloud account, so you right-size it and keep data-residency decisions in-house.
Someone has to install the platform, configure it to match how your organization actually works — roles, categories, enrollment rules, multi-site structure — migrate existing content, and test it before launch. This is a one-time project cost, not a recurring one, and it is where a platform configured to fit your sites pays back later in reduced admin time.
Out of the box, an open-source LMS looks generic. A branded, accessible theme that reflects your organization and meets accessibility requirements is a design and development task. It is mostly a one-time cost with occasional refreshes, but it is not zero, and skipping it shows.
The connections that make an LMS useful — single sign-on, HRIS provisioning, video hosting, reporting into your BI tools — are build work. The good news, and it is a real contrast with SaaS, is that on an owned platform these are built once and belong to you, with no per-connector fees and no single sign-on locked behind a premium tier.
Security patches and version upgrades are the price of running any web platform responsibly. For a free-licensed LMS this is a predictable recurring line — a support and maintenance arrangement that keeps the platform patched and current. It is real, but it is a fixed, plannable cost rather than an upsell ladder.
This is the line almost every "free LMS" budget omits, and it is frequently the largest ongoing cost of all. Enrolling learners, building and running reports, chasing down incomplete compliance training, managing users across sites — those hours belong to real people on your payroll. A half-FTE of coordinator time is meaningful money every year, and it accrues whether the software was free or not. We size this properly in our guide to the true cost of LMS admin time, because it deserves a real number rather than a shrug. The mitigating factor: a platform configured to automate enrollment and reporting cuts this line substantially, while a poorly configured one inflates it.
Here is the part that keeps this honest in both directions. Yes, the costs above are real, and anyone who sells you "free Moodle, no strings" is misleading you. But when you total those line items and project them across five years, a well-run owned Moodle is still typically cheaper than per-seat SaaS once you are at any real scale — and it has a structural advantage SaaS cannot match.
The reason is the shape of the cost. SaaS cost scales with headcount and rises at every renewal; add a site or a seasonal cohort and the bill climbs. A free-licensed, owned platform front-loads the build and then flattens, because there is no per-seat fee — your platform cost does not move when you add 50 people. For a mid-market firm past a couple hundred users across multiple sites, those two curves cross inside the five-year window, and the gap widens the longer you keep the platform. For the specifics on where Moodle's own costs land, see how much Moodle really costs.
And then there is the part no spreadsheet line fully captures: you own it. No renewal uplift, no vendor holding your data as leverage, no per-seat tax on growth, and no exit fee to leave — because there is nothing to exit. The honest verdict is not "free LMS is a myth" and it is not "free LMS is free." It is: free to license, real to run, and still the better five-year deal at scale, with ownership on top.
Build the model in three passes:
Do that and two things become clear at once: a free LMS is not free, and it is still very likely the cheaper, and better-owned, choice for a multi-site firm at scale. Both statements are true, and a budget that acknowledges both is the one that survives finance review.
The software license is genuinely free — no per-user fee, no subscription for the software itself. What costs money is running it: hosting, setup, theming, integrations, upgrades, and admin time. Free to license, not free to run.
Internal admin time. The hours staff spend enrolling learners, running reports, and chasing completions rarely appear in a "free LMS" budget, yet they are often the largest ongoing cost. Good configuration reduces this line significantly.
Because at scale it is usually still cheaper to own. SaaS cost rises with headcount and renewals; an owned platform front-loads the build and then flattens with no per-seat fee — and you own the platform and data outright.
List every line item, separate one-time from recurring costs, and project across five years against SaaS with a realistic renewal uplift. The TCO calculator does the math live once you have your headcount and growth assumptions.