Code.org
Sprite Lab arrives in Lab2, and the day's second tag carries nothing at all.
A side-by-side editorial comparison of Chamilo and Scribe — release velocity, themes, recent moves, and the top alternatives to consider.
Chamilo's 3.0 beta quietly turns the LMS into an MCP server agents can author courses through.
Chamilo runs three lines at once. The legacy 1.11 branch takes security and bugfix releases roughly quarterly, 2.0 reached GA in April and has drawn three patch releases since, and a 3.0 line opened on 13 August. The 3.0 beta is where the direction sits: 456 changes spanning 88 plugin fixes, a 44-item security sweep, and a new MCP server with OAuth 2.1 that exposes course authoring and review to outside clients. The feed's own bodies are unreliable here - both 3.0 tags arrived carrying a single line of text, and the 2.0 GA release reached it only as scraped page fragments.
Scribe is grounding its Optimize agent in company context while widening how docs get captured.
Scribe's recent work splits cleanly in two: making the Optimize agent answer from an organization's own context, and broadening what can become a Scribe in the first place. Admin-set business context now feeds every agent chat, and video uploads join browser capture as a source for step-by-step documentation. Around those, the team is filling in workspace basics — departments, cross-team sharing, and now a sortable list view for the library.
Chamilo runs three lines at once. The legacy 1.11 branch takes security and bugfix releases roughly quarterly, 2.0 reached GA in April and has drawn three patch releases since, and a 3.0 line opened on 13 August. The 3.0 beta is where the direction sits: 456 changes spanning 88 plugin fixes, a 44-item security sweep, and a new MCP server with OAuth 2.1 that exposes course authoring and review to outside clients. The feed's own bodies are unreliable here - both 3.0 tags arrived carrying a single line of text, and the 2.0 GA release reached it only as scraped page fragments.
The rewrite has stopped being the story and the agent surface has started. 2.0 spent its cycle absorbing the legacy feature set - LTI, ONLYOFFICE, the plugin catalogue - and reached GA; 3.0's first beta spends most of its weight on that same restoration work but adds something no 2.0 release contains, an MCP server with OAuth 2.1 auto-connect and tools that write rather than only read. Model providers are being wired directly into the AI helper alongside it. Security remains constant across all three branches, with 44 security items in the 3.0 beta alone.
Expect the MCP tool surface to widen in the next 3.0 beta, since the first pass already moved past read-only lookups into course authoring and review. Whether 3.0 becomes the supported line or 2.0 keeps taking patches is the question the tags themselves do not answer.
Scribe's recent work splits cleanly in two: making the Optimize agent answer from an organization's own context, and broadening what can become a Scribe in the first place. Admin-set business context now feeds every agent chat, and video uploads join browser capture as a source for step-by-step documentation. Around those, the team is filling in workspace basics — departments, cross-team sharing, and now a sortable list view for the library.
The capture engine is being decoupled from the browser recorder: if any video can become a Scribe, the product's input surface stops being tied to a live session. At the same time the agent is moving from a generic assistant to one that reasons over an org's tools and goals, which is what makes it defensible against a general-purpose chatbot pointed at the same documents. Library and org management work is following the customer size that grounding attracts.
Expect the next moves to push the Optimize agent further into retrieval over the library itself, and to extend the video-to-doc path with more source types or bulk import. Library management is likely to keep gaining filtering and ownership controls as document counts grow.
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 Chamilo or Scribe.
Sprite Lab arrives in Lab2, and the day's second tag carries nothing at all.
Kahoot's feed is classroom storytelling, with product news surfacing only occasionally
Monthly digests of accessibility work and legacy retirement, with SCORM now a paid line item
LatitudeLearning is handing its AI assistant to portal administrators to configure, not just switch on.
The cyber-readiness platform stops testing only people and starts testing the agents.
Zenler publishes version-numbered fix lists with the occasional real feature buried at the bottom.
See all Chamilo alternatives → · See all Scribe alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Chamilo and Scribe are shipping at a similar cadence (velocity 6.3 vs 6.3, 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. Chamilo and Scribe are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other EdTech products to evaluate alongside.
Top Chamilo alternatives in EdTech are ranked by recent ship velocity. Browse the "Chamilo alternatives" section above for the current picks, or visit /alternatives/chamilo for the full list with editorial commentary on each.
Top Scribe alternatives in EdTech are ranked by recent ship velocity. Browse the "Scribe alternatives" section above for the current picks, or visit /alternatives/scribe for the full list with editorial commentary on each.