eLearning · Moodle

Moodle development for universities and training teams

We build custom Moodle plugins, themes and integrations, and we make Moodle fast enough to survive exam week. Every change is built so your next upgrade stays possible.

What we build

Moodle development services

Moodle is open source and built to be extended, so most needs can be met without touching its core code. We do the extending: from a single plugin to a full rebuild of the student experience.

Custom plugins

Activity modules, blocks, local plugins, admin tools, custom reports, and enrolment or authentication plugins for workflows Moodle doesn’t cover out of the box.

Themes & student UX

Child themes built on Boost, so they keep working through upgrades. Accessible, mobile-first and on-brand, without feeling a decade old.

Integrations & SSO

Single sign-on over SAML, OpenID Connect or LDAP; enrolment and grade sync with your student information system; LTI 1.3 tools, video platforms and payment gateways.

Performance & scaling

Caching with Redis, database and cron tuning, file storage that scales, and load tests that simulate exam-week traffic before your students do.

Reporting & data

Custom reports and dashboards for teachers and administrators, and clean exports to the BI tools your institution already uses.

Migrations into Moodle

Moving courses, users, enrolments and grades from another LMS or an older Moodle site, with a dry run before the real one.

Our rule

Upgrade-safe Moodle customization, no core hacks

The most expensive Moodle problem we see isn’t a missing feature. It’s a site that can no longer be upgraded, because someone edited Moodle’s core files to get a feature shipped. Every upgrade overwrites those edits, so the site stays stuck on an old version, and eventually on an unsupported one.

We never modify Moodle core. Custom behaviour goes into plugins, themes and Moodle’s own hooks and events, follows Moodle’s coding guidelines, and comes with automated tests. When the next version ships, your customizations move with it.

If you’ve inherited a site that already has core changes, we find them, then move them into plugins. That’s often the first step of a Moodle upgrade.

How we work

From audit to launch: our Moodle development process

  1. 01

    Audit

    We review your site: version, plugins, custom code, server setup and logs. You get a written report of what’s healthy, what’s risky and what we’d change first.

  2. 02

    Scope

    We agree on what gets built, in what order and how we’ll know it works, split into milestones you can review as they land.

  3. 03

    Build on a copy

    Development happens on a staging copy of your site, never on the one your students are using. You test every milestone there.

  4. 04

    Load-test and launch

    Before go-live we test under realistic peak load, then release in a window you choose, away from exams and enrolment.

  5. 05

    Support

    One team stays on it after launch. If something breaks, it’s ours to fix.

Fit

When Moodle is the right answer, and when it isn’t

Moodle is a strong fit when you need a proven, standards-based LMS: courses, quizzes, assignments, gradebooks and enrolment that thousands of institutions already rely on, with no licence fees and full control over your data.

It’s a weaker fit when the learning experience is the product, for example:

  • a consumer-facing course platform where the UX has to compete with apps,
  • a learning flow that looks nothing like courses and modules,
  • a product where learning is one feature inside a larger system.

In those cases we build portals from scratch instead, and we’ll tell you so in the first conversation. We don’t sell Moodle work to people who don’t need Moodle.

The studio

Why universities work with R2

R2 started in 2018 with one large-scale e-learning platform, a project that grew into the platform for a fully digital, licensed university. Today we’re a studio of 21 people with more than 30 delivered projects across Europe and beyond, for clients including Howard University and Bank of Georgia.

  • One accountable team. The engineers who audit your site are the ones who build it.
  • Peak-load first. We design for the day everyone logs in at once, not the average Tuesday.
  • Straight answers. If a fix is a plugin setting rather than a project, we’ll say so.
FAQ

Moodle development: common questions

Can you take over a Moodle site another vendor built?

Yes. We start with an audit of the code, plugins and server so we know exactly what we’re inheriting, including any core modifications, before we change anything.

Do you modify Moodle core?

No. Everything we build lives in plugins and themes, which is what keeps your site upgradeable. If your site already has core changes, we can move them into plugins.

Which Moodle versions do you work with?

Any version you’re running. If it’s past Moodle’s security support, we’ll recommend an upgrade path alongside the development work, since new features on an unsupported version are a risk.

Can you make Moodle handle exam-week traffic?

Usually, yes. Most slowdowns come from caching, database and cron configuration, or from a few heavy plugins, not from Moodle itself. We find the bottleneck with a load test, fix it, and test again at the peak you expect.

How do you price Moodle development?

After the audit we scope the work into milestones and quote them up front, so you know the cost before we start building. Ongoing support can be agreed separately.

Do we keep ownership of the code?

Moodle is GPL-licensed and so are plugins built for it. The code we write for you is yours, and it’s documented so any competent Moodle team could maintain it.

Related service

Moodle upgrades

Stuck on an old version? We plan, rehearse and run upgrades to Moodle 4.5 LTS or 5.x, without the exam-week surprise.

→

Tell us what your Moodle needs to do.

Tell us your Moodle version, roughly how many users you have and what’s going wrong. An engineer, not a salesperson, replies within one business day.

What’s it about?

Or email info@r2.software