Australian Moodle hosting, development & consulting

What Managed Moodle Hosting Includes

The full scope in writing - including what costs extra and what we do not cover. Read it before the sales call, not after the invoice.

We do not publish a price list, because the honest number depends on your concurrency, your data volume and how much support you need – and a headline price with an asterisk helps nobody. What we can publish is exactly what the service covers, so you can compare our quote against anyone else’s on equal terms.

If a competitor will not tell you the same things in writing, that is worth noticing.

Diagram of a managed Moodle hosting stack, from learners through the edge layer with TLS and caching, to Moodle on tuned PHP-FPM workers, Redis for sessions and application cache, a tuned MySQL or MariaDB database, and nightly off-server backups with tested restores
Every layer here is ours to tune, patch and monitor – including the backups, which are restored and verified rather than assumed.

Included in managed hosting

Infrastructure

  • Provisioning on AWS in Sydney (ap-southeast-2) or Melbourne (ap-southeast-4) – your choice, named in writing along with the availability zones.
  • Server sizing set against your real peak concurrency, not an average or a tier name.
  • Operating system, web server, PHP and database installed, tuned for Moodle and kept patched.
  • TLS certificates issued, installed and renewed automatically. You never think about certificate expiry again.
  • Redis configured for both application cache and sessions.
  • Scheduled cron running correctly, with alerting when a task stalls – the single most common silent failure in Moodle.

Backups and recovery

  • Daily backups of the database and moodledata, retained on an agreed schedule.
  • Backups stored in the same Australian region as the site.
  • Periodic restore testing, verified by logging into the restored site rather than by a job reporting success.
  • A documented recovery process, including who to call and what happens in what order.

Monitoring and security

  • Uptime and response-time monitoring with alerting to us, not just a dashboard you have to remember to check.
  • Certificate expiry, disk usage, database health and cron completion all monitored.
  • Security patching on a defined cadence, and out of cycle for serious Moodle advisories.
  • Firewall and access control configuration, with administrative access restricted rather than open to the internet.

Moodle maintenance

  • A staging environment that matches production. Not an optional extra – it is how everything else stays safe.
  • Moodle version upgrades planned ahead of each release, rehearsed on staging, with every third-party plugin checked for compatibility.
  • A tested rollback path for every production change.
  • Production changes scheduled outside your teaching hours, in your state’s time.
  • Periodic performance review so slow drift is caught before it becomes a complaint.

Support

  • Support Monday to Friday, 8:30am–5:30pm AEST/AEDT, with first-response targets published by severity.
  • Faults diagnosed with the cause explained, not just cleared.
  • A named technical contact who knows your environment.

Costs extra

These are real work rather than hidden fees, and we would rather you saw them here than found them on an invoice:

  • Migration onto our platform – quoted separately, because effort varies enormously with the state of the source site. See how we run migrations.
  • Custom plugin or theme development – see plugin development.
  • Integration builds – SSO, SMS enrolment sync, LTI configuration and the like. See integration.
  • Significant infrastructure changes requested mid-term, such as moving to a multi-server architecture.
  • Data transfer and storage well beyond the agreed allowance, which in practice means large video libraries served directly from Moodle.
  • Out-of-hours change windows requested for convenience rather than required by your teaching calendar.

Out of scope entirely

  • Learner and trainer help desk. Best handled internally by someone who knows your courses. Our 24/7 cover is for platform incidents, not individual course queries.
  • Learner and trainer help desk. Best handled internally by someone who knows your courses.
  • Compliance reporting and regulatory submissions. Your compliance team and SMS vendor own that. We keep the underlying Moodle data clean and exportable.
  • Student management system supply. We integrate with yours; we do not sell one.
  • Course content and instructional design. Not our discipline.

Questions worth asking any Moodle host

Use these on us and on everyone else you are quoting. The answers are more revealing than the price:

  1. Which region and availability zones will my site and my backups be in? Name them.
  2. When did you last restore one of my backups, and how did you verify it worked?
  3. Do I get a staging environment, and is it included or extra?
  4. Who checks that Moodle cron completed, and what happens when it does not?
  5. What are your support hours in my timezone, and what response time do you commit to in writing?
  6. What is explicitly not included?

Take the full checklist into the call

We have written the longer version out as 30 questions to ask any Moodle host – covering data residency, backups, staging, the failures nobody checks, support and exit. No email required; print it or save it as a PDF. Use it on us too.

Next step

If this reads like the service you want, tell us about your site and we will quote against it. If you are still comparing, what actually drives Moodle hosting cost is the piece to read first.

Questions

Frequently asked questions

Why do you not publish prices?

Because the honest number depends on peak concurrency, data volume and support level, and a headline price with an asterisk misleads more than it helps. We publish the full scope instead, so you can compare quotes on equal terms. If you want a number, tell us your learner numbers and we will give you one.

Is a staging environment included?

Yes, on every managed hosting plan. It is not an upsell - it is how upgrades, plugin changes and migrations stay safe. A Moodle host that treats staging as an optional extra is telling you something about how they work.

What happens if we outgrow the plan mid-term?

We tell you before it becomes a problem, because we monitor for it. Resizing within the same architecture is routine. Moving to a multi-server architecture is a bigger change and quoted separately.

Can we leave, and do we get our data?

Yes to both, and there is no exit fee. You get a full database dump and your moodledata, in a standard format any competent Moodle host can restore. We will not hold your site hostage - a provider that would is not one you should be with.

Do you host anything other than Moodle?

No. Moodle only. It is why we can tune the stack specifically rather than running a general-purpose platform and hoping.

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.

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