Moodle
Hosting

Moodle is the application I'm most likely to push customers off shared hosting onto a cloud server, and I want to explain why. The software is excellent. The community is huge. The pedagogical capability is unmatched in the open-source world. But Moodle is also a heavy application, and treating it like a small WordPress site sets everyone up for disappointment. Quizzes time out. Course backups fail mid-stream. The gradebook lags during peak assessment periods. None of that reflects badly on Moodle itself; it reflects the mismatch between the application\'s real resource needs and the constraints of shared hosting.

For a small tutor with a private course and a few dozen students who never log in simultaneously, shared hosting will hold up. For anything resembling an institutional deployment (a school, a college, a corporate training programme), I'll always recommend starting on a cloud server from £9.99/mo with the headroom to grow. The cost difference is small. The user experience difference is enormous.

"Moodle on a cloud server is one of the great unsung deals in education hosting. For under £20 a month, a small training provider can run a learning platform that genuinely competes with what universities pay six-figure sums for. The trick is starting at the right tier."

Mark McNeece, Founder, 365i Hosting

The technical realities of Moodle hosting come down to four things. First, PHP memory: Moodle wants more PHP memory than most applications, particularly when generating reports or running backups. Cloud servers let us tune that without the constraints of a shared environment. Second, database queries: an active Moodle course at exam time generates a query volume that punishes unoptimised MySQL configurations. We tune the database for Moodle workloads on cloud servers. Third, file storage: course resources, assignment submissions and SCORM packages add up quickly. Cloud server disk space scales predictably; shared hosting limits will bite. Fourth, the Moodle cron: the cron job is the heartbeat of Moodle and runs every minute. On shared hosting it works but with constraints. On cloud servers it has the resource to do its job properly.

For migrations, Moodle is straightforward in principle and finicky in practice. The application has built-in backup and restore at site, course and user level, which makes the data side of a move clean. The fiddly part is matching PHP versions, MySQL versions and any contributed plugins on the new server to whatever the old server had. We test on PHP 8.3 with the equivalent MySQL configuration during the migration and resolve plugin compatibility issues before going live, not after.

One specific area worth mentioning is GDPR. Moodle has built-in tools for data subject access requests, the right to be forgotten and consent management. They\'re not perfect, but they\'re among the most thoughtful in the LMS space. For UK schools, colleges and training providers operating under UK GDPR, this matters more than the marketing brochures suggest. Combined with self-hosting on UK infrastructure, it\'s a much cleaner data story than a US-hosted SaaS LMS.

Plugin selection is the other place I\'ll usually intervene. Moodle\'s plugin database has thousands of entries, and the quality varies. The official Moodle HQ ones are reliable. The well-known third-party ones (BigBlueButton integration, H5P, Stash, Configurable Reports, Attendance) are reliable. Anything beyond that, treat as research-and-test rather than install-and-trust. We\'ve seen Moodle sites brought to a crawl by a single poorly-written plugin running an unindexed query on every page load.