Two audiences, one open-source training platform

Enterprises, SMEs, retail, and schools each have different constraints, and those pages set out the specifics. The short version: enterprises and schools need approvals, records and reporting; SMEs need the lowest possible cost of ownership and low technical capacity; retail needs shift-based, multi-site, phone-first delivery. If you are unsure, tell us your headcount and your hardest process and we will tell you plainly which of these is yours.

Technically yes — it is one platform with one data model. Whether it makes sense depends on governance: employee records and student records usually sit in different jurisdictions and have different retention rules, so separating them is often the better design even on shared infrastructure.

The same platform, the same six modules and the same data model, plus the same trilingual localisation and the same ownership terms. What changes is which modules you switch on first, what gets configured, and which reporting you need.

In stages. We scope and configure around your process, migrate what is worth migrating, launch with the people who do the work, and expand once the first group has actually used it. The stage that gets skipped is the one where you find out the approval chain does not do what the policy document says — which is why we insist on real examples before configuration starts.

Yes — retail frontline training, manufacturing shift handover, logistics, and others. The common pattern in these sectors is that the training has to reach people on a phone, on a shift, in a language they read, and produce a record afterwards. That is a configuration and content problem more than a product problem, which is usually good news for cost.