We are building the digital infrastructure for education.
Schoolspine started in Kampala from a plain observation: schools run on software that does not talk to itself. Attendance in one system, fees in another, results in a third — and nobody able to see the whole child.
Kampala
Where we build
Africa first
Built for the region
Nursery → University
Every stage
To become the world's most trusted operating system for schools — connecting administrators, educators, students and parents through one secure, intelligent platform.
Every release is held to one standard: secure, fast, tested, audited, configurable and documented — or it does not ship.
Five things a school is buying when it buys Schoolspine.
01
Your school’s data is protected.
02
Your school controls who sees what.
03
Your school configures the platform without requesting code changes.
04
Every important action is traceable.
05
The platform grows with your institution.
Values that survive contact with a deadline.
Security by design
Not a feature we add at the end. It is the first thing built and the reason for most architectural decisions.
Simplicity over complexity
Powerful software does not have to feel complicated. If a task needs training, we designed it wrong.
Customer obsession
Schools tell us what breaks. We build for the registrar at 7am, not for a feature comparison table.
Reliability
A school depends on this every single day of term. Uptime is not a metric, it is the product.
Transparency
Every important action is visible and attributable. Including ours.
Integrity
We will tell you what Schoolspine cannot do yet. Every time.
The people behind the platform.
You deal directly with the people who build Schoolspine. Decisions happen in a day, your feedback lands in the product rather than in a backlog queue, and whoever answers your question is able to act on it.
Marybright Etim
Founder — Product & Engineering
Sets the product direction and architecture, and writes the platform: authentication, tenancy, permissions, audit and the school modules built on top of them.
Joan Katushabe
Founder — Growth & Partnerships
Works directly with schools — pilots, onboarding, and the relationships that decide whether the product actually fits how an institution runs.
What Schoolspine will never become.
Defining the boundaries matters as much as defining the ambition. These are the things we have decided in advance not to do, however convenient they become.
- A collection of disconnected modules.
- A platform driven by customer-specific code branches.
- A system that compromises security for convenience.
- A product where permissions exist only in the interface.
- A codebase where business rules are duplicated across modules.
Talk to the people building it.
A conversation about your school with the people who build the platform.