Moodle development services

Engineering for teams that run Moodle

I'm Roxana Castillo, the engineer behind Rosseys Solutions. I work with training teams, companies and institutions that already run Moodle — or another LMS — and hit the limits of what the platform does out of the box.

That's where custom development comes in: a plugin that fits your workflow instead of forcing your workflow into a plugin, an integration that connects Moodle to the tools your organization already uses, or an automation that removes the manual reporting nobody wants to do by hand. I approach each of these as a software engineering problem, not a configuration checklist.

Moodle and LMS audits

Before building anything, it helps to know exactly what you have. I can review a Moodle installation to map custom code, plugins, integrations and technical debt — including installations where the core has been modified by a previous vendor.

That kind of core modification makes upgrades painful and risky. I have experience migrating those customizations out of the core and into properly packaged plugins, so the platform stays upgradable and maintainable. An audit gives you a clear picture of the current state and a prioritized path forward, quoted per project.

Custom plugin development

When Moodle doesn't do what your program needs, a custom plugin is usually the right answer. I develop Moodle plugins following the platform's own conventions — activity modules, local plugins, blocks, admin tools and reports — so they install cleanly and survive upgrades.

I've built and maintain my own Moodle plugins, so this is hands-on work I do regularly, not something I subcontract. Whatever the plugin does, it's written to be readable, documented in English and packaged the way Moodle expects.

LTI 1.3 integrations

LTI 1.3 is how modern learning tools talk to each other securely, and it's one of my core areas. I have experience implementing LTI 1.3 on both sides of the connection — Moodle as the platform and as the tool — including the OAuth 2.0 / OIDC handshake, deep linking and the Assignment and Grade Services (AGS).

AGS on its own only returns a grade. When you need richer tracking than that, I can extend the integration with web services to capture the completion and progress data a grade alone doesn't give you. If you're connecting Moodle to an external tool catalog or a third-party platform, this is the layer I work in.

Integrations, automations and reporting

A learning platform rarely lives alone. I build integrations and automations that connect Moodle to the rest of your stack using its web services, custom REST endpoints and background jobs:

• Web services to move enrollment, users, grades and completion in and out of Moodle programmatically.
• ETL and data pipelines to consolidate learning data for the reports leadership actually asks for.
• Custom reporting beyond the default screens, shaped around the metrics your program is measured on.
• Scheduled automations for the recurring tasks that currently eat someone's afternoon.

Each one is scoped and quoted around what you actually need, not a fixed package.

Technical background and how I work

I'm a senior full-stack engineer with more than 16 years building production systems. My stack spans PHP and the Moodle framework, C# / .NET, Node.js and SQL databases, along with REST APIs, software architecture and enterprise integrations — the range that matters when Moodle has to connect to systems that don't speak its language.

I work 100% remotely from Naples, Florida, with clients across the United States and Latin America. Direct support is in Spanish; code, documentation and written messages are handled in technical English. Every engagement is scoped and quoted per project — there are no fixed price tiers for this kind of work, because no two Moodle problems are the same. If you also need a business website, that's a separate service with clear pricing on my web design page, and I write about technical topics on the blog.