Initializing Redox Engine

Studio product · 2026

RISMS

School management where the school keeps its own money

RISMS — School management where the school keeps its own money
  • Straight to the schoolFees go
  • First-classCash payments
  • Refused at entryDouble-booking

What it actually does

  • School fees never touch us

    Each institution plugs in its own payment credentials, so parents pay the school and the money lands in the school's account. We found a withdrawal path that could pay out money the platform never held — rather than patch it, we removed custody entirely.

  • Cash is a real payment method, not a workaround

    A parent walks into the bursary with notes and a staff member records it against the student. Cash is implemented as a payment gateway alongside the card processor, so it produces the same receipts, the same ledger entries and the same audit trail.

  • Fees you can save toward

    A student wallet lets a family put money aside a little at a time — including cash handed over the counter — until it covers the term. School fees rarely arrive as one payment on one day, and pretending otherwise is how families end up locked out.

  • Nothing double-books, school-wide

    Every timetable slot is checked against the teacher's schedule and the class's schedule before it is allowed to exist. Two subjects cannot land on one class, and no teacher can be in two rooms at once — the clash is refused at entry, not found later.

  • Scores go in once

    Teachers enter scores against the school's own assessment weighting. Totals, grades and end-of-session promotion follow from that — no spreadsheet reconciliation at the end of term.

  • Infrastructure, not an intermediary

    We run the system a school operates on. The school keeps its own payment account, its own banking relationship and its own relationship with parents. If we disappeared tomorrow, none of a school's money would be sitting anywhere it could not reach.

  • Money is an append-only ledger

    Wallet movements are recorded as entries that are never edited or deleted, and balances are derived from them. A fee dispute can be traced rather than argued.

  • Four surfaces, four audiences

    Platform admin, institution staff, student and guardian each get their own layout and navigation — and a guardian's single login covers wards across different schools. Every institution routes on its own slug behind its own branded login, so there is no generic dashboard to land on by accident.

What we built

Academics, staff, students, timetabling and fees for African institutions, split across four persona surfaces so no screen serves two audiences at once. Fees are collected on each school's own payment credentials — the platform records the money without ever holding it.

Stack

  • Laravel 11
  • PHP 8.3
  • Vue 3
  • Inertia v2
  • Tailwind 4
  • Paystack
Visit project

Start here

Start a Reaction

Tell us what you are building and what is currently in the way. We reply to every enquiry within two working days — with a real answer, not a calendar link.