Moodle FAQ

Four things: managed Moodle hosting on AWS in Sydney or Melbourne, custom Moodle plugin and theme development, migration onto or between Moodle environments, and ongoing support and maintenance. Plus the consulting that sits around those. Nothing outside Moodle.

AWS Sydney (ap-southeast-2) or AWS Melbourne (ap-southeast-4) - you choose at onboarding. Course content, learner records, assessment evidence and backups all stay onshore, and we confirm the region and availability zones in writing.

No, and nor does anyone else on AWS - the only Australian AWS regions are Sydney and Melbourne. We serve clients in those cities from Sydney or Melbourne. Treat any provider claiming an AWS region in those cities with real suspicion.

Yes, for critical incidents - a site down, or learners locked out of an assessment that is open now. One hour first response, any hour, any day, including weekends and public holidays. Everything else is handled Monday to Friday, 8:30am–5:30pm AEST/AEDT. We publish what each severity means rather than leaving 24/7 undefined.

No, we are independent. Moodle Partners are licensed by Moodle Pty Ltd and part of their fee funds core development - a fair reason to choose one. Independence means no partner margin and direct access to the people doing the work. If your procurement requires a Partner, we will tell you straight away.

No. We are not an SMS vendor and we do not resell one. If you run aXcelerate, VETtrak, Wisenet or anything else, we integrate Moodle with it so enrolments flow in and outcomes flow back. Moodle is not a substitute for an SMS and we will not pretend otherwise.

No. We do not prepare or lodge regulatory reporting on anyone’s behalf. What we do is make sure Moodle holds clean, exportable delivery and assessment data so your compliance team or SMS vendor can use it.

It depends on concurrency, data volume and how much support you need, so we quote rather than publish a price list. What we do publish is the full scope of what is included and what costs extra, so you can compare quotes properly. Our article on Moodle hosting cost covers what genuinely drives the number.

A straightforward managed hosting migration is usually two to four weeks end to end, most of which is audit and rehearsal rather than the move itself. Anything involving custom development or a platform change takes longer, and we scope it rather than guess.

Not if it is written against core APIs rather than around them. That single distinction is what separates a plugin that survives upgrades from one that blocks them. We test ours against each major version before the upgrade reaches your production site.

Yes, for development and maintenance, provided there is a staging environment matching production. Response commitments differ because some fixes depend on your host acting, and we set that out in writing.

Daily backups, retained to an agreed schedule, and restored periodically to verify - by logging into the restored site, not by checking a job reported success. A backup nobody has restored is an assumption.

With a review: current version, plugin inventory and whether each is maintained, performance, backup validity, and the upgrade path. You get it in writing whether or not you engage us for the work that follows.

No. That is instructional design and belongs with specialists in it. We build and run the platform your content lives on.