iSpring
iSpring has moved AI from generating whole courses to sitting inside every text field.
A side-by-side editorial comparison of Blockly and Open edX — release velocity, themes, recent moves, and the top alternatives to consider.
Post-v13 cleanup: three beta tags in one evening, two of them carrying nothing at all.
Blockly is servicing the v13 line it opened in June with keyboard navigation and screenreader support on by default. The 13.2.2 beta train tagged three times in under three hours, but only beta.0 carries changes — an undo-stack corruption fix, a nested-tree traversal speedup, and focus restoration on toast dismissal. beta.1 and beta.2 record an empty commit range.
Open edX maintenance branches carrying security backports, not features
The visible stream is release-branch commits rather than named releases, and the recent ones are all corrective. Two July entries backport the same fix — an authorization gap where CourseTeamManageAPIView required only authentication, letting any enrolled learner call the endpoint. Earlier entries block SSRF in SAML metadata fetching by validating the URL against loopback, link-local, reserved and private ranges, add LTI launch logging, and normalize block structure keys.
Blockly is servicing the v13 line it opened in June with keyboard navigation and screenreader support on by default. The 13.2.2 beta train tagged three times in under three hours, but only beta.0 carries changes — an undo-stack corruption fix, a nested-tree traversal speedup, and focus restoration on toast dismissal. beta.1 and beta.2 record an empty commit range.
The work since v13.0.0 is consolidation around focus, rendering, and performance rather than new surface area — insertion markers rewritten for memory, connection-database updates sped up, field labels made translatable. Accessibility remains the organizing concern, now expressed as correctness fixes in the machinery that shipped rather than new capability. The rapid empty beta tags suggest release automation firing on non-code commits.
Expect a 13.2.2 final shortly, continuing the pattern of small fix batches on the v13 line. Nothing in these entries points to a v14 or a new feature theme.
The visible stream is release-branch commits rather than named releases, and the recent ones are all corrective. Two July entries backport the same fix — an authorization gap where CourseTeamManageAPIView required only authentication, letting any enrolled learner call the endpoint. Earlier entries block SSRF in SAML metadata fetching by validating the URL against loopback, link-local, reserved and private ranges, add LTI launch logging, and normalize block structure keys.
This window shows the maintenance side of a large deployment-driven platform: fixes land on master and are backported across named release branches (teak, ulmo, verawood) so operators on older lines get them. The security items share a shape — endpoints and integrations that trusted their callers more than they should. Nothing here indicates feature direction, because feature work does not surface in this branch stream.
Expect continued backporting across the active named branches, since the same authorization fix already landed on two of them within a minute of each other. What ships in the next named release is not visible from these entries.
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 Blockly or Open edX.
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 Blockly alternatives → · See all Open edX alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Blockly and Open edX are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). 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. Blockly and Open edX are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other EdTech products to evaluate alongside.
Top Blockly alternatives in EdTech are ranked by recent ship velocity. Browse the "Blockly alternatives" section above for the current picks, or visit /alternatives/blockly for the full list with editorial commentary on each.
Top Open edX alternatives in EdTech are ranked by recent ship velocity. Browse the "Open edX alternatives" section above for the current picks, or visit /alternatives/openedx for the full list with editorial commentary on each.