# DevLMS

> DevLMS builds custom Moodle plugins for schools, universities and training companies. You describe the plugin, a scoping assistant gives a fixed price and timeline in minutes, you pay through Whop, and the plugin ships in days: drafted by AI agents, reviewed line by line by a senior Moodle engineer, tested, documented, GPL code you own.

Contact: contact@devlms.com. Get a quote: https://devlms.com/#quote. Languages: English, Arabic, French. Moodle versions: 4.1 LTS to the current 5.x releases.

## Prices

- Small Moodle plugin: from $190. Blocks, filters, local tweaks, availability conditions, editor buttons. Usually 2 to 3 days.
- Standard Moodle plugin: from $700. Reports, admin tools, enrolment methods, payment gateways, question types, activity modules. Usually under two weeks.
- Complex Moodle system: from $4,000. Several plugins working together, SIS/CRM/HR integrations, AI providers, migrations. Planned in milestones.
- Moodle plugin care plan: $149 per month. Moodle and PHP upgrades, bug fixes and up to 4 hours of small changes every month.
- Quotes under $1,500 are paid in full upfront; larger ones are split half to start, half before handover.
- Every quote is reviewed by an engineer within one business day. If the plugin needs more than the quote covers, the client is told before work starts and can adjust scope or get a full refund.

## What DevLMS builds

Activity modules, blocks, local plugins, reports, enrolment methods, payment gateways, question types, authentication (SSO, OAuth), AI providers and placements, themes based on Boost, and integrations with SIS, CRM, HR, video and exam platforms. Also Moodle upgrades, rescuing old custom plugins, and Moodle Marketplace submissions.

## Questions

### How much does a custom Moodle plugin cost?

With DevLMS, small plugins (blocks, filters, local tweaks, editor buttons) start at $190 and take 2 to 3 days. Standard plugins with their own data, permissions and pages (reports, enrolment methods, payment gateways, question types, activity modules) start at $700 and usually ship in under two weeks. Systems of several plugins or outside integrations start at $4,000 and are planned in milestones. Every quote is a fixed price for a written scope.

### How long does it take to build a Moodle plugin?

Small plugins take 2 to 3 days, most standard plugins less than two weeks. The quote gives you the exact timeline before you pay, and a rush option shortens it.

### Who owns the code?

You do. Moodle plugins are licensed under the GPL, and we hand over the full repository with its tests and docs. You can publish it, extend it, or hire anyone else to work on it later.

### Which Moodle versions do you support?

Moodle 4.1 LTS through the current 5.x releases. If you run something older, mention it to the agent and the quote will include the extra work.

### Is the price really fixed?

Yes, for the scope written in your quote. An engineer reviews every quote within one business day. If your plugin needs more than the quote covers, we tell you before any work starts, and you can adjust the scope or get a full refund.

### How do I pay?

Through Whop's secure checkout, by card or the other methods Whop offers in your country. Quotes under $1,500 are paid in full upfront. Larger ones are split: half to start, half before handover.

### What happens after I pay?

You get an email within one business day to confirm the details and get access to a test site if needed. Then you receive builds with a short demo video and screenshots, test them, and send feedback. Two rounds of changes are included in every quote.

### Can you publish it to Moodle Marketplace?

Yes. Choose the directory submission pack and we prepare the listing, screenshots, documentation and the CI setup reviewers look for. Approval is decided by Moodle's reviewers, and we handle their feedback for you.

### Do you use AI to write the code?

Yes, and that's why it's faster and cheaper. AI agents draft code and tests; a senior engineer designs the plugin, reviews every line, and is responsible for what ships. You talk to people, not just a bot.

### Which languages do you work in?

English, Arabic and French. Plugins ship with language strings ready for translation, and we test right to left layouts.

## Blog

- [Moodle 4.5 to 5.3: what changed and what your server needs](https://devlms.com/blog/moodle-5-requirements-and-changes/): PHP, database and upgrade path for every Moodle release from 4.1 to 5.3 LTS, plus the changes in 5.0, 5.1, 5.2 and 5.3 that matter to organisations.
- [A Moodle plugin in days: how it works and what done means](https://devlms.com/blog/moodle-plugin-in-days/): How we take a Moodle plugin from idea to production in days with AI agents and senior review, and the checks every plugin passes before handover.
- [React in Moodle core: what it means for your custom plugins](https://devlms.com/blog/moodle-react-frontend-custom-plugins/): Moodle 5.2 added React, TypeScript and ES modules to core, and 5.3 started moving core screens over. What changes for plugins you own, and what you can leave alone.
- [What breaks when you upgrade Moodle, and how to rescue old plugins](https://devlms.com/blog/moodle-upgrade-what-breaks/): Moodle core upgrades are rarely the problem. Old custom plugins, removed features and server requirements are. A practical list, a risk score and a rescue plan.
- [Outdated PHP under Moodle is a security hole, not a detail](https://devlms.com/blog/outdated-php-moodle-security/): PHP 8.1 is out of support, PHP 8.2 follows on 31 December 2026, and the October 2026 php2shell fixes skipped both. What that means for your Moodle site.

## Optional

- [Full text of every article](https://devlms.com/llms-full.txt)
- [Terms](https://devlms.com/terms/)
- [RSS feed](https://devlms.com/rss.xml)