Chamilo vs Scribe
Side-by-side trajectory, velocity, and editorial themes.
Chamilo is racing a Symfony/Vue 2.0 rewrite to GA while hardening the legacy 1.11 line.
Chamilo is running two tracks at once. The legacy 1.11.x line keeps shipping security and bugfix maintenance releases (1.11.38, 1.11.40), several addressing critical vulnerabilities. Meanwhile the 2.0 rewrite, a Symfony backend with a Vue frontend, is grinding through release candidates packed with plugin-system revival, LTI interoperability, ONLYOFFICE and H5P integrations, and a sweep of security fixes including removal of an eval()-based RCE.
The center of gravity is the 2.0 RC series marching toward a GA that has already slipped past its milestone date. Each RC both ports legacy tools to Vue and re-enables the plugin ecosystem (CardGame, BBB, BuyCourses, XApi, Tour) on the new architecture, suggesting GA-readiness is gated on plugin parity and migration fidelity rather than new features. The parallel 1.11 security cadence signals Chamilo intends to support the old line through the transition.
Expect continued 2.0 RCs focused on migration and plugin parity before a GA cut, with the 1.11 line receiving security-only releases in the interim. The volume of security fixes inside the RCs points to a hardening push as a GA gate.
Scribe expands what it can ingest and where it can be queried — video in, AI tools out
Scribe is broadening on two fronts: the inputs it can turn into documentation (now arbitrary video, not just live capture) and the surfaces that can reach its content (an MCP server for AI tools). Around those sit enterprise org features — departments, multi-team sharing, more languages, AI editing.
The product is moving from a screen-capture documentation tool toward an AI-mediated knowledge layer: any recording becomes a guide, guides are cleaned up by AI, and the whole corpus is queryable by assistants like Claude and Cursor via MCP. The org-structure and sharing work is the enterprise scaffolding that makes that corpus worth querying.
Expect deeper investment in the AI ingestion and MCP paths — more source formats feeding Scribes and richer programmatic access — with departments and sharing continuing to harden the enterprise story.
See more alternatives to Chamilo →
See more alternatives to Scribe →