Private corporate batches, live online cohorts and 1-on-1 mentoring in deploying, authoring on and extending the Open edX platform — Tutor, Studio, XBlocks, MFEs and analytics — taught by a practitioner who runs it in production.
20 years across DevOps, SRE and Security · 10,000+ engineers trained · Trained teams at JPMorgan Chase, Verizon, Nokia and the World Bank
Principal DevOps Engineer & Architect
Rajesh teaches Open edX across both halves that a running platform needs: the operations side — Tutor-based deployment for development and production, configuration and secrets, plugin-based extension, Kubernetes deployment, backup and the named-release upgrade path that determines whether an instance stays maintainable — and the platform side, covering Studio authoring and OLX, the grading policy model, XBlocks and the component API, LTI and SCORM integration, micro-frontend customisation and comprehensive theming, SSO and the REST APIs. Sessions treat customisation as an upgrade-cost decision, teaching the plugin and theming routes that survive a release rather than the fork that does not.
Twenty years across DevOps, SRE and Security, in principal and architect roles at PayPay, SoftwareAG, ServiceNow, JDA Software, Intuit, Adobe and others. He has trained engineers at JPMorgan Chase, Verizon, Nokia, the World Bank, VMware, Oracle, Mercedes-Benz and Airbus — more than 10,000 people personally. He teaches what he runs, not what he reads.
You are booked with a named engineer, and that is who turns up. Marketplaces and larger providers rotate whoever is free, so the person who sold you the agenda is rarely the person teaching it.
The same trainer is available for the next engagement, which matters when a team builds on what it learned last time.
Your batch is assigned a named trainer before it starts, and that is who teaches it. See the full faculty.
Engagements are matched on the tool, not the calendar. For Open edX that means a trainer who has run it in production — deploying, authoring on and extending the Open edX platform — Tutor, Studio, XBlocks, MFEs and analytics — rather than whoever is free that week. You are told who is teaching before you commit, and that person is on the discovery call that shapes the agenda.
Where a batch is large enough to need a second trainer, the pairing is declared up front. The lead trainer stays accountable for the syllabus and the assessment either way.
Principal DevOps Engineer & Architect
Twenty years across DevOps, SRE and Security in principal and architect roles at PayPay, SoftwareAG, ServiceNow, JDA Software, Intuit, Adobe, IBM/Emptoris, Ness, MindTree and Accenture. He has trained more than 10,000 engineers personally, at organisations including JPMorgan Chase, Verizon, Nokia, the World Bank, VMware, Oracle, Mercedes-Benz and Airbus. He teaches what he runs, not what he reads.
Teams of 8–30
Custom agenda, your timezone, onsite or online, NDA-friendly.
Request a quoteIndividual engineers
A private instructor and a curriculum built around your goal.
₹99,999Individuals who want peers
Scheduled batch, max 8 to 10 hours of live instruction.
₹34,999A private batch starts with a discovery call. We look at the stack you actually run — the CI system, the cloud, the constraints — and map the agenda onto it, so examples use your topology rather than a generic one.
Delivery is onsite at your premises, live online, or hybrid, scheduled around your release calendar rather than ours. Batches run 8 to 30 engineers.
Every attendee leaves with recordings, slides, lab repositories and a completion certificate. You receive an attendance and assessment report. Invoicing supports PO and GST.
Talk to us about a private Open edX batchOpen edX is the open-source learning platform originally built for edx.org and now developed as an independent project. It has two faces. Studio is the authoring environment, where a course is assembled as a hierarchy of sections, subsections, units and components, and exported or imported as OLX — an XML representation that makes courses versionable and portable. The LMS is the learner-facing side, delivering that course with grading, progress tracking, discussions, certificates and instructor tooling.
Underneath it is a substantial Django application with a distributed supporting cast: MySQL for relational data, MongoDB for the course modulestore, Redis and Celery for asynchronous work, a search backend, and a growing set of React micro-frontends that have replaced the older server-rendered pages for learning, authoring, account and profile experiences. Deployment is done with Tutor, the Docker-based distribution that is now the standard way to install, configure, upgrade and extend Open edX — replacing the older configuration-management approach entirely.
Extension is where most organisations spend their engineering effort. XBlocks are the component API: a custom XBlock adds a new kind of activity to the course authoring palette and renders in both Studio and the LMS. LTI integrates external tools in both directions, SCORM content can be embedded, and Open Response Assessment supports peer and self grading. Beyond components, Tutor plugins add services and configuration, comprehensive theming and micro-frontend customisation change the look, and the REST APIs and event pipeline let Open edX participate in a wider stack rather than sit as an island. Named releases arrive on a predictable cadence, which makes upgrade planning a permanent part of operating the platform.
Organisations that took online learning seriously during the last decade have mostly outgrown their first platform. Hosted products are priced per learner, which becomes painful at scale, and they restrict how far the experience can be customised or integrated. Open edX is the credible alternative for universities, large enterprises, government training bodies and commercial course providers who need control of the data, the branding, the integrations and the cost curve.
The platform itself moved substantially in recent years. Tutor made deployment genuinely tractable where the old installation path was a specialist skill in itself. Micro-frontends replaced large parts of the legacy interface. The analytics story shifted to a modern stack. Each of those changes made the platform better and simultaneously made most existing documentation and institutional knowledge out of date, which is exactly the situation where training pays.
The scarce capability is the combination. Plenty of people can author a course; fewer can run the platform underneath it. Plenty of Django developers exist; few know the XBlock API, the modulestore, the MFE architecture or how a named-release upgrade actually goes. Teams typically need somebody who can deploy it reliably, integrate it with their identity provider and their systems of record, extend it where the business demands something the platform does not ship, and keep it upgradeable rather than forked into a corner.
Understanding what you are about to run. The service topology and the datastores behind it, how LMS and Studio share a course, the micro-frontend layer, the release train and the community process — and an honest assessment of the operational commitment Open edX represents.
Topics: Understand the Open edX architecture, tools and development process · LMS and Studio: two applications, one course · Datastores: MySQL, the MongoDB modulestore, Redis, Celery and search · Micro-frontends and the migration away from server-rendered pages · Named releases, the upgrade cadence and version support · The repository landscape: edx-platform, MFEs, XBlocks and Tutor · Community governance, contribution and where support comes from · Honest sizing: what running this actually costs a team
Setting up the necessary environment to start developing, and the same tooling used for production. Tutor local and development modes, configuration and secrets, domains and TLS, external managed datastores, the plugin system, and Kubernetes deployment for larger installations.
Topics: Set up the necessary development environment to start developing · Tutor concepts: config, environment rendering and image builds · Local development mode, mounted repositories and live reload · Production deployment: domains, TLS, reverse proxy and email · Configuration management, secrets and environment separation · External managed MySQL, MongoDB, Redis and object storage · The Tutor plugin system and official plugins · Kubernetes deployment and when it is justified · Sizing, resource requirements and cost estimation
Using Open edX's course-authoring tool to build a course. Outline structure and its effect on navigation and grading, component types, files and static assets, scheduling and release dates, course-level settings, and OLX import and export so courses are versionable rather than trapped in a UI.
Topics: Use Open edX's course-authoring tool to build a course · Course outline: sections, subsections, units and components · Component types: text, video, problem, discussion and advanced · Blend the right kind of course content and multimedia to enrich a course · Video handling, transcripts, captions and accessibility · Files, static assets and the course asset pipeline · Release dates, staged publishing and course visibility · Course settings: schedule, details, advanced settings and course team roles · OLX structure, course export and import · Course reruns, templates and reuse across cohorts
Creating interactive, hands-on lessons and activities, and grading them. The problem component types and their settings, grading policy and assignment types, open response assessment with peer and self grading, timed and proctored exams, and integrating external tools through LTI and SCORM.
Topics: Create interactive, hands-on lessons and activities · Problem component types: multiple choice, numerical, text input, dropdown, drag and drop · Advanced problems and the problem markup format · Randomisation, attempts, hints, feedback and show-answer policy · Grading policy: assignment types, weights, drop counts and passing grade · Subsection grading and how the outline affects the gradebook · Open Response Assessment: rubrics, peer grading and self assessment · Timed, proctored and special-exam configuration · Integrate existing web, desktop and mobile applications and content into a course with LTI · SCORM content embedding and its limits
How instructors design and run a course once learners arrive. Enrolment modes and entitlements, cohorts and content groups for differentiated delivery, discussions, certificates, and the instructor dashboard tools used to assess student performance and provide timely feedback.
Topics: Understand how Open edX's components work together to enable instructors to design online learning · Enrolment: modes, invitations, bulk enrolment and entitlements · Cohorts, content groups and differentiated course content · Discussion configuration, moderation and divided discussions · Assess student performance and provide timely feedback using instructor tools · Instructor dashboard: gradebook, grade adjustment and report generation · Certificates: configuration, generation, branding and verification · Email, announcements and learner communication · Collaborate with others to deploy and manage a series of online courses · Course team roles, permissions and programme-level structure
Building, testing and deploying new applications and services to extend the richness of a course. The XBlock API and lifecycle, developing and installing a custom block, micro-frontend customisation, comprehensive theming and branding, and Tutor plugins as the packaging mechanism that keeps all of it upgradeable.
Topics: Build, test and deploy new applications and services to extend a course · The XBlock API: fields, views, handlers and student state · Developing an XBlock locally and testing it in Studio and the LMS · Packaging and installing XBlocks through Tutor · Micro-frontend architecture and the Paragon design system · Customising an MFE and building it into your deployment · Comprehensive theming and branding the legacy pages · Tutor plugins: adding services, settings, patches and images · Django app plugins and platform hooks · Choosing between plugin, theme, MFE change and fork — and the upgrade cost of each
Making Open edX part of a wider estate rather than an island. Authentication and single sign-on, user provisioning, the REST APIs for courses, enrolment and grades, event and webhook integration, and connecting to systems of record such as HR, CRM and commerce platforms.
Topics: Authentication backends, OAuth2 and third-party SSO · SAML integration with an enterprise identity provider · User provisioning, deprovisioning and profile synchronisation · The course, enrolment, grades and user REST APIs · API authentication, tokens and scopes · Programmatic course creation and bulk operations · Event and webhook integration with external systems · Commerce, payment and entitlement integration options · Mobile applications and API compatibility · Data privacy, retention and learner data export obligations
Keeping it running and knowing what it is doing. Tracking events and the analytics pipeline, dashboards and reporting, monitoring and log aggregation, backup and restore, scaling under load, and the named-release upgrade rehearsal that decides whether the platform stays current.
Topics: Track, monitor and analyse the activity and performance of an Open edX service · Tracking events, the event bus and downstream pipelines · The analytics stack: warehouse, transformation and dashboards · Learner and course reporting for instructors and administrators · xAPI and Caliper event forwarding to external systems · Monitoring, log aggregation and alerting · Backup and restore of MySQL, MongoDB and object storage · Scaling: web workers, Celery queues, caching and database load · Performance troubleshooting on a live instance · Named-release upgrades: rehearsal, data migrations, plugin compatibility and rollback
We rebuild the agenda around the tools you actually run.
Request a custom agendaStand up Open edX with Tutor in development, then again in a production shape with a real domain, TLS and external managed datastores.
Build a structured course in Studio, export it as OLX, edit it outside the interface and reimport it without losing content or grading.
Design a grading policy across assignment types, add an ORA task and an LTI tool, then verify the gradebook matches the intended weighting.
Develop an XBlock with persisted learner state, install it through Tutor and confirm it renders correctly in both Studio and the LMS.
Configure enterprise SSO with role mapping, then automate enrolment for a cohort through the REST API with proper error handling.
Rehearse a named-release upgrade in staging with custom plugins, theming and MFE changes in place, documenting every breakage and the rollback path.
Billed yearly at ₹9,996
Max 8 to 10 hours of live instruction
Full program, private instructor
8–30 engineers · custom agenda · onsite or online · PO and GST invoicing
Refunds. If we cancel or postpone a cohort, you get a full refund within 15 days. There is no money-back guarantee otherwise.
Terms. Course material remains licensed to the attendee. Read the terms.
Your data. We don't share it with third parties. Privacy policy.
Certificate of completion
Very good training session. Well explained from the basics to the complex concepts. Also tried to cover practicals and demos within the 3 hour sessions. The learning content and videos are of a great deal of help.
Basics explanation was exemplary from Rajesh where he dealt with complicated topics to be simple. Great learning stuff personally for me.
Very detailed explanation and has lots of patience in attending the questionnaire. Thanks again for your wonderful sessions.
Good discussion, helped us to understand different tools in SRE.
Got good lab sessions which kept the new DevOps tool learnings to the point and it helped a lot in my career.
I took Terraform training with the tutor named Mithilesh. I requested to tailor the course curriculum for my needs. He did an excellent job of showing me how to write the Terraform script per the instructions provided.
| What matters | YouTube + blogs | Generic online course | Freelance marketplace | DevOpsSchool |
|---|---|---|---|---|
| Named practitioner | No | Rarely | Varies per booking | Yes — same trainer each time |
| Production experience | Unknown | Unknown | Unverified | 20 years, named employers |
| Custom agenda | No | No | Sometimes | Built from your stack |
| Onsite delivery | No | No | Sometimes | Yes |
| Lab environment | None | Sandbox that expires | Varies | Your own cloud — skill goes with you |
| Assessment | None | Quiz | Rarely | Assignments + capstone per module |
| Per-attendee certificates | No | Sometimes | Rarely | Yes |
| Corporate invoicing | No | Limited | Varies | PO and GST |
| Post-training support | None | Forum, time-limited | None | Lifetime forum access |
Tell us the team, the stack and the timeline. You'll get a straight answer, not a sales sequence.
Talk to an advisorPrefer to call or email?
More ways to reach us on the contact page.