Open edX
Managed Open edX
Open edX is the most capable open-source learning platform and the most demanding to operate. We run it for organisations that need the capability without building an internal platform team.
Release data last reviewed 2026-05-19. Teak recently dropped out of support.
What is in scope
Named-release upgrades
Open edX cuts a named release roughly twice a year and drops support for older ones as it goes. We plan and execute the upgrade path, including the Tutor major-version jumps and the Python and Django moves that come with them.
Security patching
Advisories tracked against the exact release and patch tag you run, so you patch what affects you rather than upgrading blind.
Platform engineering
XBlocks, MFE customisation, theming, LTI, and the integrations that make the platform match how your organisation actually teaches.
SSO and provisioning
SAML and OIDC against your IdP, with group-driven enrolment so course access follows your directory rather than manual admin.
Migration onto or off Open edX
From LearnDash, Moodle or a legacy platform, or off Open edX when it is the wrong fit. We will tell you which before you commit.
Operations
Monitoring, backups with verified restores, and an upgrade calendar you can show an auditor.
Who does the work
Engagements are led by Amir Tadrisi, who has worked on Open edX since 2013 - including four years at Appsembler, where he handled platform engineering and support for enterprise and university deployments including The Open University. That is his track record rather than a client list of ours, and we would rather say so plainly than imply otherwise.
Public, checkable work: commits in Aquent Gymnasium's own Open edX theme repository, an openedx.org blog byline and conference-meetup listing, and the open-source Tutor and Moodle plugins on github.com/amirtds.
Running a formal evaluation or RFP
We respond to RFPs and can work as a subcontractor or white-label delivery partner to an incumbent supplier, which is often the cleanest structure when you already have a vendor relationship in place.
Support tiers, response-time commitments and upgrade cadence are agreed per engagement and written into the contract - we scope them against your learner count, release policy and internal capability rather than publishing a tier table that would not survive contact with your requirements.
Send us the requirements document and we will come back with a scoped response rather than a brochure.
Start with what you are running now
Tell us your named release and how you deploy it. If you are on one of the 20 unsupported releases, the upgrade path is the first conversation.