Pages on specific Open edX capabilities that site operators enable and configure as projects: AI extensions, authorization, notifications, multi-site, exams, databases, search and mobile.
Deploying the Open edX AI Extensions plugin with self-hosted models through Ollama or vLLM, or with a hosted provider: learner assistant scope, AI-drafted questions with human review, and prompt templates per course.
Enabling the openedx-authz role-based authorization for Studio by course, organization or site, migrating existing course roles in controlled batches, and preparing for it becoming the default in Willow.
Configuring the Open edX notification system that is on by default from Verawood: web and email channels, digest timing, instance-level defaults, and how to stay opted out if needed.
Running several branded sites from one Open edX installation, each with its own domain, theme and course list, for faculties, partners or customers, and the operational limits of a shared platform.
Turning on timed exams and Custom Courses (CCX) in Open edX: the feature flags involved, how course teams use them, and what they do not provide compared with dedicated proctoring tools.
Running a new Open edX installation on PostgreSQL with the community Tutor plugin introduced in Verawood: who it suits, its fresh-install-only limit and the stability caveats before production use.
Choosing and running the Open edX search backend: Meilisearch by default, Typesense when high availability matters, the Typesense 30 server requirement in Verawood and what still needs Meilisearch.
Building and distributing the Open edX mobile app for a self-hosted platform from the official openedx-app-android code with the Tutor Android plugin, plus branding and app store considerations.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.