Sakai

Sakai is a Java learning management system built for universities, developed in the open since the early 2000s by a consortium of institutions rather than a single vendor. It covers the academic case in depth — assignments, gradebook, assessments through Samigo, lessons, rosters, rubrics, plagiarism review — and is deployed at real scale by universities that want to own their teaching platform outright.

For a standards audience the interesting part is scormplayer, a module in the main repository rather than a third-party add-on. It is descended from the ADL reference implementation: the package names are still org.adl, and there is a genuine sequencer, not just a run-time API shim. That is more SCORM machinery than most open-source LMSs carry.

It is not a light option. This is a Tomcat-hosted Java application with a substantial operations burden, and it is a poor fit for anyone who wants to host a handful of compliance courses. The SCORM tool's own README is candid about a history of unfinished work and installation caveats, and xAPI amounts to a kernel-level event bridge rather than a supported LRS integration — do not choose Sakai for xAPI.

Maintenance is not in doubt, but the shape of it is worth understanding. Sakai 25.2 was tagged in June 2026, commits land most working days, and around fifteen named contributors have touched the tree in the past year — a consortium project's normal rhythm, not a vendor's roadmap. That also sets the real risk: nothing here rots, but priorities follow whichever member institutions have staff to spare, so a fix you need in scormplayer specifically may wait unless you contribute it.