Moodle™ server options: self-hosting vs managed hosting

Once you have chosen Moodle™ as your learning management system, the next decision is where the Moodle server will run. You can run it yourself, rent space from a general web host, use Moodle’s own cloud service, or hand the whole job to a specialist. This guide compares those options, sets out what a Moodle server needs, and helps you decide between self-hosting and a managed service.

If you already know you want a specialist to run the platform for you, go straight to our managed Moodle hosting page.

Where a Moodle server can run: the options at a glance

Running Moodle means providing the server, database, storage and ongoing maintenance the software needs. Four options cover almost every case. (New to the platform itself? Start with our overview of what Moodle is and how it works.)

Who can run Moodle for you

Those four options are sold by five kinds of provider, and knowing which kind you are talking to explains most of the differences in service.

• Moodle itself. MoodleCloud is Moodle’s own software-as-a-service product: a ready-to-use site aimed at individuals who sell courses and small organizations with basic training needs. There is no server work, but you cannot install plugins. Our MoodleCloud guide covers what it does and where it stops.
• Moodle Certified Partners and Premium Certified Partners. Companies certified by Moodle to provide hosting, support, customization and training. Premium Certified Partners are long-standing partners that can also offer Moodle Workplace. Moodle lists them in its partner directory.
• Managed LMS specialists. Companies whose business is running Moodle, and often other open-source learning platforms, for clients. Some are in the partner program, some are independent. They bundle the server with upgrades, support and training.
• Generalist web hosts and VPS providers. They sell shared plans, virtual private servers and one-click installers. They look after the server; Moodle is your job.
• Public cloud platforms. Infrastructure you rent and assemble yourself: virtual machines, managed databases, storage and load balancers. A fit only if you have cloud engineering skills in-house.

Moodle server requirements: what any setup has to deliver

Moodle is a PHP application that runs on a web server (usually Apache or Nginx on Linux) with a PostgreSQL, MySQL or MariaDB database. Supported PHP and database versions change with each release, so check the release notes for your version instead of trusting an old checklist.

The official installation documentation gives a realistic minimum of about 5GB of disk space and recommends 1GB of memory or more, noting that a large production server is likely to need 8GB or more. Real sizing depends on how many people use the site at once: a cohort sitting a timed quiz is far heavier than the same number of people reading pages.

Also check that a host can provide:

• Scheduled tasks (cron). Moodle relies on a cron job for background work such as sending forum emails and running course backups. A plan that restricts cron is not suitable.
• A data directory outside the web root. The moodledata folder holds uploaded files and must not be reachable from the web.
• Memory, caching and room to grow. Moodle’s performance recommendations describe adding RAM as the fastest way to improve performance and recommend Redis for caching on load-balanced sites. Large sites usually separate the web server from the database.
• HTTPS on every page and backups that have been restored at least once as a test.

Self-hosted Moodle: pros, cons and the true cost

Self-hosting means your team installs and runs Moodle on infrastructure you control: a Moodle server in your own data centre, a VPS or a public cloud account. Our Moodle installation and setup guide walks through the process.

Advantages of self-hosting

• Full control over versions, plugins, code changes and server configuration.
• You decide exactly where the data lives and who can reach it.
• No licence fee for the software, so direct costs can be low for a small site.

Drawbacks and hidden costs

The software is free; running it is not. Self-hosting often looks like the cheapest route until these jobs are counted:

• Upgrades. Moodle publishes a major release roughly every six months. A standard release receives security fixes for 18 months and a long-term support release for 36, according to Moodle’s release schedule. Staying supported means regular upgrades, each tested on a staging site against your plugins and theme first.
• Security patching. The operating system, web server, PHP, database, Moodle and every plugin need patches. Moodle’s security recommendations are blunt: the older the version, the more vulnerabilities it is likely to contain. Add multi-factor authentication for administrators and a web application firewall.
• Backups and disaster recovery. The same documentation points out that you do not have a good backup unless you are able to restore it.
• Monitoring. Somebody has to notice when the site slows down the evening before a deadline.
• People. Staff time is the largest cost. If one person holds all the knowledge, vacations and resignations become risks. Moodle’s community forums and documentation help, but they are not on call.

Managed hosting: pros and cons

With managed Moodle hosting, a provider runs both the infrastructure and the application for you under a stated service level. From your side it behaves like SaaS, while the site remains standard open-source Moodle that you could move elsewhere.

Advantages of managed hosting

• Expertise. You work with people who handle Moodle questions every day. They can advise on plugins, troubleshoot problems and help you meet privacy requirements such as GDPR.
• Upgrades and patches are handled. A good provider tests each upgrade on a staging copy and schedules it around your training calendar.
• Monitoring and support. Many providers watch the site around the clock.
• A faster launch. Any competent team can get an instance online quickly. Getting it launch-ready, with configuration, branding and integrations, takes longer, and an experienced provider has done it many times.
• Training. Many providers train administrators and course creators, which helps when new people join your team.
• Predictable cost. There is no hardware to buy up front, and capacity grows with enrolment.

Drawbacks of managed hosting

• A recurring fee, usually linked to user numbers or resources.
• Less low-level control. You will rarely get root access, and some providers review plugins before installing them or limit changes to core code.
• You depend on the provider’s quality. That is why the checklist below matters.

Shared hosting and VPS servers: the caveats

A general-purpose web host is attractive on price, and one-click installers make it look easy. Two caveats apply.

Shared hosting. Your site shares processor, memory and often the database server with other customers. Moodle is heavier than a typical website: it needs cron, generous PHP limits and memory for caching. Plans that restrict these make the site slow or unreliable under load. That is acceptable for a pilot, not for training with deadlines. The host also secures the server, not your Moodle site, so upgrades and plugin patches are still yours.

VPS. A virtual private server gives you dedicated resources and root access. It is self-hosting in all but name: unless you pay for management, you patch the operating system, tune PHP and the database, set up backups and respond to outages. Even a “managed VPS” usually covers the server and stops short of the Moodle application.

Questions to ask before someone else runs your server

Put the same questions to every provider on your shortlist and ask for the answers in writing.

1. Uptime and SLA. What availability is committed, how is it measured, and what happens if it is missed?
2. Data residency. In which country are production data and backups stored, and from where do support staff access them? For Canadian organizations, particularly public bodies, health care and education, keeping learner data in Canada is often a policy or contractual requirement.
3. Security and compliance. Ask about encryption, firewalls, intrusion detection and independent audits, and how the provider supports your obligations under the privacy laws that apply to you, such as PIPEDA and provincial legislation in Canada, FERPA in the United States or GDPR in Europe.
4. Upgrade policy. How soon after a Moodle release do they upgrade, who tests, and is the work part of the fee?
5. Plugin policy. Can you install any plugin, including custom ones, and who keeps them updated? Our list of must-have Moodle plugins shows how much depends on the answer.
6. Support. Hours, channels and response targets. Does support cover “how do I do this in Moodle” questions or only infrastructure?
7. Backups and disaster recovery. Frequency, retention, off-site copies and restore tests.
8. Scalability and performance. How do they handle peaks such as exam periods or compliance deadlines?
9. Migration help. Will they move your existing database, files, plugins and theme, and how much downtime should you expect?
10. Exit terms. Can you get a full copy of your database, files and code on request? Open-source software means no software lock-in; make sure the contract does not create one.

Finally, ask for references from organizations of your size and sector.

Hosting trends worth knowing

• Cloud and managed environments have replaced the server in the closet. Elastic capacity matters for sites with seasonal peaks at the start of term or before a compliance deadline.
• Data residency is now a procurement question. Buyers want proof of where data is stored, not a general assurance.
• AI is arriving on both sides. Hosts use machine learning in monitoring to flag anomalies early, and AI features in the LMS put new demands on the environment.
• Learning happens on phones, in the evening and at weekends. Hosting has to perform well for the Moodle mobile app and for remote and hybrid delivery.
• Sustainability is on the questionnaire. Institutions with environmental commitments increasingly ask how data centres are powered.

Which option should you choose?

Choose self-hosting if…

• You have system administrators with Linux, PHP and database experience, and cover for when they are away.
• You need server-level control or code changes that a provider would not allow.
• Your policies require the site to run on infrastructure you own.
• You can commit to upgrades, patching, backups and monitoring for as long as the site exists.

Choose managed hosting if…

• Your team’s time is better spent on courses and learners than on servers.
• You need a committed service level, support and documented security for auditors or clients.
• You need plugins, integrations or branding that MoodleCloud does not allow.
• You have data residency requirements and want them written into a contract.

MoodleCloud suits a single trainer or a small team with basic needs, and shared hosting suits a pilot.

At Lambda Learning, we provide managed Moodle hosting with Canadian data residency: our team handles upgrades, plugin compatibility testing, migrations and around-the-clock support. To talk through your requirements, book a meeting with us.

Frequently asked questions

Should I self-host Moodle or use a managed service?

Self-host if you have experienced system administrators and need server-level control. Small teams with basic needs can use MoodleCloud. Organizations that need plugins, integrations, a service level and support without building a server team are usually better served by a managed service.

Can I run a Moodle server on AWS or another public cloud?

Yes. Moodle runs on any Linux virtual machine, including cloud instances. You are still self-hosting: you choose the instance size, storage, backups and scaling, and you patch the whole stack. Larger sites usually move the database, file storage and cache onto separate services, which takes cloud engineering skills.

What are the Moodle server requirements?

Moodle needs a web server such as Apache or Nginx, PHP, a supported database (PostgreSQL, MySQL or MariaDB), a cron job and a data directory outside the web root. The official documentation suggests about 5GB of disk as a realistic minimum and 1GB or more of memory, with far more for busy sites. Check the release notes for supported versions.

Where does a Moodle site run?

Nowhere in particular. Moodle is software, so each site is hosted wherever its owner or hosting provider puts it: an on-premise server, a VPS, a public cloud region or a managed service. MoodleCloud sites are hosted by Moodle itself. If location matters, ask your provider which country holds your data and backups.