Who EverLMS is for
- An employer training its own staff. Required courses sorted by job role, assessments that show what was learned, and certificates with an expiry date that managers can check before an audit.
- A training provider selling courses. A course catalogue with enrolment, memberships and payment, where access is sold to one learner, a team or a whole organisation.
- A training team running programmes for others. Managers and administrators who assign learners, schedule classroom and live sessions, and follow results across courses.
- An agency whose client needs a learning platform. We deploy it together with the agency, under the agency's name, as described further down.
Where EverLMS runs
EverLMS is in production at JFC System Australia, as an LMS for online training, learner management and professional development programmes, with structured learning pathways, assessments, certificates and progress tracking on any device. It went live in 2026 at lms.jfcsystem.com.au. The platform's own site is everlms.com. The screenshots further down this page show the platform with demo data.
Finalist, Splash Awards Asia 2024. EverLMS was among the finalists in the Education category at DrupalCon Singapore; TheDropTimes published the list.
What is already in EverLMS
For learners
Courses are built as course, chapter and lesson. A lesson can be an uploaded video, a YouTube or Vimeo video, a SCORM package, H5P content, text or a live Zoom class. Lessons can be scheduled, or locked until the one before is complete or its quiz is passed, and courses can be joined into a learning path taken in a set order. On sign-in a learner sees the courses they owe, their status and their expiry dates; certificates they earn are kept in their account, and each course can have its own discussion forum.
For instructors and managers
Quizzes serve as entry assessments, module reviews and final exams. Questions can be randomised, timed and grouped by topic or difficulty, answers are scored automatically, and every attempt is recorded, so instructors can follow individual and group results. Completion can issue a certificate from your own template, with your logo, signatures, the course name and the learner's details. Zoom classes are scheduled from inside the platform and linked to a course or chapter, with attendance tracking and recordings for learners who missed the session. The AI course builder drafts course outlines, lesson structures and quiz questions from a topic, as a starting point for the instructor, and a course structure can be copied for a similar programme instead of being set up again.
For administrators
Access to courses is granted to an individual, a team or a whole organisation, as a one-time purchase or through a membership for a limited period, with payment through PayPal or Stripe; the platform keeps the record of orders, payments and who has access. Users, roles and permissions, the FAQ, news and glossary pages, and branding are managed from the back office. The interface, courses, quizzes and certificates can be translated, and each learner chooses a language. Forums, certificates, quizzes, Zoom lessons and payment can each be switched off, so a deployment carries only what your programme uses.
Screens from EverLMS
View full size
View full size
View full size
View full size
View full size
View full size
View full size
View full size
View full size
View full size
View full size
View full size
View full size
View full size
View full size
View full size
View full size
View full size
View full size
View full size
View full size
View full size
How EverLMS is built
EverLMS is built on Drupal 11 and PHP 8.3, with Vue.js 3, the Zoom SDK for live classes and PayPal or Stripe for payment; the full stack is listed at the end of this page. It is built API-first, so where learners need a mobile app, the app is built against the same back end as part of the project.
An installation profile of EverLMS is also published on Drupal.org as an alpha release, for developers who want to read the code: the open-source EverLMS distribution on Drupal.org (alpha) lists its releases and requirements. Deployments for clients start from the version running in production.
How we deploy and extend EverLMS
A deployment starts from the version already running in production, not from an empty repository. Before anything is signed we show it to you on real code, one role at a time: the visitor browsing courses, the student working through a lesson, the manager assigning learners and the admin setting permissions.
Work on an EverLMS project usually covers the course catalogue and its courses, chapters and lessons; certificate templates and completion rules; enrolment, memberships and payment; the content you already have, whether SCORM packages, H5P, PDF files and slide decks, video or live Zoom classes; your branding and domain; and integration with a CRM, an ERP or another system of record. Customisation is kept apart from the platform core, so a core upgrade does not overwrite it. The order of the work, the fit report and what stays in the platform are set out in how a platform implementation runs.
Staff training and professional education are covered on the education and training page, and articles on choosing and running a learning platform are collected under Drupal LMS articles. If you are an organisation looking for a Drupal LMS development company for custom LMS development around your own training, start with what you teach and who learns it: tell us about your programme.
For agencies
If your agency's client needs a learning platform, we deploy and adapt EverLMS together with you, under your name, and your client receives the running system and its source code. You keep the client relationship; the partner programme sets out how a platform partnership works.
Hosting, source code and warranty
EverLMS runs on your own servers or cloud account, or on infrastructure we operate under a managed hosting agreement. Nothing proprietary runs on it, so that choice can be reversed later. You receive the whole running system and its source code; the customisation we build for you on top of the platform is a development project, and its source code is assigned to you like any other: what you own.
Development work carries our warranty: one year by default, up to three, agreed in the contract before the project starts, with the team that built your deployment fixing what it built. Keeping the system current after that is a separate support and maintenance agreement. Administrators and instructors are trained on your own site with your own courses, and the role guides below are written for the people who will use it every day.
What it costs
An EverLMS deployment is placed in the project tiers on the pricing page like any other build, by what the finished system has to do: the roles, the integrations, the records to move and the languages. What already runs in the platform is not charged as if it were written again; the price is for the part built for you, fixed once the fit report is agreed. The tiers run from Micro to Strategic, and the fit report says which one your deployment is in.
Questions about EverLMS
Can we bring the training content we already have?
Yes. A lesson can be a SCORM package, H5P content, an uploaded video, a YouTube or Vimeo video, text or a live Zoom class, and PDF files and slide decks are moved in as part of the project. What comes across, and in what shape, is listed in the fit report before the price is fixed.
Where are learner records kept?
On the system you choose to run it on: your own servers or cloud account, or hosting we operate for you. Each deployment is a system of its own, not an account on a shared service, so learner records, quiz attempts and certificates stay in your database.
Can learners use it in their own language?
Yes. The interface, courses, quizzes and certificates can be translated, and each learner chooses a language. Which languages a deployment carries is agreed in its scope.
Do our learners need a mobile app?
Usually not: learners follow their courses and track their progress on a phone as well as on a computer. Where an app is needed, it is built against the same back end as part of the project, because EverLMS is built API-first.
What happens to our changes when EverLMS is updated?
They stay. Customisation lives in its own modules and configuration, apart from the platform core, so an update does not overwrite it. Each update is applied on staging first and tested against your changes before it reaches the live system.
Tech stack
- Drupal 11
- PHP 8.3
- Bootstrap 5
- SCSS
- Vue.js 3
- Zoom SDK
- PayPal/Stripe