Gakuin

Gakuin is a complete operating system for a school. It brings admissions, students, staff, timetables, attendance, grades, fees, communication, the library, transport, and more under one roof — so that everyone from the head teacher to a parent at home is working from the same, trustworthy picture. After a long build, version one is finished and the whole platform is live end to end.

The problem it solves

Most schools don't run on one system. They run on a dozen — a student database here, a spreadsheet for fees, a separate app for messaging parents, a paper register for attendance, and a notebook for the bus routes. Information gets copied by hand between them, which is slow and quietly error-prone. Gakuin replaces that patchwork with a single platform where a fact entered once is correct everywhere: enrol a student in admissions and they immediately exist for the timetable, the register, the fee ledger, and the parent portal.

What it covers

Version one is genuinely broad. It handles the full life of a school year:

• Admissions and enrolment, from application to a registered student
• Student and staff records, classes, and subjects
• Timetabling and daily attendance
• Assessments, examinations, and grading
• Fees, invoicing, and finance
• Human resources and payroll for staff
• A learning management space for coursework and materials
• Library, transport and fleet, and inventory management
• Announcements, messaging, and notifications
• Dedicated portals for students and for parents

The ambition was never to build a thin demo of a school app. It was to build the real thing — the unglamorous modules that a school actually depends on every single day — and make them work together.

Who it's for

Gakuin serves an entire school community at once, and each role sees only what's relevant to them. Administrators get the full operational view. Teachers get their classes, registers, and grade books. Students get their timetable, coursework, and results. Parents get a calm window into their child's day — attendance, fees, announcements — without needing to phone the office. Because it's multi-tenant, a single deployment can host many schools, each fully walled off from the others.

Why it's built the way it is

School software tends to live for years and pass through the hands of people who didn't build it, so the guiding value throughout has been reliability over flash. The platform is built to keep running quietly and correctly, and to be safe to change years from now. That long-horizon mindset shows up everywhere — in how carefully the data is modelled, and in a deliberate choice to favour correctness even when it made the build slower.

Where it is today

Version one is complete: every module above is built, wired together, and working as one system, with a fresh, modern web experience for staff and a clean portal for students and parents. The foundation is finished and dependable. From here the work is depth — richer reporting and analytics on top of all the data the platform now holds, and continued polish on the day-to-day flows that schools live in.