Build vs buy an LMS: what each really costs you
Building an LMS looks cheaper on a spreadsheet than it is in year three. Four common myths about building, open source and SaaS, what each one misses, and a plain rule for picking a build, a SaaS plan or a licensed self-hosted LMS.
On this page
Buy, unless the learning platform is the product you sell or your process is so unusual that nothing on the market fits it. For most training teams the real choice is between renting a SaaS LMS and licensing one you run on your own server. Building from scratch wins in a narrow set of cases, and the build cost is rarely the part that hurts. The upkeep is.
This is for anyone weighing a custom build against an off-the-shelf platform: an L&D lead, a training company owner, a CTO with a spare developer. It's not for someone who needs a course online by Friday. Pick a hosted plan and move on.
A note on interest: Cloudgramam sells a self-hosted LMS on a per-domain licence, so one of the three options below is ours. I've written down where the other two win, and our prices sit in a separate post so this one stays about the decision.
Is building your own LMS cheaper in the long run?
Usually not. A custom LMS swaps a licence or subscription fee for a permanent maintenance bill, and the bill keeps coming after the first release ships.
I know this from our own code. Cloudgramam LMS started as a build for one client. The first version had courses, lessons, sign-in and progress. Then the list grew, because every buyer's checklist grows. Today the README lists six lesson types (article, video, PDF, quiz, assignment and SCORM package), SCORM 1.2 and 2004, xAPI and cmi5, three payment providers (Razorpay, Stripe and PayPal), GST tax invoices with credit notes, single sign-on over both OpenID Connect and SAML 2.0, SCIM provisioning, a REST API, signed webhooks, certificates with QR verification, recertification, deadlines and reminder emails, and a backup script with a restore check.
Each of those is a feature someone asked for after launch. Each one also has to keep working when a payment provider changes its API, when a browser changes how it handles cookies in frames, or when a security fix lands in a library you depend on. If you build, that work never ends, and it lands on whoever wrote the code. When that person leaves, it lands on someone who didn't.
Can a custom LMS really be built in three months?
A course player with sign-in and quizzes, maybe. An LMS your buyers will accept, rarely, because the hard parts are standards and edge cases rather than screens.
SCORM is the clearest example. Uploading a package and saving the score is the easy half. The SCORM 2004 sequencing rules are the hard half, and we've been honest about our own position: we apply one sequencing rule (a course marked as linear opens each part only after the one before it is done) and ignore the others, and the package support has not been through ADL certification. That's after a lot of work. Explained in plain terms in SCORM vs xAPI vs cmi5.
Ask whoever quotes you three months which of these they've counted: password reset and email verification, two-step sign-in for administrators, rate limiting, private file storage, refunds that also fix your tax records, time zones on live class times, and what happens to a learner's progress when you edit a course they're halfway through. None of these show up in a demo. All of them show up in support tickets.
Is open-source LMS software free?
The licence is free. Running it isn't. Moodle, the best-known open-source LMS, is released under the GNU GPL, so there's no licence fee to download, run or change it.
The cost moves to people. Moodle ships a major release every six months, in April and October, according to its release page. Its upgrade guide says to test on a copy first, back up the code, data folder and database, and check that every plugin has a version for the new release. Both were checked on 13 November 2026. That's a recurring job for someone on your team, twice a year, plus the plugins that hold your site together.
To be fair to Moodle: if you already have a person who runs it well, staying is often the cheapest choice. We cover when to stay and when to switch in Moodle alternatives.
Does a SaaS LMS mean you're never locked in?
You're not locked to a server, but you can be locked to a price and a data format. The lock-in in SaaS is quieter: per-learner pricing that rises as you grow, and learner history that's hard to take with you.
Before you sign, ask three things. Can you export completion records and certificates for every learner, in a file you can open? Do you keep the original SCORM or video files, or only the copy inside the platform? And what does the price become at three times today's learner count? If the answers are vague, the switching cost is higher than it looks.
Licensed self-hosting has its own form of lock-in, and you should know it up front. Our software runs only on the domain or domains named in a signed licence file, so moving to a new domain means a new licence file from us. The upside is that the data sits in your own MySQL database on your own server, the backup script writes dated copies you control, and the REST API lists courses, learners and enrolments for any system you want to feed. The full trade-off is in SaaS vs self-hosted LMS.
Which option should you pick?
Pick by who you want carrying the upkeep and how your learner count will move over three years. The table puts the three options side by side.
| Option | Choose it when | Wrong for | Who carries the upkeep |
|---|---|---|---|
| Build from scratch | The LMS is the product you sell, or your workflow fits no existing platform, and you'll fund a developer for years | Teams that want training running this quarter, or have no in-house developer to keep | You, forever |
| SaaS LMS | Learner count is small and stable, you want no server at all, and the vendor's features cover you | Fast-growing learner counts on per-user pricing, or rules that data stays on your own server | The vendor; you pay for it in the subscription |
| Licensed self-hosted LMS (such as ours) | Learner count is large or growing, you want the data on your server, and you need things like Razorpay with GST invoices, SSO or SCORM without a plan upgrade | Anyone with nobody to keep a server patched, or who won't pay a provider for one | Shared: your hosting provider runs the server; we install the software and provide security updates and optional monitoring, as set out in our pricing guide |
A hybrid also works. Some teams license a platform and pay for custom features on top, which gets them their unusual workflow without owning sign-in, payments and standards. With our licence, new features and custom work are quoted separately; the LMS pricing guide lists what the licence, setup and optional monitoring cost.
How do you test the decision before you commit?
Write your three-year learner count on paper first, then price all three options against that number, not today's. A choice that looks cheap at 200 learners can be the expensive one at 2,000.
Then try the software. Our live demo lets you click through the learner side, and the Cloudgramam LMS page lists what's included. If you're still leaning towards a build, take your must-have list to the demo and tick off what's already there. Whatever's left is the real size of your build. For the wider picture, start at our self-hosted LMS guide.