Moodle hosting · Maintenance
Moodle hosting and maintenance, handled for you.
We size and run the server, take and test the backups, apply security updates and answer when something fails. You keep administrator access to your platform and do not deal with the technical side.
10+ years
of experience
50+
projects delivered
Ongoing
support
Custom
development
What managed hosting means
With a generic hosting plan you get space on a server, and you are responsible for everything else: the version of PHP, the scheduled tasks, backups, security and performance. With managed Moodle, the server is sized for the platform and run by people who know it, and the maintenance work is part of the service.
The practical difference appears the day something goes wrong. In a generic hosting, you open a ticket about a server problem. In a managed service, the same team looks at the server and the Moodle at the same time.
What the service includes
All plans include the same service, and what changes is the capacity of the server.
Plans by capacity
We publish managed Moodle plans with their monthly prices. Popular plans start for small projects, Corporate plans cover companies and institutions, and Elite plans are for platforms with many concurrent users.
Migration of your current Moodle is free on Corporate and Elite plans.
Maintenance on its own
If you host your Moodle elsewhere, or on your own servers, we can still maintain it: updates, backups, monitoring and support, without moving the platform. We review your infrastructure first and propose what is needed.
Where the data lives
For many institutions, especially public ones, the location of the hosting and the rules about personal data are requirements. We discuss them at the start and agree the setup with you, so that the platform meets what your organization needs. If you have specific requirements, such as hosting inside a particular region, tell us before the quote.
How we size a server for your platform
The right server depends on how the platform is used, not only on how many learners are registered. A site with ten thousand registered learners who log in occasionally needs less than a site with five hundred learners who all take an exam at the same hour. The number that matters is concurrent users, together with what they do: reading pages, submitting files, taking timed quizzes or joining video classes.
We start with your expected number of learners and your peaks, choose a plan with a margin and watch the real usage after launch. If the platform grows, we move you to a larger plan without rebuilding anything.
Backups that have been tested
Everyone has backups, and many discover during a failure that they cannot be restored. Our backups are automatic, and we also test that they can be restored. A backup that has never been restored is an assumption, not a guarantee.
Security updates and monitoring
Moodle publishes security fixes regularly, and applying them on time is among the most effective ways to protect a platform. We follow the announcements, test the updates on a copy when they could affect your plugins and apply them in a planned way. The server itself also receives updates, and we keep the web server, PHP and the database in supported versions.
Monitoring watches the availability of the site, the free space on the disk, the state of the scheduled tasks and the response time. When something moves outside the normal range, we are notified and act, often before users notice.
An illustrative case: a training company that stopped worrying about the server
This is a hypothetical example, and not a client case. A training company runs courses for several corporate clients from a Moodle on a generic hosting plan. Every few months something fails: the scheduled tasks stop, a backup does not complete or the site slows down at the start of a big course. Its team spends hours on server problems that have nothing to do with its business.
It moves to managed hosting. The platform is migrated to a server sized for its peaks, backups are tested, tasks are monitored and updates are applied by the provider. When a problem appears, one team looks at the server and at Moodle together. The company's team goes back to producing courses.
Choosing a plan
Plans are organized by capacity. The Popular plans suit projects that are starting, the Corporate plans suit companies and institutions with more learners, and the Elite plans are for platforms with many people connected at the same time. All plans include the same service, and what changes is the capacity of the server.
If you are not sure which plan fits, tell us how many learners you expect and when your peaks are, and we will recommend one. We also build custom setups when a platform needs a dedicated database or extra capacity.
Common mistakes with Moodle hosting
These are the situations that cause most of the problems we see in hosting:
What you need to tell us to choose a plan
To recommend a plan, we ask for the number of learners you expect, the typical and peak number of simultaneous users, the kinds of activities you run (videos, large file uploads, timed exams, live classes), the size of your content, your calendar of busy periods and any requirements about data location. With that, we can recommend a plan and explain why.
Moving from your current host
If your platform lives elsewhere, moving to managed hosting is a migration, and we handle it as such: inventory, test on a copy, a planned cutover and a way to go back. For Corporate and Elite plans the migration is free, and for Popular plans we quote it by the size of the platform. Moving at the right moment, away from exams and course starts, makes the change invisible to your users.
What managed hosting does not replace
Managed hosting takes care of the infrastructure and the technical maintenance, and it does not replace the work of running your courses. Your teachers still create the content, your administrators still manage users and courses, and your organization still decides how the platform is used. What changes is that nobody on your side has to worry about whether the server is up, whether the backups work or whether a security update has been applied.
This division of tasks is one of the reasons the service works well: each side does what it does best.
Growth: moving to a larger plan
Platforms grow, and a plan that was enough last year may not be next year. We follow the usage of your platform and tell you when a larger plan would make sense, before performance suffers. Moving to a larger plan does not require rebuilding anything: the platform is moved to a server with more capacity, in a planned window, and your users notice only that things are faster.
If your usage is seasonal, we can also discuss how to handle peaks without paying for capacity you do not need during the rest of the year.
Support included in hosting
Hosting plans include technical support for the server and for Moodle. When something fails, you do not need to find out whether the cause is in the infrastructure or in the platform: one team looks at both. This reduces the time to resolution and removes the usual back and forth between a hosting company and a Moodle specialist.
Reports and transparency
Managed hosting should be visible. We share regular summaries of what was done on your platform: updates applied, backups taken and tested, incidents and their resolution, and the use of the server compared with its capacity. These summaries help you see the value of the service, anticipate when a larger plan will be needed and answer questions from management or auditors about how the platform is looked after.
Related Moodle services
Managed Moodle: we take care of the server
Server, backups, SSL, security updates and support included. These are some of our monthly plans.
Popular L
US$66 /month
~400 students · ~40 concurrent
Corporativo XL
US$268 /month
~1.500 students · ~150 concurrent
Corporativo Max
US$668 /month
~3.000 students · ~300 concurrent
Elite M
US$944 /month
~5.000 students · ~500 concurrent