Coassemble Moodle Integration: Is the Certified Plugin Worth It for UK Teams?
Coassemble is now a Moodle Certified Integration. We compare it against H5P, SCORM, and the native editor, covering UK GDPR compliance, technical specs, and pricing.
by Cleverson Gouvêa

The Coassemble Moodle integration is now official: on 16 November 2026, Moodle announced Coassemble as a Certified Integration, making it possible to build interactive e-learning modules directly inside your VLE without exporting SCORM packages or requiring learners to manage a second login. In this comparison, I break down what actually changes in day-to-day delivery, how much it costs, and when upgrading makes commercial sense.
TL;DR
- Coassemble joined the Moodle Certified Integration programme on 16/11/2026. The plugin is free and supports Moodle 4.1 through 5.3, running on PHP 8.1 or higher over HTTPS.
- Learners authenticate exclusively using their existing Moodle accounts. Grades, progress, and completion data flow directly into the Moodle gradebook.
- Production deployments require a paid subscription: the entry-level tier starts at US$ 2,500 per year (around £2,000 before taxes), with no per-author seat licence fees. A limited free sandbox is available for testing.
- Course content is hosted on Coassemble's external servers outside your Moodle database. Regional data residency selection is restricted to the top enterprise tier—a significant consideration under UK GDPR.
- For many UK universities, colleges, and training providers, well-configured native H5P remains sufficient. Coassemble pays off primarily when non-technical subject matter experts need to publish high volumes of rapid learning quickly.
What was officially announced vs what remains a promise
The announcement appeared on the Moodle website on 16 November 2026. The following day, Coassemble issued its press release from Sydney, syndicated by Training Industry, followed by coverage in IT Brief Australia on 20 November. Founded in 2015, the Australian EdTech firm positions itself as an "API-first" training platform.
According to the official Moodle announcement and the plugin repository listing:
- once the Coassemble Moodle plugin is installed, the course builder functions as a native course activity directly within Moodle;
- instructors create and edit content in the exact environment where learners study, eliminating intermediate file exports;
- learners do not need an account or separate credentials on Coassemble;
- grades, percentage progress, and completion status synchronise automatically with Moodle's gradebook and activity completion tracking;
- published revisions update immediately for active students without re-uploading packages.
The promised free account tier has not arrived yet
This is where early marketing creates confusion. The press release noted that "later this year", Moodle site administrators will be able to generate a free Coassemble account directly from their site. As of late November 2026, this capability remains roadmap messaging. What currently exists is a free evaluation sandbox with strict usage limits, alongside a mandatory paid subscription for production use, as detailed on the Moodle Marketplace listing.
What "Certified Integration" actually signifies
Certified Integration is Moodle's commercial partnership tier. It does not mean the code has passed an independent on-premise penetration test within your bespoke server architecture, nor is it a baseline requirement for plugins in the directory. In practice, it signifies a formal commercial agreement, verified baseline compatibility, and a coordinated vendor support channel. It serves as a helpful procurement indicator, but it does not replace proper staging and security due diligence.
Under the bonnet: how the Coassemble Moodle integration operates
The plugin is registered as mod_coassemble, released under the GPL v3 licence, and maintained directly by Coassemble. The latest release in the directory dates from 28 October 2026. At the time of review, it showed 5 registered production installs. It is a nascent integration within the broader ecosystem, which IT leaders should factor into their risk assessments.
Technical prerequisites
| Component | Published requirement |
|---|---|
| Moodle version | 4.1 to 5.3 |
| PHP runtime | 8.1 or higher |
| Protocol | Mandatory HTTPS (progress synchronization relies on incoming webhooks) |
| Network connectivity | Server must allow outbound HTTPS access to api.coassemble.com |
| Site settings | Activity completion enabled and embedded content permissions active |
| Authentication credentials | Coassemble workspace API key (one per Moodle installation) |
Outbound network connectivity is the most frequent deployment stumbling block. On hardened servers with restrictive outbound firewalls, or institutions routing traffic through strict corporate proxies, the connection handshake will fail. We regularly encounter this across enterprise VLEs we maintain: the plugin code is fine, but the outbound perimeter rules block the API calls.
Four-step installation workflow
- Deploy the plugin ZIP file via Site administration > Plugins > Install plugins.
- Within your Coassemble admin console, navigate to Developer > API keys and generate a new key (prefixed with
COASSEMBLE:). - Paste the key under Plugins > Activity modules > Coassemble and execute the live connection test.
- Configure user role permissions:
mod/coassemble:addinstance,author,manage, andview. By default, editing trainers and course managers can provision activities.
Coassemble's documentation notes that truncated API keys caused by clipboard formatting errors are the single most common installation issue—a simple trap that can waste an afternoon of an administrator's time.
How completion data feeds back to Moodle
For each learning activity, you can configure whether the recorded grade reflects completion progress or quiz performance. If a learner closes their browser tab before the client-side JavaScript communicates with Moodle, Coassemble dispatches an asynchronous server-to-server webhook directly to your instance. This makes a valid SSL certificate and public HTTPS mandatory; without it, the webhook fails silently and the gradebook records missing marks.
Coassemble Moodle vs H5P vs SCORM vs native resources
The core question for learning technologists and e-learning managers is simple: do we need another commercial authoring tool? The breakdown below benchmarks Coassemble Moodle against standard alternatives using verified public technical criteria.
| Feature | Coassemble (Certified Plugin) | Native H5P | External SCORM (Articulate, iSpring) | Standard Moodle (Page, Book, Lesson) |
|---|---|---|---|---|
| Authoring environment | Inside Moodle via the embedded Coassemble builder | Inside Moodle (Content Bank) | External standalone desktop or cloud app | Inside Moodle natively |
| Content storage location | Coassemble cloud servers | Local Moodle server database/filedir | Local Moodle server (uploaded .zip) | Local Moodle server |
| Content updates | Instant live updates upon publishing | Edit and save instantly | Re-export and re-upload ZIP package | Edit and save instantly |
| Gradebook integration | Yes (progress percentage or quiz scores) | Yes (H5P activity reporting) | Yes (SCORM tracking API) | Yes (Lesson and Quiz modules) |
| Secondary learner login | No | No | No | No |
| AI course generation | Yes (from PDFs, slide decks, SCORM, or text prompts) | No native AI generation | Varies by authoring software | Moodle 4.5+ and 5.x AI subsystem capabilities |
| Licencing fees | Annual subscription in US$ | Zero (open source) | Annual author seat licences | Zero (built into core) |
| Vendor lock-in risk | High | Low | Moderate | None |
Native H5P: the built-in powerhouse
H5P has formed part of core Moodle since version 3.9, offering deep gradebook synchronisation and an integrated Content Bank to share and repurpose modules across multiple courses. Interactive video, drag-and-drop exercises, branch scenarios, timelines, and knowledge checks run directly on your own infrastructure with zero third-party licencing costs. Its primary drawback is authoring ergonomics: non-specialists require initial onboarding. However, for organisations with in-house instructional design support, mature H5P authoring handles the vast majority of digital learning requirements.
Legacy SCORM packages: the friction point Coassemble targets
The traditional digital learning pipeline relies on building modules in Articulate Storyline or iSpring, exporting a ZIP package, uploading it into a Moodle SCORM activity, and hoping tracking handshakes function predictably. Fixing a minor typo requires re-exporting, re-uploading, and occasionally invalidating learner attempt records. This specific operational friction is what Coassemble resolves, and it represents the plugin's most compelling selling point.
Moodle's native resources: frequently underestimated
Standard Page, Book, and Lesson modules comfortably handle structured long-form content, embedded media, and foundational pathways. While uninspiring under vanilla Moodle themes, a modern, well-designed theme paired with consistent corporate layout templates dramatically elevates the end-user experience. Before committing capital to external authoring platforms, evaluate whether your issue is tool capability or the absence of robust visual templates.
The operational impact on content production
With Coassemble Moodle, the primary return on investment lies in process efficiency rather than novelty of features. It removes trainers from the tedious export-upload-test loop and consolidates authoring in the delivery environment. This offers high utility across three operational profiles:
- Non-technical subject matter experts. Compliance officers, clinical educators, or engineering leads building training lack the appetite to learn complex authoring suites. An AI-assisted builder converting source PDFs or slide decks materially lowers the barrier to contribution.
- Corporate training environments with fast-changing content. Health and safety updates, product specs, or regulatory policies that change weekly benefit immensely from instant updates. Those reviewing Moodle Workplace for enterprise training should evaluate this integration alongside their broader capability roadmap.
- Decentralised multi-author departments. Because Coassemble does not charge per-seat author fees, ten or fifty regional contributors incur the same baseline platform cost.
What the integration does not solve
Pedagogical rigour remains the responsibility of your team. An AI-generated module built from an unstructured PDF will simply reflect the deficiencies of the original document. Meaningful learning outcomes, cognitive framing, and valid assessments still require deliberate instructional design.
Furthermore, accessibility compliance remains your legal liability. While Coassemble and Moodle cite alignment with WCAG 2.2 AA standards, the actual assets your creators upload—such as uncaptioned video or diagrams lacking descriptive alt text—fall squarely on the hosting organisation. For teams managing compliance, review our breakdown on accessibility in Moodle adhering to public sector regulations and WCAG 2.2.
Coassemble Moodle pricing breakdown for production
While the Moodle plugin itself is open-source and free, using Coassemble in production requires an active software subscription. Based on Coassemble's public pricing as of late 2026, annual commitments are structured as follows:
| Plan | Published annual cost | Annual IR allowance | Key inclusions |
|---|---|---|---|
| Sandbox | Free | Evaluation caps | Restricted testing environment |
| Build | US$ 2,500/year (billed as US$ 250/month) | 600 | Entry-level tier |
| Scale | US$ 5,000/year (US$ 500/month) | 2,400 | Priority support, Data Processing Agreement (DPA) |
| Partner | From US$ 20,000/year | 6,000 | Dedicated infrastructure, US/EU/UK/AU data residency |
Every tier provides unlimited course authors, eliminating the punitive per-seat licence penalties common among traditional desktop authoring tools.
Demystifying "IR" metrics
Coassemble's tier structure references an "IR" quota alongside a separate allowance for "Anonymous Recipients". The term "IR" is not explicitly defined in the public documentation. In practice, it denotes an Identified Recipient—effectively an individual tracked learner. However, this is an industry deduction rather than an officially published specification. Before signing a contract, secure written confirmation regarding what triggers an IR consumption event, whether a single user enrolled on three separate modules counts once or thrice, and how overages are billed. For bespoke Moodle commercial queries, Coassemble routes contacts to [email protected].
Calculating the business case in pounds
On the Build plan with 600 IRs annually, assuming each IR equals one active learner, the baseline cost is approximately US$ 4.17 per user per year—roughly £3.30 per learner, prior to currency conversion rates, international transaction charges, and standard UK VAT accounting. For a niche academy with 200 learners, that is an unnecessary overhead compared to zero-cost native H5P. For an enterprise training 600 staff and expending dozens of billable instructional design hours repackaging SCORM files, the subscription quickly pays for itself. Total cost of ownership must be evaluated against the operational labour it displaces.
UK GDPR considerations: data hosting outside your perimeter
This is the critical element of the Coassemble Moodle integration that promotional announcements overlook, and which UK data protection leads must scrutinise.
What data leaves your Moodle database?
According to the plugin technical documentation, learners are identified externally via an algorithmic hash generated from their Moodle user ID and site identifier, excluding plain-text personal names and email addresses. Trainer profile names and avatars are only transmitted during active authoring sessions. The vendor also holds SOC 2 Type II certification.
While this architecture is thoughtful, a pseudonymous identifier tied back to a user database remains personal data under the UK GDPR and the Data Protection Act 2018. Because your organization retains the key to link that identifier to a living individual, tracking telemetry, test attempts, and final completion marks transmitted to external infrastructure represent data processing under the purview of the Information Commissioner's Office (ICO).
Your compliance obligations under UK law
- Transparency and Privacy Notices. You must update your VLE privacy notices to inform data subjects of the third-party processor and the specific processing purpose.
- International Data Transfers. With Coassemble based in Australia and hosting on global cloud platforms, transferring UK learner data abroad requires valid transfer mechanisms under UK GDPR, such as an International Data Transfer Agreement (IDTA) or the UK Addendum to standard contractual clauses. Note that a formal DPA is explicitly highlighted on the Scale plan and above—confirm coverage on the Build tier before subscribing.
- Data Residency Guarantees. Dedicated UK or EU hosting regionalisation is restricted to the Partner tier. On entry and mid-tier packages, data location defaults are unlisted. Establish where your data resides in writing.
- Vendor Lock-in and Offboarding. Because the underlying content is hosted within Coassemble, what happens to your intellectual property if you end the contract? Can course modules be exported as standalone SCORM or HTML5 packages? Ensure your exit strategy is documented before onboarding.
For NHS trusts, public sector organisations, or providers managing the learning records of minors, this integration must be treated as a full Information Governance project rather than a routine plugin installation.
When to invest and when to hold off
Coassemble Moodle is a viable candidate if:
- you manage a high volume of non-technical subject matter experts creating training, and SCORM re-packaging has become an acute bottleneck;
- your learning materials undergo frequent policy or procedural updates where continuous publishing saves substantial operational time;
- you are planning to procure third-party SaaS authoring licences and Coassemble can replace individual seat subscriptions;
- your information governance officers approve the data transfer mechanisms and hosting architecture.
Avoid adopting (or pause) if:
- your Moodle deployment is on a legacy release below 4.1 or running on PHP versions prior to 8.1 (note that Moodle 4.1 has already reached the end of security support);
- your course volume is modest and internal teams already leverage H5P effectively;
- strict internal security mandates require all learner data and educational assets to stay entirely within your local hosting environment;
- your organisation lacks the subject matter capacity to review and validate AI-generated draft modules for pedagogical accuracy.
Common implementation pitfalls to avoid
- Deploying directly into production to "have a look". Thoroughly validate Coassemble Moodle using the sandbox key inside an isolated staging environment.
- Overlooking the
mod/coassemble:addinstancecapability. Without auditing role permissions, any course tutor could inadvertently spin up activities against your usage allowance. - Unplanned coexistence of legacy SCORM and Coassemble. Formulate a clear governance rule determining which modules migrate and which remain native.
- Budgeting on an anticipated free tier. The free account remains roadmap messaging. Base your business case exclusively on published commercial rates.
- Tracking usage caps haphazardly. Exhausting your annual IR quota midway through a delivery term will trigger access disruptions and administrative friction.
How to validate the integration safely in staging
Before introducing Coassemble Moodle to your live environment, we suggest executing a structured one-week technical pilot:
- Clone your production environment. Spin up a fresh staging clone with anonymised test accounts.
- Verify technical prerequisites. Ensure supported PHP releases, valid SSL certificates, open outbound connectivity to
api.coassemble.com, and active activity completion tracking. - Configure sandbox credentials. Input your dedicated sandbox API token, never production keys.
- Execute an end-to-end pilot. Have an instructor build a representative unit, enroll test accounts, complete quizzes, and verify gradebook reconciliation.
- Simulate edge-case failures. Test connection dropouts, mid-quiz tab closures, and concurrent edits to confirm webhook reliability.
- Audit data egress. Review system transaction logs to monitor outbound payload structures.
- Review commercial feasibility. Quantify operational hours saved against the projected annual software cost in pounds.
This rigorous approach applies to any mission-critical VLE module. For instance, in our assessment of BigBlueButton live classrooms for Moodle, we demonstrate how to properly scope infrastructure and capacity overheads alongside baseline software licensing.
How Agathas Web supports your Moodle architecture
At Agathas Web, we have architected and supported enterprise Moodle infrastructure since our inception, managing mission-critical learning platforms across corporate institutions and education providers, including IEJUR where I serve as CTO. When auditing third-party plugins, our mandate is straightforward: does this solve a concrete operational problem without introducing disproportionate overhead or data protection risk?
Through our dedicated Moodle consulting and support services, our team manages plugin evaluations end to end:
- Compatibility and security reviews: auditing core versions, PHP runtimes, HTTPS certificates, proxy firewalls, and potential database hooks;
- Isolated staging environments: configuring mirror environments for safe sandbox evaluation before production sign-off;
- Configuration and role management: calibrating capability flags, activity defaults, and completion webhooks;
- Total Cost of Ownership modelling: comparing proposed SaaS subscription fees against native H5P workflows in pounds sterling;
- UK GDPR compliance alignment: assessing processor agreements, transfer mechanisms, and updating site privacy notices;
- Core Moodle upgrades: modernising legacy Moodle instances to supported, secure releases.
If our evaluation demonstrates that native H5P provides the right balance, we will advise accordingly and assist you in designing repeatable, professional course templates. We also integrate Moodle with communication frameworks, such as official WhatsApp notification APIs, which frequently deliver a more measurable uplift in learner completion than third-party authoring suites.
To discuss your learning platform, get in touch through our Agathas Web Moodle services page, outline your infrastructure requirements, and let us help scope your roadmap.
Final verdict: solid technology, strategic commercial decision
The Coassemble Moodle certified integration addresses an enduring frustration within e-learning: creating and updating engaging content without the clunky cycle of manual SCORM packaging. For multi-author organisations updating time-sensitive digital content, it represents a capable option. For smaller institutions with steady content, native H5P and structured core resources remain unbeatable in terms of value.
With Coassemble Moodle, what makes the difference between an efficient deployment and a procurement headache is the detail beyond the marketing copy: IR quota boundaries, international hosting locations, offboarding flexibility, and rigorous staging. Interrogate these factors thoroughly before committing. If you would like expert support assessing this plugin within your learning stack, speak with our specialist Moodle development and support team.
Related posts

Moodle Workplace 5.3 Review: Multi-Tenancy, AI Limits and UK Business Impact
Multi-tenant unified accounts, 500-row AI limits, and an updated catalogue: what Workplace 5.3 delivers and how to replicate it on open-source Moodle.

Moodle 4.5.16 Security Flaws: Breakdown of All 13 Advisories
SQL injection, cross-course IDOR, and SCORM XSS: all 13 November security bulletins explained for UK VLE administrators.

Configurable Reports for Moodle: Critical Security Vulnerabilities and Remediation
Two critical CVEs have hit Moodle’s most popular reporting plugin. Discover whether your VLE is exposed and how to remediate without breaking faculty reports.