Best Moodle Hosting in 2026: The LTS Jump Is a Platform Upgrade

If you buy hosting for the Moodle you run today, you may be buying for the wrong Moodle.

Here are the official minimum requirements for the current LTS and the next one, from Moodle’s own developer documentation:

PostgreSQL 13 to 16 is three major versions. PHP 8.1 to 8.3 is two. An LTS-to-LTS move is a platform migration, and for a school or training provider that means it belongs in a procurement cycle rather than a maintenance window.

Two more requirements worth knowing before you sign anything:

• Only 64-bit PHP is supported. Moodle’s docs state this explicitly.
• The sodium PHP extension is required. It’s the single most common reason a Moodle install fails on a host that otherwise “supports PHP”.
• Oracle Database is no longer supported from Moodle LMS 5.0. If your institution standardised on Oracle, that decision has been made for you.

Where each version stands

Read from Moodle’s release page on 18 August 2026:

• 4.5 (LTS) and 5.0 — in security-only support
• 5.1 and 5.2 — current stable
• 5.3 (LTS) — not yet released; its own page states “This version of Moodle has not yet been released.”

For 5.2 specifically, Moodle publishes the end dates plainly: “Bug fixes for general core bugs in 5.2.x will end 19 April 2027” and “Bug fixes for security issues in 5.2.x will end 4 October 2027.”

The practical read for an institutional buyer: if you’re on 4.5 LTS you’re on security-only support, and the next LTS isn’t out yet. Buy hosting that can run PHP 8.3 and PostgreSQL 16 now, so the upgrade is a Moodle task rather than a hosting migration.

The cron trap

Moodle’s scheduled-task system needs cron running frequently — the standard guidance is every minute. It drives far more than housekeeping: forum post notifications, scheduled report generation, course backups, message delivery, badge issuing, gradebook recalculation and enrolment sync.

When cron isn’t running properly, Moodle doesn’t announce it. The site works. Students log in, courses load, quizzes open. What fails is everything asynchronous — notifications don’t arrive, backups don’t happen, grades look stale — and the symptoms get blamed on the software for months.

So ask the host one question: can I run cron every minute? Shared plans that cap cron at five- or fifteen-minute intervals will run Moodle badly in a way that’s hard to diagnose. This is worth more than any performance claim in a sales page.

We could not reach Moodle’s official cron documentation — docs.moodle.org returned 403 to us — so treat the every-minute figure as the widely-documented convention rather than something we quoted from source today.

Why Moodle load is unlike any other CMS

A normal web application has traffic. Moodle has timetables.

An exam window puts every student in a cohort on the same server in the same ten minutes, all submitting attempts that write to the database. Average throughput tells you nothing about whether that works. A box that idles at 5% for six days can fall over on Tuesday at 10am.

What that implies for buying:

• Headroom over average sizing. You’re provisioning for the peak ten minutes of your worst week.
• Database performance matters more than page caching. Quiz submissions are writes. Full-page caching, which rescues most PHP applications, doesn’t help a write storm.
• PHP-FPM worker count is a real limit. When workers are exhausted, requests queue and students see timeouts during the exam.

We did not simulate this. The brief for this article asked for a quiz-submission storm benchmark across hosts — see the methodology below for why there isn’t one. The architectural point stands on its own, but treat the sizing advice as reasoning rather than measurement.

The hosts

Hosting.com (formerly A2 Hosting) — has historically marketed Moodle-specific plans and is a natural first call for an institutional buyer. Confirm the provisioned PHP and database versions against the table above, and confirm per-minute cron — we have not verified its current Moodle offering.

Liquid Web — the clearest published support boundary of any host here, with a tier matrix stating exactly which level stops troubleshooting your server. For a school where the LMS is institutionally critical, a documented scope is worth more than a promise — and its fully managed tier puts OS patching on someone else.

Cloudways — managed hosting on DigitalOcean or AWS with published SLA tiers: 12 hours initial response on the included tier, 6 hours at roughly $100/month, 2 hours at roughly $500/month. Check that response time against your exam calendar — and note its support excludes debugging custom code, which covers your plugins.

InMotion Hosting — a long-standing provider in the education and small-institution segment. We have not verified its current specifications, Moodle support or pricing, so treat this as a name to evaluate rather than a recommendation we’ve evidenced.

Hetzner — the most headroom per euro by a wide margin, which is exactly what spiky exam-window load wants: buy for the peak cheaply. Its dedicated CCX line is sold explicitly for “constantly high CPU usage.” You build and maintain the stack, which also means you control your PHP and PostgreSQL versions ahead of the 5.3 jump. Note availability limits since June and that backups exclude attached Volumes — critical when the Moodle database is the institutional record.

DigitalOcean — $24 for 4GB, best documentation in the category, and managed PostgreSQL if you want the database handled — though at $15/month single-node and $30/month for the HA tier, that add-on can cost more than the server.

ScalaHosting — managed VPS with its own SPanel rather than cPanel, removing a licence cost. Reasonable if you want managed infrastructure and will run Moodle yourself.

What we’d tell a school IT buyer

Specify the stack, not the host. Put PHP 8.3, PostgreSQL 16 and per-minute cron in the requirement, and let providers answer against it. That single change filters the market better than any review.

Size for the exam window, and confirm what happens when PHP-FPM workers are exhausted.

And confirm the backup covers the database specifically, not just the web root — the Moodle database is the student record.

How we checked this

The requirement figures are from Moodle’s official developer documentation at moodledev.io, read on 18 August 2026. Moodle 4.5: PHP minimum 8.1.0, PostgreSQL 13, MySQL 8.0, MariaDB 10.6.7, SQL Server 2017. Moodle 5.3: PHP minimum 8.3.0 with 8.4.x supported, PostgreSQL 16, MySQL 8.4, MariaDB 10.11.0, Aurora MySQL 8.0, SQL Server 2019. The 64-bit-only PHP requirement, the sodium extension and the statement that “Oracle Database is no longer supported from Moodle LMS 5.0” are from the same source, as is “This version of Moodle has not yet been released” on the 5.3 page.

These are minimums, and Moodle says so — its docs note “We recommend keeping all of your software and operating systems up-to-date.” Don’t read the table as a target.

On version support dates: we’ve quoted only the two that Moodle states unambiguously in prose — general bug fixes for 5.2.x ending 19 April 2027 and security fixes ending 4 October 2027 — plus the current status of each release. The release page also carries a dated table whose column meanings we could not determine with confidence, so we’ve left those dates out rather than risk publishing a support-expiry date that an institution might plan around. Check the release page yourself before building a procurement timeline.

We could not reach docs.moodle.org at all — it returned 403 to us — which is why the cron section is flagged as convention rather than quoted requirement, and why there’s no detail here on Moodle’s caching or clustering documentation.

The brief asked for a benchmark and there isn’t one. It specified ranking hosts by burst capacity, PHP-FPM headroom and database performance under a simulated quiz submission storm. We have no Moodle installation, no seeded cohort and no accounts at these seven providers, so nothing here is measured. Everything in the load section is reasoning about how exam-window traffic differs from ordinary web traffic — sound, we think, but not evidence.

It also asked for the cost of a Moodle cluster past one box. We haven’t priced one, because doing it honestly needs the load data we don’t have.

On the hosts: Liquid Web’s support matrix and Cloudways’ SLA tiers and exclusions were verified earlier in this series. We have not verified Hosting.com’s or InMotion Hosting’s current Moodle plans, specifications or pricing at all, and neither has been tested by us. Other provider prices are figures established across this series rather than re-verified today.

What we did not do: install Moodle, run a course, submit a quiz, hold an account at any host here, or measure anything.

The host links above are affiliate links. The advice most likely to save an institution money — specify PHP 8.3 and PostgreSQL 16 in the tender and let providers bid against it — doesn’t require clicking any of them.

FAQ

What are Moodle’s system requirements in 2026?

Moodle 4.5 LTS requires PHP 8.1.0 minimum with PostgreSQL 13, MySQL 8.0 or MariaDB 10.6.7. The next LTS, 5.3, raises that to PHP 8.3.0 with PostgreSQL 16, MySQL 8.4 or MariaDB 10.11.0. Only 64-bit PHP is supported.

Can I run Moodle on shared hosting?

Sometimes, but check cron first — Moodle’s scheduled tasks need to run every minute, and plans limited to five- or fifteen-minute cron will run it badly in ways that are hard to diagnose.

Why aren’t my Moodle notifications sending?

Almost always cron. Moodle’s site keeps working when cron isn’t running properly — it’s the asynchronous work that stops: notifications, backups, gradebook recalculation and enrolment sync.

Does Moodle still support Oracle?

No. Moodle’s documentation states Oracle Database is no longer supported from Moodle LMS 5.0.

How much server does a Moodle site need?

More than its average traffic suggests, because exam windows put an entire cohort on the box in the same ten minutes. Size for that peak and prioritise database write performance over page caching.

Should I upgrade from 4.5 LTS to 5.3 LTS?

Plan it as a platform migration. It means PHP 8.1 to 8.3 and PostgreSQL 13 to 16 — three major database versions — so buy hosting that already runs the newer stack.

Is Moodle Cloud better than self-hosting?

It removes the stack management this article describes, which is the real cost for a small institution. Self-hosting wins on control, plugin freedom and price at scale.