Six connected products covering primary, secondary and tertiary institutions, exam practice, AI tutoring, and independent teachers. Each one deploys on its own; all six are built on one academic core, so a pupil, a term and a result mean the same thing everywhere.
Pick the one that matches the institution in front of you. Every card opens a page that says plainly what the product does and where it runs.
One system for pupils, classes, attendance and report cards.
primaryArms, subject combinations, timetables and results at scale.
secondaryFaculties, course registration and transcripts end to end.
tertiaryExam-body question banks with a timed practice engine.
practicequestionsA tutor for every learner, grounded in your curriculum.
aitutorOpen and distance learning the regulator recognises.
tertiaryonlineIndependent teachers running live and recorded classes.
educonnectA primary school has no subject combinations and a polytechnic has no class teacher. Forcing all three into one schema is how school software ends up unusable for everyone.
One database per product, and one tenant per institution inside it. When a customer asks where their data lives, the answer is a specific database on a specific host.
Fees paid in instalments, results that follow NERDC and WAEC, Paystack and Campay rather than card-only checkout, and screens that survive a bad connection.
Tell us what you run today and what is not working. We will tell you which of the six fits, and what moving would actually involve.