// the take
This is the Django monolith at the core of Open edX, serving both the LMS (learner-facing delivery) and Studio/CMS (course authoring). It's for institutions and developers building or operating large-scale online course platforms, not for anyone wanting a lightweight LMS to bolt onto a side project.
Genuinely mature project with real CI gates (migrations checks, static analysis, pylint, shard-based unit tests) and clear ownership via CODEOWNERS and a contributor agreement process. The REST API layer is versioned (v0/v1/v2) and split out from the monolith, which is how they're actually migrating pieces to MFEs over time rather than just promising to. The README is unusually honest about operational footguns — it explicitly calls out that LTI nonce replay protection breaks silently on multi-node deployments without a shared cache backend, and spells out the SameSite cookie requirement for LMS/Studio SSO instead of letting you discover it in production.
The maintainers themselves say running this bare-metal is 'mostly undocumented' with only limited community support, and push you toward Tutor or a managed provider — meaning the raw repo isn't really meant to be operated standalone despite being the 'platform' repo. Getting a working UI requires separately cloning and running five MFE repos (authoring, learning, learner-dashboard, profile, account) at fixed ports, so the actual surface area is much bigger than this one repository suggests. Infra requirements are heavy for what you get: MySQL, Mongo, and a shared Redis/Memcached cache are all hard requirements, not optional. It's AGPL v3, which is a real constraint if you intend to build a commercial product on top rather than just self-host for internal use.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →