Schools run on softwarethat does not talk to itself.
Tavech started in Kampala from that one plain observation. Attendance in one system, fees in another, results in a third — so the child falling behind and the child whose fees lapsed in March are never known to be the same child. We are building the one record underneath all of it.
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.
The product promise
Five things your school has from the first day.
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.
How we work
Values that survive contact with a deadline.
Security by design
Not a feature we add at the end. It was the first thing built, and it is the reason behind most of the decisions underneath.
Simplicity over complexity
Powerful software does not have to feel complicated. If a task needs training, we designed it wrong.
Schools first
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 Tavech cannot do yet. Every time.
Boundaries
What Tavech 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 product quietly forked for one school and left behind at the next update.
- A system that compromises security for convenience.
- A product where permissions exist only in the interface.
- A place where the same rule is written five times and disagrees with itself.
Talk to the people building it.
A conversation about your school with the people who build the platform.