Open source LMS

A Moodle development company for institutions and training teams

We build, extend, integrate and look after Moodle for schools, universities, training providers and compliance teams. Our own developers do the work, and the code and data stay yours.

  • Team behind 300+ LMS projects
  • We build our own LMS
  • Plugins, never core hacks
What we cover
  • New sites and rebuilds
  • Plugins written to Moodle standards
  • Themes on top of Boost
  • Integrations and single sign-on
  • Upgrades and migrations
  • Care after launch
Get a free quote Reply within one business day. NDA on request.
The problem

Why Moodle sites become hard to live with

Moodle is rarely chosen for its looks. It gets chosen because a registrar, an HR director or a compliance officer needs things most course tools do not have: a role system fine enough to give a department head exactly one category, a gradebook that can weight and aggregate, completion records that stand up in an audit, and a catalog that can hold thousands of courses.

It is also open source, so the code, the database and the hosting decision are yours. The price of that freedom is that someone has to run it properly. We set up new Moodle sites, write plugins and themes, connect Moodle to HR and student systems, and rescue installs that have drifted years behind. If your catalog is small and you mainly sell courses from a marketing site, a WordPress LMS plugin may be the lighter option, and we will say so.

  • Nobody can find anything

    Years of courses, half of them copies of last term, sit in a category tree that no longer matches the organization. Learners search, give up and email the help desk instead.

  • Core was edited years ago

    A previous developer changed files inside Moodle itself. Every upgrade since has been postponed, the site now trails several releases behind, and security fixes are not reaching it.

  • Accounts are managed by hand

    New starters, leavers and class lists arrive as spreadsheets. Somebody uploads them, enrolments drift away from the HR or student system, and managers stop trusting the completion reports.

  • It looks nothing like your brand

    The default theme works, but the dashboard feels like a generic tool. Staff compare it with the consumer apps they use every day, and adoption suffers before the content gets a chance.

Explore

Moodle services one by one

Moodle LMS Development

We stand up new Moodle sites: server stack, category and course structure, logins, enrolment methods, roles, gradebook, completion tracking and…

Moodle Customization

Moodle customization without touching core: settings, custom profile and course fields, dashboards, course formats, renderer overrides, local plugins…

Moodle Plugin Development

Custom Moodle plugins written to Moodle coding style: local, block, activity, auth, enrol, report, format and question type plugins with…

Moodle Theme Development

Boost-based Moodle child themes in your brand: SCSS, Mustache templates, renderers and theme settings, checked for accessibility and mobile, with…

Moodle API Development

Moodle web services set up and extended: REST calls, tokens, service definitions and custom external functions, so HR systems, portals and mobile…

Moodle Integration

We connect Moodle to the systems around it: single sign-on, HR and student records sync, LTI tools, video classrooms, payments, WooCommerce…

Moodle Migration

Moves to Moodle from another LMS, between hosts, or from several Moodle sites into one: courses, users, grades, completion and files rehearsed and…

Moodle Upgrade

Moodle version upgrades planned and rehearsed: upgrade path, PHP and database requirements, plugin and theme compatibility, staging run, data checks…

Moodle Mobile App Development

Mobile learning for Moodle: the official app set up properly, branded app options, custom Flutter apps on Moodle web services, plugin support for…

Moodle Maintenance & Support

Monthly Moodle maintenance and support: security updates, cron and task health, backups, caching and database performance, storage, monitoring and an…

What we do

Where our Moodle team comes in

We cover the full life of a Moodle site, and each service below has its own page with the detail.

New sites and rebuilds

Hosting stack, category and course structure, authentication, enrolment methods, roles and completion rules set up as one design, then tested with real teacher and learner accounts.

Plugins written to Moodle standards

Local plugins, blocks, activities, reports and enrolment methods that use the DB API, capabilities, events and the privacy API, so they install cleanly and survive upgrades.

Themes on top of Boost

Child themes with your brand, templates and dashboard layout, built with SCSS and Mustache overrides instead of edits to the parent theme.

Integrations and single sign-on

SAML, OAuth 2 and LDAP logins, user and enrolment sync from HR or student records, LTI tools, video classrooms, payments and data feeds to reporting tools.

Upgrades and migrations

Moves between hosts, merges of several sites into one and release upgrades, each rehearsed on a copy with user, grade and completion counts compared before cutover.

Care after launch

Security releases, cron and task monitoring, backups you can restore, cache and database tuning, and an admin help desk for the people who run your site.

In depth

When Moodle is the right LMS and how we work on it

What Moodle is good at

Moodle organizes everything into contexts: the site, a category, a course, an activity, a user. Roles are bundles of capabilities assigned in one of those contexts, which is why you can let a faculty admin manage one category, give an external auditor read-only access to grades, or create a line manager role that sees only that manager's own team. Add cohorts for bulk enrolment, a gradebook with weighted categories and scales, activity and course completion, and competency frameworks with learning plans, and you have a system built for institutions that must prove who learned what.

Where it asks more of you

That depth has a cost. Moodle needs a server, a working cron, regular upgrades and an administrator who understands the settings. Out of the box it is functional more than pretty, and selling courses to the public takes extra work compared with a store-first platform. We see that as the fair trade for owning an LMS you can shape to your own rules.

Moodle and WordPress LMS plugins

Our team works on both, which leaves us free to recommend whichever fits. A WordPress LMS plugin suits a business whose course site is also its marketing site and shop: fewer courses, strong content pages, checkout and memberships close at hand. Moodle suits organizations where a course is part of a formal process: terms and cohorts, assessors and moderators, mandatory training with expiry, many departments sharing one platform. Plenty of organizations run both, with WordPress and WooCommerce selling the seats and Moodle delivering the learning. Our eLearning platforms page walks through that decision in more detail.

Our rules for working on Moodle

Core is never edited. Behavior changes go into plugins, appearance into a child theme, and wording into language customizations, all kept in a Git repository you own. Changes are made on a staging copy with a recent database, checked against Moodle coding style, and deployed with a written rollback step. Anything that touches grades, completion or enrolments is verified by comparing counts before and after.

What we bring to it

Our team has delivered 300+ LMS and eLearning projects, and we build and maintain our own LMS product, so we know the unglamorous side of learning software: scheduled jobs that fail quietly, reports that time out on large tables, emails that never arrive. We are an independent development company working on the open source Moodle LMS. If you need a single specialist inside your team, you can also hire a Moodle developer from us.

Process

How a Moodle engagement runs

  1. 1

    Talk and review

    You show us the site or the plan. We ask about learners, courses, reporting duties and connected systems, then send a written scope and a free quote.

  2. 2

    Audit or blueprint

    For an existing site we audit plugins, theme, core changes and server health. For a new one we draw the category, role and enrolment design.

  3. 3

    Work in staging

    Development happens on a private copy with a recent database. Your project manager shares progress and you review each milestone with real accounts.

  4. 4

    Rehearse and release

    Upgrades, migrations and data changes are rehearsed first. Go-live happens in a quiet window with a tested backup and a rollback step ready.

  5. 5

    Support on your terms

    We can stay on for monthly maintenance and admin help, or hand over the repository and documentation so your own team carries on.

Deliverables

What stays with you after a Moodle project

  • A Moodle site with no edits to core files
  • Plugins and theme in a Git repository you own
  • A staging environment that matches production
  • Written notes on roles, enrolment and scheduled tasks
  • A project manager and direct access to developers
FAQ

Questions about choosing Moodle and us

Is Moodle the right choice for us, or should we use a WordPress LMS plugin?
It depends on what the LMS has to prove. If you need fine-grained roles, cohorts, a real gradebook, compliance records and a large catalog shared by many departments, Moodle fits. If you mostly sell a handful of courses from your marketing site, a WordPress plugin is usually simpler to own. We build both and will tell you which we would pick.
Do you have a formal partnership with Moodle?
No. We are an independent software company that develops on the open source Moodle LMS, and we do not claim partner status or any Moodle accreditation. What we offer is our own developers, an LMS product of our own that we maintain, and code that follows the Moodle coding guidelines.
Our Moodle was set up years ago and nobody here understands it. Where do you start?
With an audit. We check installed plugins and their state, any changes to core files, theme code, cron and task health, and server settings. You get a plain list of risks ranked by urgency, and we fix them on a staging copy before anything reaches learners.
Where will our Moodle be hosted?
Wherever suits your data and budget rules. We deploy to your own cloud account, a managed server or on-premise hardware, and we advise on sizing, caching and backups. The hosting contract and the data remain in your name, so you are never tied to us.
Do we own the plugins and themes you write?
Yes. Everything we write for you is delivered in your Git repository with install and upgrade notes, and the source code belongs to you. Nothing on the site depends on a private library of ours, so another developer could pick it up tomorrow.
How is a Moodle project priced and scheduled?
By scope. A single plugin or one integration is often a matter of weeks, while a new site with a theme, single sign-on and data migration runs longer. The free consultation ends in a quote with milestones you can hold us to. The main cost drivers are the number of integrations, the custom plugins and how much data has to move.
Start a project

Tell us what your Moodle needs to do

Send us the site address or a short description of the plan. A developer who works on Moodle replies within one business day, usually with a few questions, and the quote that follows is free.

  • Free consultation and quote
  • NDA on request
  • You own the source code
  • Reply within one business day
Add budget and timeline optional, helps us quote faster

This form is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.