Send us a message and we'll get back to you shortly.
Moodle powers 146,000+ sites and serves 506 million users across 233 countries and territories — making it the world's most widely used learning management system. The software is free. Hosting it is where the real decisions begin.
Moodle hosting determines how fast your platform loads, how smoothly upgrades go, whether your plugins work after each release, and how many 2 AM server emergencies you'll face. And with Moodle 5.1 breaking most shared hosting setups, the hosting landscape has shifted significantly in 2025-2026.
This guide covers what no other article does: both hosting options AND installation methods in one place — with real pricing, honest tradeoffs, and a framework to help you decide.
Here's what you'll find:
Moodle is the open-source LMS originally created by Martin Dougiamas in 2002. Today it's backed by Moodle HQ (an Australian B Corporation), maintained by 82+ Certified Partners worldwide, and used by organizations from small schools to Shell and the Open University (UK).
The numbers tell the story of scale:
| Metric | Value |
|---|---|
| Registered sites | 146,856 |
| Total users | 506+ million |
| Courses created | 55+ million |
| Course enrollments | 3.5+ billion |
| Plugins available | 2,390+ |
| Countries and Territories | 233 |
Moodle is free under the GPL license — but "free" describes the software, not the operation. Running Moodle requires a web server, PHP 8.2+, a database, and someone to keep it all running. The hosting decision shapes your cost, performance, and how painful every upgrade will be.
And upgrades just got more demanding. Moodle 5.0 dropped Oracle database support and the Atto editor. Moodle 5.1 introduced a public directory requirement that breaks most shared hosting setups.
Before choosing a hosting path, you need to know what Moodle actually needs. These requirements are current for Moodle 5.0 and 5.1:
| Resource | Minimum | Production Recommended |
|---|---|---|
| CPU | 1 GHz | 2+ GHz dual-core |
| RAM | 512 MB | 1 GB (8 GB+ for large sites) |
| Disk | 200 MB (code) + content | SSD with RAID for production |
| Component | Requirement |
|---|---|
| PHP | 8.2.0 minimum; 8.3.x and 8.4.x supported; 64-bit only |
| MySQL | 8.4+ |
| MariaDB | 10.11.0+ |
| PostgreSQL | 14+ |
| Oracle | No longer supported (dropped in Moodle 5.0) |
| Web server | Apache, Nginx, OpenLiteSpeed, or IIS |
| PHP extensions | sodium (required), max_input_vars >= 5000 |
Moodle 5.1 requires a public directory for serving web-accessible files. This architectural change improves security but breaks most shared hosting setups — especially those using Softaculous or cPanel auto-installers.
The official performance FAQ states that shared hosting is inadequate for more than 25-50 students. Combined with the public directory requirement, shared hosting is effectively dead for Moodle 5.1+.
Per the official performance recommendations:
Every Moodle deployment falls into one of four categories. Here's the operational reality of each:
| MoodleCloud | Managed Hosting | Self-Hosted (VPS) | Cloud Platform (AWS/Azure) | |
|---|---|---|---|---|
| You control | Course content, basic settings | Content, branding, plugin choices | Everything | Everything |
| Provider handles | Everything including platform | Infrastructure, upgrades, plugins, security | Nothing | Infrastructure only (you manage Moodle) |
| Custom plugins | No | Yes | Yes | Yes |
| Custom themes | No | Yes | Yes | Yes |
| User limit | 750 max | Unlimited | Unlimited | Unlimited |
| Technical team needed | None | None | Sysadmin | Cloud engineer + sysadmin |
| Time to launch | Minutes | Days to weeks | Hours to days | Days to weeks |
| Typical cost | $130-1,770/yr | $3,000-15,000+/yr | $50-300+/mo + staff | $100-500+/mo + staff |
| Best for | Small orgs, pilots, < 750 users | Most organizations | Tech-savvy orgs with sysadmin | Orgs with existing cloud teams |
The short version: MoodleCloud is fast and cheap but limited. Self-hosted gives you control but demands expertise. Moodle cloud hosting on AWS, Azure, or GCP adds scalability but requires cloud skills. Managed hosting through a Moodle Certified Partner is the middle ground — and where most organizations land.
MoodleCloud is Moodle's official SaaS (software as a service) hosting. It's the fastest way to get a Moodle site running — but it comes with significant limitations that many organizations hit within their first year.
| Plan | Users | Storage | Price/Year | Per User/Year |
|---|---|---|---|---|
| Starter | 50 | 1 GB | $130 | $2.60 |
| Mini | 100 | 2.5 GB | $220 | $2.20 |
| Small | 200 | 5 GB | $410 | $2.05 |
| Medium | 500 | 20 GB | $940 | $1.88 |
| Standard | 750 | 50 GB | $1,770 | $2.36 |
Source: MoodleCloud Standard Plans
| Limitation | Impact |
|---|---|
| No custom plugins | Can't install third-party plugins — only what MoodleCloud includes |
| No custom themes | Limited to available theme options — no branding control |
| No API access | Can't integrate with external systems (HR, SIS, analytics) |
| No white-labeling | MoodleCloud branding remains |
| 750 user maximum | Forces migration once you grow beyond this |
| Storage caps | 1-50 GB depending on plan — video-heavy courses hit this fast |
You need to move beyond MoodleCloud when any of these are true:
The next step is either a Moodle Certified Partner (managed hosting) or self-hosting on a VPS or cloud platform.
Your organization needs to install a plagiarism detection plugin (like Turnitin) for student assessments. Can you do this on MoodleCloud?10 pts
Select all that apply
Your training program has 600 active learners today and you expect to reach 1,200 within a year. Is MoodleCloud a viable long-term solution?10 pts
Select all that apply
Your university wants to integrate Moodle with its Student Information System (SIS) via API to automatically sync enrollments. Can MoodleCloud handle this?10 pts
Select all that apply
If you're going the self-hosted route, here are the five ways to get Moodle installed — from traditional to modern.
| Method | Difficulty | Time | Scalability | Best For |
|---|---|---|---|---|
| Manual LAMP/LEMP | Hard | 2-4 hours | Medium | Sysadmins who want full control |
| Docker | Medium | 30-60 min | High | Developers, staging environments |
| Kubernetes/Helm | Hard | 4-6 hours | Very High | Enterprise, auto-scaling |
| Cloud marketplace (AWS/Azure) | Easy | 15-30 min | High | Quick production deployment |
| One-click (Softaculous) | Easy | 5 min | Low | Small sites (Moodle < 5.1 only) |
The traditional approach — install PHP, a database, and a web server, then download and configure Moodle.
If you want to know how to install Moodle on Ubuntu, here are the core commands:
This is a simplified overview. Production deployment requires SSL configuration, firewall rules, cron setup (/usr/bin/php /var/www/moodle/admin/cli/cron.php), and the Moodle 5.1 public directory configuration. See the full MoodleDocs guide.
For development, use Moodle HQ's official moodle-docker. For production, use the Bitnami Moodle image:
[Code Example: Moodle with Docker Compose (Bitnami) — production-ready]
Run docker compose up -d and access Moodle at http://localhost. The Bitnami image bundles MariaDB and handles initial configuration automatically.
For auto-scaling production deployments, use the Bitnami Helm chart:
helm install my-moodle oci://registry-1.docker.io/bitnamicharts/moodle
This works on EKS (AWS), GKE (Google), AKS (Azure), and any standard Kubernetes cluster.
AWS offers an official Moodle reference architecture with CloudFormation templates including Auto Scaling, Aurora database, and EFS storage. Bitnami AMIs are also available on AWS, Azure, and GCP marketplaces.
The easiest option — but Moodle 5.1's public directory requirement may break Softaculous installations on shared hosting. Only use this for Moodle 4.5 LTS or earlier on shared hosting, or for quick testing.
Installing Moodle is the easy part. Keeping it running, secure, and performant is where self-hosting gets expensive — in time, expertise, and stress.
Redis caching is the single biggest performance improvement according to the official docs. Without it, every page load hits the database. You also need to configure OPcache, tune innodb_buffer_pool_size (80% of RAM on dedicated DB servers), and use PHP-FPM instead of mod_php.
Community members report 8.5 million SELECT queries per hour even with minimal users when caching isn't configured properly.
Moodle releases major versions every 6 months (April and October). Each upgrade can require PHP version bumps, database version upgrades, and plugin compatibility testing. Users report significant performance degradation after upgrades when server environments aren't updated to match.
Moodle's cron is described as "a very important part of overall performance". It must run via PHP CLI (not HTTP) to reduce memory consumption. Misconfigured cron causes email queues to back up, grades to not calculate, and the site to slowly degrade — often without obvious error messages.
Beyond a few hundred concurrent users, you need to separate web and database servers, configure load balancing, set up shared file storage (GlusterFS or similar), and implement Redis for distributed caching. This is real systems architecture work.
SSL certificates, PHP patching, database security, moodledata directory permissions (must be writable but outside web root), and monitoring for vulnerabilities — all your responsibility. Moodle releases security patches with each minor release (every 2 months), and you need to apply them promptly.
As TheEduAssist notes: "You become the Moodle administrator AND server administrator." When the person who set up the server leaves, you inherit an undocumented system — and the next upgrade becomes a gamble.
The Moodle hosting market has five tiers. Most affiliate articles only cover Tier 4 (generic VPS), making a real Moodle hosting comparison nearly impossible. Here's the full landscape — from official SaaS to enterprise managed:
| Provider | MoodleCloud |
|---|---|
| Price | $130-1,770/year |
| Best for | Small orgs, pilots, < 750 users, no custom plugins needed |
| Limitation | No custom plugins, no API access, 750 user cap |
These are the providers that most comparison articles miss — and they're the best option for the majority of organizations:
| Provider | Type | Key Differentiator |
|---|---|---|
| Lambda Solutions | Managed + analytics | 20+ years, AWS-based, built-in Lambda Analytics platform, 99.9% SLA |
| Open LMS | Managed + enhanced UX | Part of Learning Technologies Group; "largest team of Moodle experts"; unlimited support model |
| Titus Learning | Managed + development | UK-based Premium Partner; custom plugin development; Moodle Workplace provider |
| Catalyst IT | Managed + development | New Zealand-based; strong in Asia-Pacific and Canada; open-source contributors |
| Hubken Group | SaaS Moodle provider | UK-based, 20+ years; focus on UK education and corporate sectors |
| Cubite | Managed + development | LMS specialists supporting both Moodle and Open edX; Kubernetes on AWS; custom development |
Pricing for Certified Partners is typically quote-based, ranging from $3,000-15,000+/year depending on user count, plugins, and SLA level.
| Provider | Price | Key Feature |
|---|---|---|
| Moclusters | $4-24/mo | Kubernetes-based cloud built specifically for Moodle; supports versions 3.11-5.0; 7-day free trial |
These require you to install and manage Moodle yourself:
| Provider | Starting Price | Key Feature |
|---|---|---|
| Hostinger | $4.99/mo | LiteSpeed, NVMe SSD, 1-click Moodle install |
| ScalaHosting | $19.95/mo | Managed cloud VPS, SPanel, free migration |
| IONOS | $2/mo | Budget option, NVMe SSD |
| Kamatera | $4/mo | 30-day free trial, 24 global data centers |
For Moodle AWS hosting, Amazon offers an official Moodle reference architecture with CloudFormation templates, Auto Scaling, Aurora, and EFS. This is the strongest cloud option for organizations with existing AWS teams — but you still manage the Moodle application layer yourself.
Must-haves:
Red flags:
Moodle hosting ranges from $4/month for basic VPS to $6,000+/month for enterprise managed services. MoodleCloud (official SaaS) costs $130-1,770/year for 50-750 users. Self-hosting infrastructure runs $20-200/month but requires a sysadmin. Most organizations with 200+ users spend $3,000-15,000/year on managed hosting.
The total cost depends on your user count, plugin requirements, and whether you self-host or use a managed provider. A $2/month VPS seems cheap until you factor in the sysadmin time for upgrades, security patches, caching configuration, and plugin compatibility testing. For most organizations, managed hosting through a Moodle Certified Partner is cheaper than dedicating even 10 hours/month of internal IT time to Moodle operations. See our full cost breakdown above.
Moodle LMS software is free and open-source under the GPL license. However, running it requires server hosting, a domain, SSL, and ongoing maintenance. MoodleCloud starts at $130/year for 50 users. Self-hosting costs $20-200/month in infrastructure. "Free" refers to the software license, not the total cost of ownership.
Think of it like WordPress: the software costs nothing, but you still need hosting, a domain, themes, plugins, and someone to maintain it all. Moodle's infrastructure requirements are higher than WordPress — you need PHP 8.2+, a database server, Redis for caching, and properly configured cron jobs. The "free" label is accurate for the license but misleading for the total cost of running a production Moodle site.
Moodle requires PHP 8.2+ (64-bit), MySQL 8.4+ or MariaDB 10.11+ or PostgreSQL 14+, and Apache or Nginx. Minimum hardware: 1 GHz CPU, 512 MB RAM, 200 MB disk. For production, use 2+ GHz dual-core, 8 GB+ RAM, and SSD storage. Moodle 5.1+ also requires a public directory structure.
The official Moodle documentation lists 512 MB RAM as the absolute minimum, but production sites need significantly more. Key PHP settings include OPcache (enabled), max_input_vars >= 5000, and the sodium extension. Oracle database support was dropped entirely in Moodle 5.0. Starting with Moodle 5.1, web-accessible files must be served from a public directory — a change that breaks most shared hosting setups.
Moodle technically runs on shared hosting, but it's not recommended beyond 25-50 students. Starting with Moodle 5.1, the new public directory requirement breaks most shared hosting setups. For reliable performance, use a VPS ($4-20/month minimum), managed hosting, or MoodleCloud.
The Moodle Performance FAQ explicitly states that shared hosting is inadequate for anything beyond very small deployments. Shared hosting can't provide the Redis caching, dedicated database resources, or cron CLI access that Moodle needs for good performance. With Moodle 5.1's public directory requirement, many Softaculous and cPanel auto-installs will simply break. If you're on shared hosting, now is the time to migrate.
MoodleCloud is Moodle's official SaaS hosting service. Plans range from $130/year (50 users, 1 GB storage) to $1,770/year (750 users, 50 GB). It includes automatic updates, mobile app, and video conferencing but does NOT support custom plugins, custom themes, or API access. For those needs, use a Moodle Partner.
MoodleCloud is the fastest way to launch a Moodle site — you can be up and running in minutes with no technical skills. It includes a 28-day free trial with no credit card required. However, its limitations (no custom plugins, 750 user cap, no API access) mean most growing organizations eventually outgrow it. When that happens, the path forward is either a Moodle Certified Partner for managed hosting or self-hosting on a VPS.
Moodle Certified Partners are companies officially vetted by Moodle HQ to provide hosting, implementation, training, and support. There are 82+ partners globally — 36+ Premium Partners (who can offer Moodle Workplace) and 46+ Standard Partners. They pay a ~10% revenue tithe to Moodle HQ, which funds platform development.
Certification matters because it signals deep Moodle expertise and a direct relationship with Moodle HQ. Premium Partners like Lambda Solutions, eThink/Open LMS, Titus Learning, and Catalyst IT have decades of experience managing production Moodle deployments. When evaluating providers, "Moodle Certified Partner" is the first qualification to check — it's the difference between a hosting company that happens to support Moodle and a Moodle specialist that happens to run servers.
Upgrading Moodle involves backing up your database and files, replacing the Moodle code directory with the new version, and running the upgrade script via browser or CLI. Major version jumps require PHP and database upgrades too. Test on a staging server first. Managed hosting providers handle upgrades automatically.
Moodle releases major versions every 6 months (April and October) and minor releases every 2 months. Each major upgrade can break plugins, require PHP version bumps, and need database schema changes. The safest approach: clone your production environment, apply the upgrade, test all plugins and integrations, then apply to production during a maintenance window. This process takes hours of skilled sysadmin time — which is why upgrade management is one of the top reasons organizations choose managed hosting.
Moodle is the world's most widely used LMS for good reason — 146,000+ sites, 2,390+ plugins, and an active global community. But choosing the right hosting is what turns Moodle from "free software" into a reliable learning platform.
Here's what to remember:
The question isn't whether Moodle is the right LMS. It's whether you want to spend your time managing servers — or building courses.
Looking to learn more about and ? These related blog articles explore complementary topics, techniques, and strategies that can help you master Moodle Hosting: The Complete Guide (2026) | Cubite.