iSpring
iSpring has moved AI from generating whole courses to sitting inside every text field.
A side-by-side editorial comparison of Brightspace and Code.org — release velocity, themes, recent moves, and the top alternatives to consider.
Brightspace's public changelog feed is mostly community forum noise — real product news is buried elsewhere.
What surfaces on Brightspace's recent feed is dominated by community forum discussions: customer questions about LockDown Browser LTI 1.3 support, archived course locations, faculty-name filtering after course-management changes, and a thread on the meaning of 'Active Display' in February release notes. The only structural product-side change is that the Fixed Issues List is now offered as an embedded spreadsheet for easier scanning.
Challenge evaluation is quietly becoming a real feature inside the daily deploy train.
Code.org ships a dated deploy train most weekdays, each release a flat list of merged PRs with no grouping. The current train is carrying three threads at once: challenge evaluation, which has grown from model foundations to a frontend and now class-gallery listing endpoints; the Lab2 migration, which keeps absorbing Sprite Lab and Python Lab behaviors; and the codeai rebrand, which is now mostly cleaning up regressions rather than repainting surfaces.
What surfaces on Brightspace's recent feed is dominated by community forum discussions: customer questions about LockDown Browser LTI 1.3 support, archived course locations, faculty-name filtering after course-management changes, and a thread on the meaning of 'Active Display' in February release notes. The only structural product-side change is that the Fixed Issues List is now offered as an embedded spreadsheet for easier scanning.
From this slice alone, it's hard to read product trajectory — the feed is community help-desk content rather than release notes. The signals that do appear hint at ongoing migrations (course-management → course-offering search), pending integration work (LockDown Browser LTI 1.3), and a planned end-of-life for the Course Updater tool. Customers are asking transition questions, suggesting Brightspace is in the middle of operational changes that aren't fully documented yet.
Until D2L's actual release notes flow into this feed, predictions are speculative. Based on the customer questions surfacing, expect formal announcements in the next two cycles confirming Course Updater EOL guidance, LockDown Browser LTI 1.3 GA, and clarification around the search/filter changes that replaced course management.
Code.org ships a dated deploy train most weekdays, each release a flat list of merged PRs with no grouping. The current train is carrying three threads at once: challenge evaluation, which has grown from model foundations to a frontend and now class-gallery listing endpoints; the Lab2 migration, which keeps absorbing Sprite Lab and Python Lab behaviors; and the codeai rebrand, which is now mostly cleaning up regressions rather than repainting surfaces.
Challenge evaluation is the thread worth watching. It arrived as a data model in early August, gained an evaluation job and frontend a day later, and now has listing endpoints for class-wide galleries plus a rubric simplified to a flat list of integer levels — the shape of a teacher-facing grading surface rather than an internal experiment. Moderation, meanwhile, has finished its sweep: after Java Lab, Web Lab, and the Asset Manager, this train only adds error handling around lab sandboxes.
The class gallery and simplified rubrics point at challenge evaluation surfacing to teachers as a reviewable set of student responses. What the entries do not show is whether evaluation is automated or human — the rubric-as-integer-levels change reads either way.
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 Brightspace or Code.org.
iSpring has moved AI from generating whole courses to sitting inside every text field.
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.
Whatfix has spent two months naming a problem category it does not yet sell a product for.
See all Brightspace alternatives → · See all Code.org alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Code.org is currently shipping more aggressively (velocity 6.3 vs 2.5), with 0 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. Code.org is currently shipping more aggressively (velocity 6.3 vs 2.5), with 0 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 Brightspace alternatives in EdTech are ranked by recent ship velocity. Browse the "Brightspace alternatives" section above for the current picks, or visit /alternatives/brightspace for the full list with editorial commentary on each.
Top Code.org alternatives in EdTech are ranked by recent ship velocity. Browse the "Code.org alternatives" section above for the current picks, or visit /alternatives/code-org for the full list with editorial commentary on each.