What is an LMS and what does it do?
An LMS (Learning Management System) is the central place where you deliver learning content, track progress, administer assessments and record proof of competence. For trainers and HR it is what an ERP is for finance: the system of record for everything to do with development.
That sounds simple, but in practice it gets messy. An LMS often has to serve at the same time as a content library, assessment engine, certificate issuer, record tracker, integration hub to HR systems, communication platform between teacher and learner and, increasingly, a place where AI functionality lands. When you buy one, you are not just choosing software but a foundation for years of learning rollout.
So the crucial question is not "which LMS is best?" but "which route fits our type of learning, our processes and our compliance context?". Broadly, there are two answers: an off-the-shelf LMS, or a custom LMS built around your specific learning objectives.
An off-the-shelf LMS covers a broad range of standard course needs with minimal set-up. Custom pays off once the learning process itself is a differentiator, or once sector compliance, roles and integrations become too complex for the standard features.
The off-the-shelf landscape: who offers what?
The packaged LMS landscape is mature. A handful of players have won a firm place in each segment. We're not claiming any one is best: they suit different contexts.
Moodle
Open-source and widely adopted in vocational (MBO), higher professional (HBO) and university (WO) education, as well as in non-profit settings. Modular via plugins, strong community, low licensing pressure. A Moodle implementation rarely works truly out of the box: hosting, plugin management and stable upgrades all need attention. The quality of the plugin marketplace varies.
Canvas
Commercial, popular in higher education and in parts of the business world that want a higher-education look and feel. Clean UX, a smooth onboarding process and a reasonably well-documented API. The licensing model is per active user, which adds up with large populations.
itslearning
Strong position in Dutch primary and secondary education. Curriculum-focused, built to tie together course material, method integrations and teacher workflows. Less common outside the primary and secondary education segment.
TalentLMS
Cloud LMS for corporate L&D at small and medium-sized businesses. Quick to set up, reasonable licences, solid SCORM support. Customisation is possible within the platform's limits, but beyond them you hit a wall.
Docebo
Enterprise-oriented platform with strong AI positioning and extensive configuration options. Suits organisations with multiple business units, complex roles and large content libraries.
Cornerstone
A veteran in talent management; the LMS is one module of a broader suite that also covers recruitment, performance and succession. Suitable for organisations that want to tie L&D fully into their HR stack.
What they have in common
They are all generic packages, designed to be usable for a broad audience. That is their greatest strength and their greatest limitation: as soon as your learning process structurally deviates from what the package models, you either end up fighting the tool or building a separate add-on.
What exactly is a custom LMS?
A custom LMS is not a "package we've tuned a bit". It is software written for you, on its own codebase, with data models and roles derived from your learning process rather than from a generic learning paradigm. You own the source code, you set the pace of further development, and your integration architecture is a design choice rather than an accidental remnant of what the vendor offers.
A good implementation builds on standards: SCORM 1.2 and 2004 for classic courseware, xAPI (Experience API) for broad learning-activity tracking, cmi5 for modern package exchange, and LTI 1.3 for embedding external tools, so content from other sources remains interchangeable. A custom LMS that ignores all these standards eventually turns itself into a lock-in machine, only with your name on it.
Custom comes in different flavours: a fully custom platform, a layer on top of an open-source core such as Moodle (the core handles the courseware engine, while the UX and roles are entirely your own), or a hybrid with authoring and delivery in a package and progress and records in a custom back end. Which flavour fits depends on where in the stack your differentiating strength lies.
TCO and ownership: look beyond the licence
The biggest mistake in LMS selection is looking at the licence instead of at total cost of ownership. A packaged LMS shows a per-user or per-tenant price and looks predictable. Custom requires an upfront investment and looks expensive. In the very short term that picture holds; over the timeframe that usually matters, not always.
What packaged TCO underestimates: licence escalation as users and modules grow, plugin maintenance (especially with Moodle), customisation work within platform limits, implementation partners who have to keep up with every release, and workaround systems because the LMS can't handle one particular process.
What custom TCO underestimates: active maintenance after go-live, security patches, platform changes and an ongoing development budget to keep pace with your L&D strategy. If you invest in custom and then let it age, you pay again.
If you offer commercial training courses or want to serve large learner volumes with strong branding, a route towards a training app or your own learning platform is structurally often cheaper than a licensing structure that grows with every participant.
Room for customisation: where is the wall?
Every packaged LMS offers customisation. The question is how far it goes. On most platforms we're talking about branding (colours, logo, limited typography), reporting fields, and setting up your own learning paths within the existing course structure. That covers a lot.
Where the wall sits differs from package to package. It gets harder as soon as you want something the platform's data model doesn't know. A genuine parent/student/teacher triangle with overlapping roles. A competency record that follows compliance requirements rather than course completion. A learning path that adapts to signals from another operational system. A meeting of serious gaming and formal certificate evidence. This is where packages get stuck: either the plug-in doesn't exist, or the plug-in does "do" it but can't be maintained sustainably.
A nuance we often hear: "we'll start with a package and build custom around it". That can be an excellent route, provided you acknowledge up front that in time the package will no longer lead, but your extension will. That moment calls for an honest conversation about which is the main component. We describe this trade-off in more detail on the page about custom LMS development.
SCORM, xAPI, cmi5, LTI: which standards do you need to know?
A good conversation about LMS choices stands or falls with the standards. Four terms that every decision-maker should be able to place in broad terms:
SCORM 1.2 and 2004
The classic packaging standard for courseware. Your authoring tool (Articulate, Storyline, Captivate, iSpring) publishes a SCORM package; the LMS records progress and score. 1.2 is simple and limited; 2004 adds sequencing and better reporting. Almost every LMS reads SCORM.
xAPI (Experience API, "Tin Can")
A much richer model for tracking learning activity: not just "completed or not" but "this learner, this action, this object, this context". It lets you record learning outside a formal course too: on-the-job moments, videos watched, simulations played. You need an LRS (Learning Record Store) to store and query it all.
cmi5
The bridge between SCORM and xAPI: the same packaging paradigm as SCORM, but running on xAPI events under the hood. Slowly being adopted by authoring tools and modern LMSs; often the practical next step.
LTI 1.3
Not a content standard but an integration standard: how an LMS securely embeds external tools (assessment tool, video platform, AI tutor). It standardises single sign-on and score exchange between platform and tool. Indispensable if you're linking ecosystems together.
Almost all packaged LMSs claim "SCORM and xAPI support". In practice it varies. Test every flow you need before you sign, with a real package, a real LRS integration and a real LTI integration. With custom development, these standards are not a marketing claim but a design choice.
GDPR, EU residency and audit trails
LMSs process personal data almost by definition: names, dates of birth, learning results, certificates, sometimes sensitive competency records. For healthcare, pharma and parts of education, this means special category personal data or data with an elevated legal basis.
Data processing agreement and sub-processors
With a SaaS LMS, the vendor processes your data. The DPA should settle this watertight, including a list of sub-processors. For some sectors, "outside the EU" is a blocker.
EU residency
The question of where the data is physically stored is no longer technical but legal. Schrems II placed US storage under strict conditions. EU-only is technically feasible on any modern platform, but not every packaged vendor offers it by default. With custom development, it's a design choice you control yourself.
Audit trail
Healthcare and pharma require immutable logs: who changed what, when, on which record? Append-only records that stand up to an inspection. A packaged LMS sometimes offers this through an audit module or plug-in, sometimes not. Custom development makes it a first-class citizen of the system.
Accessibility and the EAA
The European Accessibility Act sets requirements for digital services with an educational component, and WCAG AA has long been mandatory for public institutions. An off-the-shelf package that isn't WCAG-compliant gives you limited levers to fix that quickly; with custom development, accessibility is a design choice.
The AI Act and adaptive learning
In certain scenarios, adaptive learning paths built on machine learning fall under the AI Act's high-risk categories, particularly systems that assess learners or influence access to further education. That requires documentation of training data, model explainability and human oversight. With custom development you control those settings yourself, which is both a burden and an advantage.
Integration freedom: how well does the system talk to everything else?
An LMS rarely stands alone. It connects to HR systems, SSO providers, data warehouses, payment platforms, community platforms and CRMs. The quality of those integrations determines whether the LMS makes the working day smoother or becomes a second silo.
Off-the-shelf LMSs offer integration on three levels: built-in connectors for well-known HR and SSO vendors, their own API, and marketplace integrations via partners. That is enough for standard integrations. It gets difficult as soon as you want to connect something atypical: an industry association registration, a legacy HR system, or your own data platform with non-standard identifiers. With custom development, integration architecture is a design choice from day one rather than a fallback option, and event-driven integrations and data flows to a privacy-hardened data platform become part of the design.
Vendor lock-in: code ownership and exit paths
Lock-in isn't a dirty word; it's a trade-off. Every off-the-shelf LMS involves some degree of lock-in. The question is how deep it goes and what the exit costs. There are three layers to distinguish:
- Content lock-in: content that only exists in a proprietary format is hard to export. SCORM/xAPI export is your friend. Ask about export paths before you sign.
- Data lock-in: progress data, certificates, competence records. Ask for a data portability clause and a testable export procedure.
- Process lock-in: the habits and workflows built around the system. These cost more to move than the licence itself.
Custom development shifts the lock-in: no longer to a vendor, but to your build partner and your own codebase. Code ownership is not a detail here. A serious build partner delivers the source code, a transparent deployment pipeline and documentation that another party can pick up. That is the real exit route with custom development: the work can be continued by another team of developers without you having to start over.
Performance, scalability and peak load
Most off-the-shelf LMSs run stably under normal load. It gets interesting at peaks: exam periods, the simultaneous start of a new cohort, or a media-rich training course suddenly opened by thousands of people at once. Custom development gives you control over the architectural choices that determine peak performance: CDN distribution, separate read and write paths, asynchronous score processing. That requires a team that can make those choices, but the room to do so exists, which is rarely the case with an off-the-shelf package.
Scalability also has a less visible side: cost scalability. A package that charges per user gets more expensive as you succeed. A custom system on your own infrastructure or on a hyperscaler with flexible pricing decouples user numbers from your cost structure. For commercial training providers with large learner volumes, that is an important difference.
Sector choices: corporate L&D, education, healthcare, pharma
The right choice differs greatly by sector. Here are a few typical patterns we come across.
Corporate L&D
For broad staff training, compliance courses and onboarding, an off-the-shelf LMS (TalentLMS, Docebo, Cornerstone) is often perfectly fine, provided your organisation is standard enough in its processes and reporting needs. Custom development pays off once L&D is intertwined with operational KPIs, or once your organisation offers commercial training to external parties with its own branding and payment flows.
Education: primary, secondary, vocational, higher professional and university
In primary and secondary education, itslearning and Magister-style packages dominate, often linked to publisher platforms. In vocational, higher professional and university education, Canvas or Moodle is the norm. Custom choices there rarely concern the entire LMS; they more often involve an additional layer (mentor workflows, exam monitoring, parent portals) with LTI integration to the existing package. Our background in education app development shows what that hybrid looks like in practice.
Healthcare: competency register
Here the story changes. A competency register is not a course tracker but a records system that connects to functional assessments and quality audits. Off-the-shelf LMSs can offer a layer, but most healthcare organisations end up building an extra layer on top of or around them. Audit trail requirements, integration with HR competency procedures and links to inspection frameworks often make custom development the pragmatic route.
Pharma compliance training
GxP training, GMP instructions, computer system validation protocols: here, learning activity must be traceable, validatable and revision-proof. Some enterprise packages (Cornerstone, ComplianceWire) cover part of this, but many organisations build a shell around them for their specific SOP set and validation flow. Custom development makes that shell part of the core system instead of a separate tool.
When an off-the-shelf LMS is enough
Our pragmatic test: choose an off-the-shelf package if you can agree with three of the statements below.
- Our courses have a standard structure: theory, video, test, certificate.
- Our division of roles is simple: learner, teacher/manager, administrator.
- Our branding requirements go no further than a logo and a house colour.
- Our integration needs are limited to SSO, HR and possibly a payment platform.
- Our compliance context is standard GDPR with no additional sector framework.
- Our learner population is stable in volume.
In that case, you would be short-changing yourself by spending money on custom development where it isn't needed. An off-the-shelf LMS rolls out faster, costs less budget in the short term and delivers most of the value of the system a team actually needed.
We do advise one thing: don't adopt the package in isolation. Make sure SSO is set up properly from day one, that export routes to your data platform are in place, and that the authoring environment is independent of the package. That keeps a later migration feasible.
When custom development pays off
Custom development pays off once the learning process itself is part of what makes your organisation distinctive, or once the limits of an off-the-shelf package force you into workarounds that become more painful every year. In practice, we see these patterns come up again and again:
- Commercial L&D providers who deliver white-label training to multiple clients and need to separate brand, content and user boundaries cleanly, something an ordinary package rarely handles well per tenant.
- Extended parent/student/teacher roles where overlapping read and write permissions at record and learning-material level are the norm (think primary and secondary education with parent portals, or healthcare with mentor competency).
- Specific process integrations in healthcare and pharma where the learning activity is a formal piece of evidence in an audit trail.
- A combination of SCORM, xAPI and LTI in a single learning journey, with external tooling that has to plug in seamlessly and feed data back.
- Game-based learning as the core, not a gimmick: learning progress that comes from interaction in a simulation or serious game rather than from clicking through videos.
- An AI tutoring layer that works across your entire content library, with data governance you don't want to leave to a vendor.
- Large learner volumes where per-user licences get out of hand and your own infrastructure offers a better cost structure.
- Strict EU residency or sovereignty requirements that not every off-the-shelf vendor meets by default.
Not every pattern means "start from scratch". Sometimes the route is a layer on top of an open-source core, sometimes a hybrid with an off-the-shelf package for delivery and a custom back end for records. That is what a serious preliminary discussion about custom LMS software maps out: "which route for each layer of the stack".
The AI tutoring layer: new, fast-moving, loaded
One topic that comes up in every LMS conversation is the AI layer: adaptive learning paths, content recommendations, AI tutoring, automatic assessment of open answers. Vendors deliver AI features in separate modules, often built on an external model API. That works fine for general tutoring, but less well once you want AI to work on your own specific content or records while keeping control over governance, costs and quality. With a custom build, you can create your own retrieval layer that works with your content, with logging, evaluation and compliance control.
Not every AI feature is worth a big investment. A chatbot that answers questions about a handbook fits within any modern LMS via an LTI integration. An AI tutor that assembles adaptive learning paths based on evidence in your xAPI LRS is a different game, and that is exactly where a custom architecture becomes valuable.
How to decide: a workable process
No flowchart can make this decision for you. What does work is a four-step process.
1. Write down the learning process, not the tool
Don't start with a vendor shortlist. Start with a document of a few pages describing what learning looks like in your organisation: who learns what, why, how learning is proven, who sees which data, which laws and standards apply, and which other systems are involved. That document is the touchstone against which you test every tool.
2. Do an honest fit analysis
Hold that document up against the packages that are serious contenders in your segment. Not "what does the website say?" but "what does the system do when we want to run this specific process in it?", preferably with a proof of concept on real data. Seriously testing three packages takes work, but it often saves you from a wrong choice.
3. Make the custom question concrete
If packages don't add up, describe what the custom layer would need to do, more specifically than "our own LMS". Which modules, which roles, which integrations, which compliance choices? The less vague you are, the easier it is for a serious development partner to give a sound estimate.
4. Plan for evolution, not for an end state
LMS choices are rarely made once and for all. Plan in phases: a minimum viable version first, get it into production, gain experience, then keep building. That applies to package implementations (don't roll everything out at once) and to custom projects (start with a core and expand based on what works).
For every LMS project, whether off-the-shelf or custom, ask for a testable export procedure. A real data extraction on real data, not just a promise in the DPA. That tells you whether an exit is ever feasible.
Frequently asked questions
Is Moodle free?
The software is open source with no licence fees. Hosting, plugin maintenance, customisation and stable upgrades are not free. For mid-sized organisations, Moodle's TCO can rise to amounts comparable with commercial packages, but you do retain ownership of the direction.
Can a custom LMS use SCORM content?
Yes. A well-built custom LMS reads SCORM 1.2 and 2004 just like an off-the-shelf package. That is precisely the point of standards: they make content portable. The same goes for xAPI and cmi5. If you are considering a custom solution, you don't lose content investments made in standards.
What is the difference between an LMS and an LXP?
An LXP (Learning Experience Platform) focuses on recommending and discovering content across multiple sources, often based on skills. An LMS is more formal: course, progress, certificate. In practice, the two categories are growing towards each other.
Does LTI 1.3 work with every LMS?
The major packages support LTI 1.3, and some still support LTI 1.1 for backwards compatibility. A custom LMS that implements the standard correctly can embed any LTI-compliant tool or connect as a provider itself. Test it explicitly before you sign.
How does a custom LMS relate to a training app?
A training app is often the mobile, learner-facing side: native UX, offline content, push notifications. A custom LMS is the broader stack beneath and behind that app: content management, reporting, integration, administration. They are often developed together: the app is the shell, the LMS is the engine.
What if we already have an off-the-shelf package and want to switch?
Start with an audit of the three lock-in layers (content, data, process). Plan a parallel track in which the new platform runs alongside the existing one. Handle data migration and certificate transfer explicitly, as that is where valuable evidence would otherwise be lost.
How much does a custom LMS cost?
That depends on scope: the number of modules, roles, integrations, the compliance framework and how you start (greenfield, on an open-source core or hybrid). A figure without context is misleading; a scoping conversation gives a more reliable picture. You can find more background articles in our knowledge base.