About EduCore

Software that gets out of the way of teaching.

EduCore exists because most institutions run on four or five disconnected systems — a spreadsheet for marks, a register book for attendance, a separate ledger for fees, and someone's inbox for admissions. This is all of that, joined up.

How we build it

Three decisions shape almost everything else in the product.

One record, one place

A student exists once. Admissions, enrolment, attendance, marks, and fees all point at the same record instead of each keeping their own copy.

Show only what is real

If the system has no data for something, it says so. No placeholder charts, no invented averages, no numbers that look precise but are not.

Match the school day

Terms, periods, registers, and result cards are first-class concepts — not custom fields bolted onto generic business software.

Dedicated portals

Admin, Teacher, and Student

Core modules

Academics, SIS, Finance, Access

Multi

Campus aware

Data scoped per campus

What it's built on

A conventional, boring stack — chosen so the system is maintainable by whoever inherits it, not just by whoever wrote it.

Talk to us

Application

Next.js App Router with server-rendered portals and a shared component system.

Data

A relational schema with real foreign keys and versioned migrations — no ad hoc schema drift.

Access

Matrix permissions checked on the server, with the navigation filtered to match.

Want to see it on your own data?

Send us a note about your institution and we'll walk you through the portals.