LMS and e-learning platforms
Moodle and LMS services for public institutions and private companies.
We implement, host, maintain and develop learning management systems and educational platforms, with Moodle at the core. The same services for universities, government bodies, training providers and companies.
10+ years
of experience
50+
projects delivered
Ongoing
support
Custom
development
The services our clients ask for
Organizations that run a learning platform need a set of services that go beyond installing software. These are the ones we provide, and each has its own page with the details:
Public institutions and private companies
We work with both, and the work is the same: a learning platform that has to be reliable, documented and easy to run. What changes is the emphasis. Public institutions, such as universities, ministries, local governments and public programs, care especially about documentation, data protection, accessibility and continuity over many years. Companies care about predictable costs, availability when training is scheduled and clear reports for HR and managers.
We adapt the proposal, the documentation and the way we work to each case. We can work directly with the organization, or alongside a local integrator that leads the contract while we provide the specialized work.
For companies and institutions
Whether you train employees, run courses for customers or teach students, the platform must work when you need it and be simple for your team to run.
Tell us what you teach, to whom and how many people, and we will propose the platform and the services that fit.
More than an LMS: an educational platform
An LMS manages courses, learners and results. Many organizations also need a public catalog, online enrolment and payment, a portal for learners, reports for management and a connection to the systems they already use. These pieces are not what an LMS is designed for, and they often end up in spreadsheets and manual steps.
We design the whole platform and decide what Moodle does, what needs a plugin and what is connected as a separate application, so that the platform stays simple to maintain. See our page on educational platform development for more detail.
Custom development
Development that fits how you work
Standard Moodle covers a lot, and the rest is built around it. These are the kinds of work we do most often.
- Custom plugins when no existing one solves what you need
- Integrations with academic, HR and payment systems
- Reports and screens for what management needs to see
A specialist provider, instead of one person's memory
A learning platform lives for years and crosses several changes of team, of management and of version. When it depends on one person, each change is a risk. A specialist provider brings continuity: it knows the platform, keeps its documentation up to date and can respond when people change in your organization.
It also brings accumulated experience. Many problems repeat from one organization to another: performance during exams, plugins that stop being maintained, updates that fail. Whoever solved them before solves them faster and with less risk.
How a project works
Every project starts with a conversation about who learns, who teaches and who administers. We then send a written proposal with scope, timeline, responsibilities and support terms. Work happens on a test copy of your platform, and you review the result before it reaches your users. After the launch, we continue with support, maintenance or hosting if you want it.
Conversation and written proposal.
Work and testing on a copy.
Review and approval by your team.
Launch with backup and a plan to go back.
Training, documentation and handover.
Optional support and maintenance.
Documentation and handover
A serious project lives on its documentation. Besides the working platform, we deliver the documents that let another person understand and maintain it: installation details, versions and plugins, guides for administrators and teachers, backup and recovery procedures, a description of the integrations and the custom code, and recommendations for continuity.
The handover is part of the service and not an extra, because the investment depends on it when the contract ends or the team changes.
Data, security and accessibility
A learning platform holds data about students, teachers and employees. We agree at the start who can see what, how long data is kept, where the platform is hosted and how it is recovered after a failure. We also take accessibility into account, so that people with different abilities can use the platform. These points shape the design, so we settle them before quoting.
An illustrative example: a university with an aging platform
This is a hypothetical example, written to illustrate how a project might look, and not a client case. A university runs a Moodle that is several versions behind, maintained by one person, with plugins that no longer receive updates and slow pages during exams.
It decides to contract a service that includes a review of the platform, migration to a current version, replacement of unmaintained plugins, two years of support and training for its team. The provider starts with an inventory, plans the migration on a copy, defines response times and delivers documentation. At the end, the university's team can run the platform and has support for what it needs.
Questions to ask any LMS provider
These questions help you tell a provider that can sustain your platform from one that only installs it:
Service levels that match how critical your platform is
Organizations depend on their learning platform to different degrees. A university during exams, a company with mandatory training deadlines or a public program with a national audience cannot have long outages, while a small internal platform can tolerate more. We agree the level of service with each client: coverage hours, response times by type of problem and the way urgent requests are escalated.
We prefer a level that we can keep every time over a promise that sounds better and fails once. If your organization has formal requirements, we write the levels in the format you need.
Working with your IT team
Many organizations have an IT team that already looks after other systems. We work alongside them and not in place of them: we agree who does what, document how Moodle fits into your infrastructure and give your team the knowledge to handle routine tasks. Where the team prefers to leave the platform entirely to a provider, we take that responsibility under a managed plan.
Either way, the aim is that the platform does not depend on a single person, and that your organization keeps ownership of its data and its configuration.
Planning the platform over several years
A learning platform is a long-term asset, and the cost of running it depends on decisions made early. We help organizations plan for upgrades, for growth in users and for the retirement of components that stop being maintained. A simple plan, with a calendar of updates and a budget for support, avoids the usual pattern of neglect followed by an expensive emergency.
Training programs for administrators and teachers
Training is built into our projects, and it can also be a service on its own. We offer sessions for administrators on settings, users, backups and updates; for course creators on activities, assessment and reports; and for teachers on using the platform with their classes. Sessions are recorded, and we leave guides that your team can reuse when new people join.
Common mistakes when contracting LMS services
Both public institutions and companies tend to repeat the same errors:
What organizations usually value most in a provider
When organizations explain what made them choose a provider, the answers are consistent: clear communication, documentation that other people can follow, honest estimates, response when something fails and a platform that keeps working after the project ends. We organize our work around these points, because they are what makes the difference between a platform that serves for years and one that is replaced after a short time.
Continuity after the project ends
The most valuable part of a service is often what remains after the project: a platform that is documented, a team that knows how to run it and a provider that can still help when needed. We close every project with a handover and a short plan for what comes next, such as support, updates and the next stage of development, so that the organization is never left alone with a system it does not understand.
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