Australian Moodle hosting, development & consulting

Moodle services

Moodle Support & Maintenance

Ongoing Moodle support and maintenance - patching, backups with tested restores, monitoring, and upgrades rehearsed on staging. Business hours with published response targets.

Illustration of Moodle support and maintenance: a steady monitoring pulse line with checkpoints running across a skyline of lit buildings against an orange sunset sky
Patched, monitored and backed up - with the backups actually restored rather than assumed.

Most Moodle sites do not fail suddenly. They drift – a version behind, then three; a plugin that stopped being maintained; backups that run but have never been restored; a cron task that has been failing quietly since March. Maintenance is the work of not letting that happen.

What ongoing maintenance covers

  • Security patching applied on a defined cadence, and out of cycle when Moodle publishes a serious advisory.
  • Version upgrades planned ahead of each release rather than after it, rehearsed on a staging clone, with every third-party plugin checked for compatibility and a tested rollback path.
  • Backups with restore testing. A backup nobody has restored is a hypothesis. We restore periodically and verify by logging in.
  • Monitoring and alerting on uptime, certificate expiry, disk, database health, and – the one most providers miss – cron actually completing.
  • Performance review, so slow drift gets caught before it becomes a complaint.
  • Troubleshooting when something breaks, with the cause explained rather than just cleared.

Support hours, stated honestly

We support Moodle Monday to Friday, 8:30am to 5:30pm AEST/AEDT, with first-response targets published by severity on our support and SLA page.

Support is 24/7 for critical incidents. If the site is down, or learners cannot reach an assessment that is open right now, you get a first response within one hour – any hour, any day, including weekends and public holidays. High, normal and low severity work runs Monday to Friday, 8:30am–5:30pm AEST/AEDT. Plenty of providers advertise 24/7 without defining it; our severity definitions and targets are published in full.

Who this suits

Maintenance works best where somebody internally owns the Moodle day-to-day – course setup, enrolments, learner questions – and needs a specialist behind them for the platform itself. We are the layer that keeps the site current, fast and recoverable. We are not a learner help desk, and we will not pretend to be one.

Maintenance on hosting we do not provide

Possible, and reasonably common. We need appropriate access and a staging environment that matches production. What we cannot do on someone else’s infrastructure is guarantee response times that depend on their provider acting – so the commitments differ, and we will set that out in writing rather than leaving it vague.

Where this stops

  • We do not sell or operate a student management system. We integrate Moodle with the one you already run.
  • We do not prepare or lodge compliance reporting. We make sure Moodle holds clean, exportable data for the people who do.
  • We are not a Moodle Partner. We are independent – weigh that as a trade-off rather than assuming either way.
  • We do not write your course content. We build and run the platform it lives on.

Maintenance is usually bundled with managed hosting, and it is where custom plugins get re-tested ahead of each major upgrade. If your site has already drifted a long way behind, a migration and rebuild is often safer than an in-place upgrade.

Questions

Frequently asked questions

Do you offer 24/7 support?

Yes, for critical incidents - a site down, or learners locked out of an open assessment. One hour first response, any time, any day. Routine questions and change requests are handled Monday to Friday, 8:30am–5:30pm AEST/AEDT. The point is not that we say 24/7; it is that we define what qualifies and publish the target.

How often do you apply security patches?

On a defined cadence, and out of cycle whenever Moodle publishes a serious security advisory. Patching is applied to staging first wherever the change is significant enough to warrant it.

Do you actually test that backups restore?

Yes, periodically, and we verify by logging into the restored site rather than by checking that a job reported success. A backup nobody has restored is an assumption, not a safeguard.

Can you maintain a Moodle you do not host?

Yes, with appropriate access and a staging environment matching production. Response commitments differ because some fixes depend on your hosting provider acting - we set that out in writing rather than leaving it implied.

Are you a help desk for our learners?

No. We look after the platform - patching, upgrades, backups, performance, and faults. Learner and trainer support is best handled by someone inside your organisation who knows your courses.

Keep exploring

Talk to a Moodle specialist

Tell us how you deliver training and what is not working. We will tell you what we would do about it, and whether we are the right people to do it. No charge for that conversation.

Book a free consultation See what hosting includes
Email support@techlearning.com.au Phone +61 3 7067 3365 24/7 for critical incidents; Mon–Fri, 8:30am–5:30pm AEST/AEDT otherwise