Cheltenham Interactive LTD
Cheltenham Interactive helps universities, colleges, training providers, and smaller organisations running Moodle. Plugin development, managed hosting, upgrades, support, and integrations, with Azure-backed infrastructure where it genuinely helps.
Core Services
The core services are straightforward: build what Moodle needs, host it properly, upgrade it safely, support it sensibly, and connect it to the systems around it.
Custom plugins, admin tools, reporting, and workflow improvements shaped around real Moodle use.
Explore serviceManaged hosting with staging, backups, updates, monitoring, and practical operational ownership.
Explore serviceUpgrade planning, compatibility checks, staging runs, rollout support, and post-upgrade validation.
Explore serviceIssue investigation, bug fixing, performance troubleshooting, maintenance, and follow-through.
Explore serviceSSO, API work, reporting feeds, data sync, and Moodle connections into the rest of your stack.
Explore serviceTechnical reviews, feasibility checks, planning input, and practical advice on what to do next.
Explore serviceMost real Moodle projects cut across a few of these areas. Hosting, plugin work, consultancy, upgrades, integrations, and support often need to be handled together.
View all Moodle servicesFree Public Plugins
Cheltenham Interactive also releases useful Moodle plugins publicly where they stand on their own. They are free, open source, and a good way to show the same practical plugin work outside paid delivery.
Featured Plugin
assignfeedback_aifeedback
Teacher-side assignment grading guidance for Moodle, designed to support marker judgement rather than replace it.
Common Moodle Work
Why Cheltenham Interactive
You talk to the person doing the work. That matters on Moodle projects, because hosting, plugins, integrations, support, and upgrades all affect each other and are easier to handle when the context stays with one technical owner.
Platform work, hosting, integrations, upgrades, and support can be handled as one picture.
The goal is useful delivery and honest scoping, not theatre, jargon, or layers of account management.
Azure capability is still there where it helps with environments, reliability, security, and operations.
Custom workflows, broken upgrades, messy hosting, or odd platform behaviour are all fair game.
How Work Usually Starts
No complicated delivery theatre. Most Moodle work starts with understanding the setup, sorting the priority, and getting on with the right change.
01
Look at the Moodle estate, plugins, hosting, constraints, and the thing that is actually causing pain.
02
That might be plugin development, an upgrade, support work, an integration, or a hosting change.
03
Support the rollout, follow through on fixes, and leave the platform in a better state than it started.
Early conversations usually end with clearer priorities, safer next steps, and fewer unknowns around the Moodle work itself.
Pedi and Yuri
They are not especially helpful with Moodle upgrades, but they are very much part of the place.
Chief Morale Officer
Specialises in calm focus sessions, desk-side company, and making sure long debugging sessions include a proper break.
Head of Fetch Operations
Known for high-energy patrols, enthusiastic support, and strong opinions about when it is time to stop staring at logs.
Contact
Send a short email with your current setup, what is not working, and any deadlines you are dealing with. That is enough to get a useful conversation started, whether the need is delivery, support, or a technical sanity check before a bigger Moodle change.
