Opigno vs Drupal LMS: Which Open-Source LMS for Hong Kong?
Opigno Community and Opigno Enterprise differ sharply from Drupal LMS. We compare the forks, the licensing, the module ecosystems and which one fits a Hong Kong enterprise or school.
Key facts about this comparison
- Are Opigno and Drupal LMS the same?
- No. Drupal LMS began as a fork of the Opigno distribution and was rewritten from the ground up for Drupal 10.3 and above.
- Is Opigno still free?
- Opigno Community is free and open source. Opigno Enterprise is a separate commercial product sold under a commercial licence.
- What does Drupal LMS cost?
- HK$0 licence fee. No per-seat charge and no annual renewal. Hosting, configuration, integration, content and administration are quoted separately.
- Who maintains Drupal LMS?
- Tag1 Consulting, with initial and ongoing development from the American Federation of Teachers. 208 reporting sites on drupal.org.
- Which content standards are supported?
- SCORM 1.2, SCORM 2004, xAPI with a minimalistic LRS, H5P, and YAML course packages.
- Who is this page for?
- Hong Kong enterprises and schools deciding between Opigno, Drupal LMS and commercial LMS platforms.
Two projects that share an ancestor
If you have evaluated open-source learning platforms in the last few years, you will almost certainly have met both Opigno and Drupal LMS. They look and behave similarly. They are also not the same thing, and the difference matters more than most comparisons admit.
The history is short and recent. Drupal LMS began as a fork of the Opigno distribution. That means it started life as a copy of Opigno with the intent to diverge — and it did. As stated on the project page, Drupal LMS "has been rewritten from the ground up based on Drupal 10.3 and above." Opigno, meanwhile, continued on its own path and now offers two very different products under one name.
Opigno Community and Drupal LMS are both free and open source. Opigno Enterprise is a separate commercial product built on new technology. If you are evaluating "Opigno" as an open-source option, you are evaluating a project that your Hong Kong vendor has already forked.
Community vs Enterprise: a fork in the road
Opigno today positions itself across two editions, and it is worth being precise about the gap between them.
| Opigno Community | Opigno Enterprise | |
|---|---|---|
| What it is | The free, open-source Drupal-based LMS | A commercial Learning Intelligence Platform |
| Technology base | Drupal-based | Built from the ground up on newer technology |
| Cost | Free, no licence fee | Commercial licence, price not published |
| Core idea | Robust LMS for delivering and administering training | Detect capability gaps, deploy learning, verify competence, re-measure |
| AI | Not the product focus | Agent suite, governed AI, coaching agent |
| Multi-tenancy | Standard Drupal patterns | Advanced, per-tenant content, roles, languages, compliance rules |
| Content standards | SCORM, xAPI | SCORM 1.2 and SCORM 2004 explicitly stated |
| Deployment | Self-hosted | On-premise, dedicated cloud, or customer-selected jurisdiction |
| Compliance posture | Depends on your own configuration | ISO 27001, GDPR, SOC 2 stated |
That last column is not a minor difference. Opigno Enterprise is described as a platform that can run on your infrastructure, in a jurisdiction you choose, using your own LLM, with your workforce data staying in the location you specify. Those are enterprise procurement requirements, and they are real requirements — but they come with a commercial licence and, in practice, a commercial relationship.
The genuinely interesting capability in Enterprise is the agent suite: a Learner Intelligence Agent, Corporate Context Agent, Content Generation Agent, Pedagogical Agent, Coaching Agent (Clara), Localization Agent, Administrative Agent, coordinated by an Orchestrator — plus an Agent Builder where administrators describe agent behaviour in plain language. The governance model is notable: your team decides what agents can see, what they may act on, where they must stop, and when a human is required.
One boundary condition is worth quoting, because it is the kind of thing vendors rarely state plainly: skills data is not used as an input to performance management. If you are evaluating any AI-driven LMS, that is a question to ask of every vendor.
The Drupal LMS module ecosystem
Drupal LMS is not a monolith. It is a set of small contributed modules you enable as needed, each doing one job well. The published ecosystem is:
| Module | What it does |
|---|---|
| <strong>LMS Membership Request</strong> | Requires students to request membership on selected courses instead of enrolling freely |
| <strong>LMS File Upload</strong> | Adds a file-upload activity type |
| <strong>LMS Webform</strong> | Lets you use Webform forms as LMS activities |
| <strong>LMS Certificate</strong> / <strong>LMS Certificate Entity</strong> | Generate PDF certificates for completed courses |
| <strong>LMS Messages</strong> | Integrates with the Message module to send notifications on LMS events |
| <strong>LMS YAML</strong> | Export and import courses as zip packages of YAML files |
| <strong>LMS Xapi</strong> | Imports xAPI packages, provides an activity-answer plugin and a minimalistic LRS for scores and states |
| <strong>LMS H5P</strong> | Integrates Drupal H5P — access to the open-source interactive activity library |
| <strong>LMS SCORM</strong> | Adds SCORM package support |
| <strong>LMS Migrate</strong> | Migration plugins and templates for moving from Opigno to Drupal LMS |
The activity types available inside a course are worth knowing, because they determine what an assessment can actually ask: file_upload, free_text, free_text_feedback, no_answer, select_multiple, select_multiple_feedback, select_single, select_single_feedback, true_false, true_false_feedback, webform and xapi_tincan.
Underneath sit custom entities for lms_activity, lms_answer, lms_lesson, lms_course_status and lms_lesson_status, plus lms_course and lms_class group types. Progress tracking is therefore a first-class modelled concept rather than something bolted on with reports — which is exactly why an HK school can track a student across years without a licence conversation.
Licensing and cost in Hong Kong terms
Both projects are GPL open source. Neither charges a licence fee. That matters enormously in Hong Kong, where a school district with 1,200 students or an enterprise with 8,000 staff would otherwise face a per-seat line item that has to be justified to finance.
But "free licence" is not "free". The real cost sits in hosting or cloud infrastructure, configuration, integration work, content development, and the people who administer it. For most Hong Kong organisations the honest comparison is against Opigno Enterprise or a commercial LMS licence, not against zero. Open source wins when you already have technical capacity or are prepared to buy that capacity; it loses when you do not.
It is also worth noting the scale data point: Drupal LMS reports 208 sites using the module on drupal.org, with development led by Tag1 Consulting and the American Federation of Teachers. That is a meaningful institutional signal for a school-sector buyer — this is not an abandoned hobby project.
Which one should a Hong Kong organisation pick?
| If you… | Then… |
|---|---|
| Are a Hong Kong school or SME with no in-house IT team | Drupal LMS + managed hosting. Lowest entry cost, and the ecosystem covers assessment, certificates and messaging out of the box |
| Are a regulated enterprise that needs contractual SLA and vendor accountability | A commercial platform. The open-source route requires you to own uptime yourself |
| Need capability verification and AI coaching as the primary product | Opigno Enterprise is designed for that. Just budget for the licence and the relationship |
| Already run Opigno and want to stay Drupal-native | Stay on Opigno Community, or plan a migration to Drupal LMS via the LMS Migrate module |
| Must keep data inside Hong Kong under the PDPO | Either self-hosted Drupal LMS, or Opigno Enterprise with customer-selected jurisdiction — both can do it, only one is free |
| Want tri-language content: English, 繁體中文(香港), 简体中文 | Drupal LMS with a Hong Kong build. Confirm the language workflow before committing |
Our own position is worth stating plainly: we build on Drupal LMS because its modular structure lets a Hong Kong school or enterprise enable only what it needs, and because the fork is far enough from Opigno that the ecosystem moves at its own pace. We are not in the business of reselling a commercial licence.
Migrating between them
Because Drupal LMS was forked from Opigno, the data model is broadly recognisable to anyone who has administered Opigno. The ecosystem ships LMS Migrate specifically for this: migration plugins and template examples for moving from Opigno to Drupal LMS.
In practice, expect the content to move more easily than the configuration. SCORM and H5P packages are portable by definition; course structure, roles and approval workflows usually need re-mapping because the entity model was rewritten for Drupal 10. Budget for a data migration workshop before quoting a fixed price — that is the work that decides whether the migration lands on time.
The platforms that lock you in are rarely the ones that lock the content. Content standards are open; configuration is where the lock lives.
Questions about Opigno vs Drupal LMS
Is Opigno still being maintained?
Opigno Community and Opigno Enterprise are separate products with different licensing and different maintenance trajectories, and they have diverged from Drupal LMS — which began as a fork of the Opigno distribution and was then rewritten from the ground up for Drupal 10.3+. The article works through where each one actually stands, and we would encourage you to check the current upstream release notes as well as reading our summary of them.
Which has the larger module ecosystem?
Drupal LMS sits on Drupal itself, and inherits Drupal's very large contributed module ecosystem — which is the single most important practical difference for an organisation that will need to extend the platform. The article covers the module landscape in detail, module by module.
Which one is right for a Hong Kong school?
The deciding factors are usually who will maintain it, whether you need per-student economics to work, and whether the school needs to run content authoring in-house. For a school with a limited technical team, the maintenance question tends to dominate, and the article says so rather than pretending the comparison is purely technical.
Is migrating from Opigno to Drupal LMS difficult?
There is a dedicated LMS Migrate module with migration plugins and template examples, and courses can be exported and imported as YAML zip packages. The difficulty is not usually the export — it is the assessment data and the reports you need to keep working afterwards, which is where scoping effort belongs.
Do you use Opigno yourself?
No. We run Drupal LMS. Opigno appears in our articles because it is the most common point of comparison for people evaluating open-source LMS platforms in Hong Kong, and because a fork relationship is genuinely confusing when you are choosing.
Evaluating Drupal LMS for your organisation?
Tell us your current platform, your learner numbers and the reports you need. We will show you a Drupal LMS deployment configured around them — and tell you honestly if we are not the right answer.