Users, classes, rosters, parent-child links, PIN resets, credential cards, and per-user app assignments from one school-scoped console.
Run your whole school on one platform.
Roster, attendance, gradebook, fees, lesson plans, and NaCCA-aligned learning apps — sharing one identity, one source of truth, and one login. The platform layer your IT department would have built, if you had an IT department.
Your school's entire operations suite is free.
Onboard your students and your whole staff gets the operations workspace at no cost. You only pay for the optional NaCCA learning apps your students actually use.
100% free · no per-seat staff fee · no card required
School ops and student apps, one platform.
Attendance, grades, fees, lesson notes, and the learning apps share one identity and one source of truth. No four-app shuffle, no re-keying the same roster five times, no integration held together with tape — just one workspace your staff sign into once.
Fast roll call from the back of class, with optional face recognition for attendance marking at the gate or in class where a school enables it.
Assignments, scores, term reports. Grade-weighting that matches your school's curriculum — not a curriculum that matches the software.
Fee structures, invoices, collections, receipts, waivers, trial balance, and student statements, with a finance gate separate from classroom roles.
Author, submit, approve. Drafts to the head teacher; approval workflow built in. Print-ready lesson notes, every Friday.
Author quizzes once, deliver to the whole class, auto-grade multiple-choice answers. Built for the classroom, not the exam hall.
Maths and Science across the NaCCA primary curriculum, with playful interactions designed for shared classroom devices.
Guided visual mathematics lessons with fraction bars, number lines, shapes, and practice packs students can manipulate.
A student reading shelf with levelled stories, progress, and illustrated reading experiences that make literacy feel alive.
Junior-high curriculum coverage with diagnostic quizzes, BECE-style practice, and topic mastery that students can see.
A virtual science lab. Build circuits, watch refraction, set up experiments, and observe results without waiting for equipment.
One hub. Today's classes, due quizzes, last term's grades, and quick launches into the learning apps assigned to each student.
Attendance, grades, and the day-to-day at a glance — designed for parents who'll mostly check this on their phone, on slow networks.
A teacher's day, in one screen: take attendance, grade work, post a lesson plan, launch a CBT — without four tabs and three logins.
For schools as they actually are.
Most school software is designed for a school that doesn't exist — one with unlimited bandwidth, parents on iPads, and an IT department in the basement. Simusim is built for the school that has none of those things and still needs to run a tight ship.
Offline once downloaded.
Lessons cache on first run and work through dropped connectivity. Every screen assumes a parent on a mid-range Android, on 3G, on a bus — mobile is the desktop here.
NaCCA-aligned learning.
Simu Primary maps to NaCCA Basic 1–6, Simu JHS covers the BECE years, and Simu Science Lab is built from the ground up for the NaCCA curriculum.
Free ops. Pay only for apps.
The operations suite is free for schools that onboard their students. You only pay for the optional learning apps your students use — bank transfer or mobile money, recorded by our team from the source of truth, no Stripe webhook gating your access.
Paper still matters.
Login cards print on A4 in pre-cut grids. Term reports print to PDF without a designer's intervention. Class lists are made for the photocopier on the corridor.
From spreadsheet to pilot workspace
in under fifteen minutes.
Our staff onboards your school personally. In a focused setup call we configure your slug, validate your roster, generate PINs, and prepare a print-ready stack of login cards. Card distribution and the first sign-in happen on your school's timeline — we're on the other end of every question.
Set your slug.
Name, slug, country, term start. A short setup form, with Ghana-first defaults for phone numbers, currency, and primary & JHS school levels.
Upload your roster.
One spreadsheet. Students, parents, teachers, and the parent ↔ child links. We validate the data, dry-run the import, and let you fix the broken rows in place.
Generate PINs.
We mint a unique code & PIN per student. Parents get a printed PIN letter with their child's card. Teachers get a phone-PIN walkthrough. Admins pick their password & enable MFA.
Print login cards.
Login cards exported as a single PDF, eight to a page. Apps assigned to classes. We send you a Monday-morning sign-in test you can do with a kid in five seconds.
Quietly uncompromising.
Schools handle the data of minors. We treat that as the responsibility it is — with a model that physically prevents one school's data from touching another's, even if we wrote a buggy query. Belt, braces, and a third belt for good measure.
-
I.
One org per school. Always.Every row in the database is stamped with an
org_id. Every query is filtered by it. PostgreSQL row-level security enforces this at the engine level — not just the app. There is no "shared" data because there is no shared data. -
II.
Authorization, twice.At the API edge: "is this user allowed to call this endpoint?" At the data layer: "does the row they're touching belong to their school?" Either failing aborts the request. We don't trust a single check with the data of children.
-
III.
PIN-aware lockout.A 4-digit PIN is, by maths, weak. So Simusim treats every failed PIN attempt as serious: 8 strikes lock the account for 30 minutes, every attempt is logged, and school admins can review login activity for their org.
-
IV.
Entitlements live outside the token.A lapsed subscription doesn't wait for tokens to expire. App access is checked against the Platform API at session start, so overdue or reactivated schools follow the subscription state without stale token claims — a payment lapse never holds a child's records hostage.
-
V.
Audit log, by default.Key account, payment, entitlement, and parent-child relationship changes are written to the audit log with who, when, from where, and what changed.
Asked at every walkthrough.
The honest answers to what heads, bursars, and proprietors ask us first — so you can bring the harder questions to the walkthrough.
What does Simusim cost a school?
We already manage with WhatsApp, Excel, and a paper register. Why change?
Our roster is in a notebook. Can we still start?
What happens when the internet is down?
Who owns the school's data?
Do teachers need training?
Come see the platform your school already deserves.
Bring a roster — even a sample class is enough. We'll show your school login path, the admin console, the printed cards, finance, the portals, and the learning apps your staff and parents will actually use.
Are you a teacher rather than a decision-maker? There's a page made for you to share with your head teacher →