Skip to main content
TavechTavech
About

We are building the digital infrastructure for education.

Tavech 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.

The product promise

Five things a school is buying when it buys Tavech.

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.

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 Tavech cannot do yet. Every time.

Who is building this

The people behind the platform.

You deal directly with the people who build Tavech. 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 builds it — sign-in, permissions, audit and every school module that stands on 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.

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 customer 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.