iSpring
iSpring has moved AI from generating whole courses to sitting inside every text field.
A side-by-side editorial comparison of LifterLMS and Processing — 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.
Processing is shipping again — and quietly moved its renderer onto wgpu.
Processing spent much of 2025 with a stalled release train; 4.5.4 in June explicitly marked the restart, and three releases have landed since. The work splits in two: build and release plumbing (the Ant-to-Gradle migration now sitting on Gradle 9.x, a release workflow that survives a failed macOS notarization) and an editor-shell refresh built on Jetpack Compose and Material 3. Contributor volume is the other signal — most release notes are lists of first-time PRs rather than maintainer work.
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.
Processing spent much of 2025 with a stalled release train; 4.5.4 in June explicitly marked the restart, and three releases have landed since. The work splits in two: build and release plumbing (the Ant-to-Gradle migration now sitting on Gradle 9.x, a release workflow that survives a failed macOS notarization) and an editor-shell refresh built on Jetpack Compose and Material 3. Contributor volume is the other signal — most release notes are lists of first-time PRs rather than maintainer work.
The plumbing work is close to finished, which frees attention for the graphics stack. `the-wgpu-moment`, a branch open for nearly a year, is now merged into main, pointing Processing away from Java plus OpenGL through JOGL. Expect the next stretch to be about making that path usable and testable rather than about the editor UI.
The likely next move is exposing the wgpu renderer behind an opt-in flag with an open call for testers, while the 4.5.x line continues as the stable Gradle and Compose track.
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 Processing.
iSpring has moved AI from generating whole courses to sitting inside every text field.
Challenge evaluation is quietly becoming a real feature inside the daily deploy train.
Pear Deck's feed is mostly pointer entries; the AI assessment workflows are the one real thread.
Three straight digests point one way: OpenLearning is building for outcomes-based assessment.
IXL keeps enhancing its diagnostic, analytics, and curriculum breadth on a steady monthly cadence.
A listicle engine that opens on the reader's audit anxiety and never mentions a release.
See all LifterLMS alternatives → · See all Processing alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. LifterLMS is currently shipping more aggressively (velocity 6.3 vs 3.8), 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 3.8), 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 Processing alternatives in EdTech are ranked by recent ship velocity. Browse the "Processing alternatives" section above for the current picks, or visit /alternatives/processing for the full list with editorial commentary on each.