Answers before you book a demo
The things schools ask us most — from rollout time to data ownership to how the Khmer interface really works.
A teacher can set up a classroom pilot quickly. An institution rollout depends on data migration, identity setup, department structure, and staff training, so the implementation plan is agreed after a short discovery session.
Yes. Students, staff, and course lists import from a spreadsheet. On the Institution plan we can connect directly to an existing student information system so enrolment stays in sync rather than being re-uploaded each term.
The student experience is built mobile-first and kept light on purpose. Lesson materials load progressively, and submitted work is queued if a connection drops mid-upload rather than being lost.
The institution does. Course content stays with the school when a teacher leaves, and a full data export is available at any time on every paid plan — not just on the way out.
The interface, notifications, and exported reports are fully available in Khmer. Course content itself is whatever the teacher writes, so a course can be delivered entirely in Khmer, entirely in English, or a mix of both.
Nothing breaks. Enrolment above your plan limit stays active and the difference is settled at the next billing period, so a mid-term intake never locks students out of their courses.
Built to be read in the language your students actually think in
Interface, notifications, course content, and reports all work in Khmer and English. Students can switch languages without losing their place, and teachers can publish a lesson in either.
- Full Khmer interface, not a partial translation
- Khmer typography that renders correctly on low-end devices
- Bilingual course content in a single lesson
- Reports and exports in either language
Still have a question?
Book a short walkthrough and we'll answer anything specific to your school, campus, or programme.