Schools don't run on one system. We think their software should.
A fee spreadsheet here, a WhatsApp group there, an admissions notebook somewhere else — most schools hold themselves together with tools that were never built to talk to each other. EduCore is what we built instead.
Based in Nairobi, Kenya.
The gap isn't effort. It's tooling.
Running a school in Kenya means holding together admissions, academics, fees, staffing, and parent communication at the same time — often across more than one campus. The people doing that work aren't short on effort. They're short on a system built for how the work actually happens: fees paid over M-Pesa, parents reached over WhatsApp, connectivity that isn't always guaranteed, and grading that has to support both a numeric scale and CBC competencies at once.
Generic school software built somewhere else tends to bolt these things on as afterthoughts, if it supports them at all. We built EduCore around them from the start.
What we're here to do
Give every school — one campus or several — a single system that covers the whole operation, instead of a different tool for every department.
How we build it
Every module ships because a real part of running a school needed it — not as a feature to check off a list. If it's on our site, it's in the product.
Who it's for
School owners running one campus or a group of them, principals, teachers, finance teams, administrators, and the parents and students on the other end of every record.
See whether EduCore fits your school.
A short conversation is usually enough to tell.
Related guides
- Case Study: Gititu High School on Running End of Term From One System
In his own words, the principal of Gititu High School describes end of term before and after moving marks, fees and student records into EduCore, what surprised the school, and what still needs improving.