Plugins as proof of technical Moodle experience.
Sebsoft has Moodle.org contributions across coupon flows, payments, user lifecycle, security and messaging gateways.
No obligation · personal technical advice · independent Moodle™ specialist since 2004
Moodle.org contributions.
Published, visible plugin families across access flows, payments, lifecycle management and messaging integrations.
Coupon suite
4 plugins · maintained since 2018
Access and enrolment via coupon codes, including sign-up without a pre-existing account.
- Coupon
- Email/coupon authentication
- Coupon form text filter
- Coupon processor profile field
Payment plugins
7 plugins · maintained since 2021
Paid enrolments, paid activities and gateways for Mollie and PAY.
- Gateway Payments Enrolment
- Gateway Payments activity module
- Gateway Payments availability condition
- Gateway Payments report
- Mollie
- PAY.
- ClassicPay
User lifecycle
2 plugins · maintained since 2015
Suspend, delete and restore accounts automatically, according to your own rules.
- User Suspension
- User Restore
Security
1 plugin · maintained since 2015
Protection against brute-force attacks on the Moodle login screen.
- Anti-hammering / Login blocker
SMS gateways
4 plugins · maintained since 2025
Connect Moodle to an SMS provider for notifications and two-factor authentication.
- Textmagic
- Sinch
- Messagebird
- Plivo
Fonts
2 plugins · maintained since 2021
Your own fonts in PDF certificates and in the text editor, without touching core.
- TCPDF Fonts
- TinyMCE Font Tools (in development)
Build, rescue or modernise Moodle plugins.
Sebsoft helps when a plugin is business-critical, abandoned by its original developer, blocking an upgrade, or simply not available as standard Moodle functionality.
- Custom Moodle plugins built to spec
- Plugin rescue: fix or modernise abandoned plugins
- Payment and enrolment flows
- API and webservice integrations
- Upgrade-ready Moodle coding standards
- Test environments and acceptance support
A controlled technical route.
No black-box development: clear scope, version control, test environment and release path.
Technical intake and scope
We map out the plugin requirements, existing code, dependencies and risk factors before a single line is written.
Code and environment review
Assessment of existing code quality, compatibility with the target Moodle version and security posture.
Build or rescue sprint
Development follows Moodle coding standards. Work happens in a dedicated environment with version control.
Acceptance, release and maintenance
Testing on an acceptance environment, a defined release plan and a maintenance path for future Moodle upgrades.
Need a technical Moodle™ specialist?
Book a technical consultation about plugins, hosting, integrations, BigBlueButton or a partner project.
No obligation, no sales pitch. We advise first; a proposal comes later.