Schoox
Schoox argues the LMS should be judged on workforce performance, in post after post
A side-by-side editorial comparison of ILIAS and LifterLMS — release velocity, themes, recent moves, and the top alternatives to consider.
Three supported majors, one security fix, patched in lockstep every month.
ILIAS maintains versions 9, 10 and 11 simultaneously and patches all three on the same day. The August drop (11.3, 10.10, 9.22) and the July drop (11.2, 10.9, 9.21) are identical in shape: a maintenance release per branch, each described only as containing security fixes with the details held behind the project's security blog. Release notes carry no changelog at all, just a pointer and a warning to download the packaged tarball rather than GitHub's auto-generated source archive, which breaks composer.
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.
ILIAS maintains versions 9, 10 and 11 simultaneously and patches all three on the same day. The August drop (11.3, 10.10, 9.22) and the July drop (11.2, 10.9, 9.21) are identical in shape: a maintenance release per branch, each described only as containing security fixes with the details held behind the project's security blog. Release notes carry no changelog at all, just a pointer and a warning to download the packaged tarball rather than GitHub's auto-generated source archive, which breaks composer.
The pattern is a disciplined coordinated-disclosure cadence rather than a development roadmap — roughly monthly, all branches together, no feature content in the feed. Keeping three majors on the same patch schedule tells you the installed base is spread across all of them, which is what you would expect from self-hosted university deployments that upgrade on academic-year boundaries. Nothing observable here indicates what version 12 might contain.
Expect the next coordinated triple in roughly a month, again with the substance published on the security blog rather than in the release notes.
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.
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 ILIAS or LifterLMS.
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
Kahoot's public feed is classroom storytelling and partner content, not product releases
See all ILIAS alternatives → · See all LifterLMS 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 5.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 5.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 ILIAS alternatives in EdTech are ranked by recent ship velocity. Browse the "ILIAS alternatives" section above for the current picks, or visit /alternatives/ilias for the full list with editorial commentary on each.
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.