ILIAS
Three supported majors, one security fix, patched in lockstep every month.
A side-by-side editorial comparison of LifterLMS and Sakai — release velocity, themes, recent moves, and the top alternatives to consider.
A WordPress LMS that just made its whole REST surface discoverable to AI clients.
LifterLMS spent June on a run of security-only patches — checkout order creation, quiz start, REST authentication, import user creation, each crediting an outside reporter — before shipping 10.1.0, which registers its REST endpoints for courses, sections, lessons, memberships, access plans, students, enrollments and progress as WordPress Abilities API abilities. That release also added wp llms CLI commands for course enrollments and course structure, and shipped a docs/ai-agents.md guide naming Claude Code, Cursor and Codex as intended clients. The 10.1.1 follow-up is bug fixes plus more entropy in generated order keys.
Sakai keeps a slow annual cadence — Sakai 25 in mid-2025, 25.1 point release in late 2025, with most feed entries being archival docs.
Sakai's recent feed surfaces release-cycle documentation rather than feature-by-feature changelog content. Visible artifacts include the Sakai 25.1 Features-by-Tool index, a Sakai release-date list (with 25.0 in June 2025 and 25.1 in November 2025), and older 25/23/22 release-notes pages. Some entries are decade-old 2.x tool documentation that resurfaces because page metadata changed.
LifterLMS spent June on a run of security-only patches — checkout order creation, quiz start, REST authentication, import user creation, each crediting an outside reporter — before shipping 10.1.0, which registers its REST endpoints for courses, sections, lessons, memberships, access plans, students, enrollments and progress as WordPress Abilities API abilities. That release also added wp llms CLI commands for course enrollments and course structure, and shipped a docs/ai-agents.md guide naming Claude Code, Cursor and Codex as intended clients. The 10.1.1 follow-up is bug fixes plus more entropy in generated order keys.
The direction is clear from what got built around the Abilities API integration: not just the registration, but CLI commands that return a whole course structure in one call and a written guide for driving the plugin from an agent. That is a plugin being deliberately shaped for machine operation rather than exposing an API and hoping. Running underneath it is a sustained security pass — the June patches plus the order-key entropy fix — which is the necessary counterpart to opening the surface up.
Expect the AI-agent documentation and CLI commands to expand faster than the web UI, since the recent releases put more new capability behind wp llms and the abilities registry than in the admin.
Sakai's recent feed surfaces release-cycle documentation rather than feature-by-feature changelog content. Visible artifacts include the Sakai 25.1 Features-by-Tool index, a Sakai release-date list (with 25.0 in June 2025 and 25.1 in November 2025), and older 25/23/22 release-notes pages. Some entries are decade-old 2.x tool documentation that resurfaces because page metadata changed.
Sakai continues its longstanding annual major-release rhythm with point releases on top, consistent with a mature open-source LMS used predominantly in higher education. There is no observable pivot toward AI features, agentic workflows, or new platform surfaces in this feed — the trajectory is steady stewardship.
Expect Sakai 26 along the established annual pattern, with continued point releases and Apereo-aligned community work. Any AI integration would be a notable departure from the current cadence and would be unusual to see appear without clear advance notice.
Other EdTech products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either LifterLMS or Sakai.
Three supported majors, one security fix, patched in lockstep every month.
Schoox argues the LMS should be judged on workforce performance, in post after post
Post-v13 cleanup: three beta tags in one evening, two of them carrying nothing at all.
One feature, four branch tags — TAO's feed is backport plumbing, not release news.
The rebrand is finishing while a challenge-evaluation subsystem quietly assembles.
Whatfix's blog has narrowed onto workflow drift and governance — a repositioning in progress
See all LifterLMS alternatives → · See all Sakai alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — lms — within EdTech. LifterLMS is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. LifterLMS is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other EdTech products to evaluate alongside.
Top LifterLMS alternatives in EdTech are ranked by recent ship velocity. Browse the "LifterLMS alternatives" section above for the current picks, or visit /alternatives/lifterlms for the full list with editorial commentary on each.
Top Sakai alternatives in EdTech are ranked by recent ship velocity. Browse the "Sakai alternatives" section above for the current picks, or visit /alternatives/sakai for the full list with editorial commentary on each.