LAMS vs Open edX

LAMS is an open-source system for designing, managing and delivering collaborative online learning activities. Teachers create activity sequences in a visual authoring environment, while separate Author, Monitor and Learner areas support creation, oversight and participation. It can run as a standalone e-learning system or connect with an LMS. Listed integrations include Moodle, Sakai, Blackboard/WebCT, .LRN, Microsoft SharePoint and Tiger Online Training LMS, with options for single sign-on and automatic course and user creation from LMS information. LAMS supports multimedia content, interactive activities, branching paths, live lesson delivery and learner analytics. Version 2.2 supports exporting in IMS Learning Design Level A format. Released under the GPL, it is available as a free download when users install, configure and maintain it themselves under the license. LAMS International offers support, hosting, training, updates, upgrades and development services. The maker describes use in K–12, vocational, higher and adult or community education. Commercial services and licensing have no listed fees.

Open edX is an open-source platform for teaching and learning, combining course authoring tools with a learner-facing learning management system. Open edX Studio supports creating, managing, reusing and remixing course content. Aspects analytics turns enrollment, learner progress, assessment performance, forum activity and video engagement into metrics and visualizations. The platform supports LTI 1.3 integrations and extensible course components called XBlocks. Listed sign-in integrations include SAML and OAuth 2.0 providers such as Facebook, Google, Microsoft and LinkedIn. Open edX supports assessments, certificates, APIs and mobile apps, and can be self-hosted. Universities, governments, nongovernmental organizations and enterprises use the platform. Institutions control their content, learner data, hosting environment and governance policies. The software has no license fees, but an organization operating an instance must arrange hosting, infrastructure, maintenance, support and customization. Organizations can seek implementation help from service partners. The project began in 2012 and is headquartered in Cambridge, Massachusetts. Its security process directs vulnerability reports to its Security Working Group and does not offer bug bounties.