Founded in Kampala · Software Product Company
Ozak Technologies engineers software products, enterprise systems, and SaaS platforms for organizations across East Africa — with full source ownership on every delivery.
Our story
Ozak Technologies was started in Kampala by Matovu Mathew Phillip and Ssendisa Denis with a straightforward conviction: organizations in East Africa deserve software engineering that is as disciplined, documented, and maintainable as anything built globally — without the overhead of hiring a full in-house team before they're ready.
The problem we kept seeing was the same. Organizations — schools, hostels, cooperatives, sports bodies — were either stuck on paper and spreadsheets, or paying for generic software that didn't fit how they actually operated. The alternative, custom development from vendors that disappear after delivery, left them with codebases no one could maintain. Ozak exists to close that gap: build systems tailored to the problem, document them properly, and transfer full ownership.
We started by shipping Assessor HMS — a live hostel management platform on production infrastructure. DevPath, our developer learning platform, and a School Management System for Ugandan academic administration are in active development. Sports technology platforms extend our capability into league management and fan-facing interfaces.
We're building Ozak to be a software product and technology company — not a project shop. We're early-stage and honest about that. What we have is a production-grade stack, working products, and a commitment to engineering discipline on every engagement we take on.
To become East Africa's most trusted software product company for operational systems — where institutions, cooperatives, and enterprises run on platforms engineered from Kampala with full client ownership.
To design, build, and deploy operational software that replaces manual processes — API-first, documented, deployed to production, and transferred with full ownership.
Core values
We design around partial payments, term fees, and room occupancy—not idealised demos that break in production.
Assessor HMS runs on Vercel and Render. A feature isn't done until it works in your environment.
Architecture notes, deployment guides, and source repos go to you on delivery. No lock-in.
Deployed, in development, and planned are different states—and we label them that way everywhere.
Mobile money, local payment behaviour, and Ugandan operational reality inform every integration we build.
Leadership
Ozak is led by two full-stack engineers who write production code on every project. We're an early-stage company—no large leadership bench, no inflated titles.
"We build software the way you'd build infrastructure for a city — to last, to scale, and to serve the people who depend on it every single day."
Matovu is a full-stack engineer who leads technical architecture and client discovery. He focuses on translating operational problems—hostel payments, school fees, league fixtures—into systems that deploy and last.
"Every project ends with source code in your repo and docs your team can follow. That's non-negotiable."
Ssendisa is a full-stack engineer who handles operations, deployment, and delivery. He ensures what we build runs reliably in production and hands over cleanly to clients.
Why Ozak
We start with how your team actually works—registers, ledgers, approvals—not technology for its own sake.
Resident/Stay separation, fee ledgers, room state machines—designed for the administrator who comes after us.
Authentication, role-based access, and careful handling of payment and personal data from the first commit.
You leave with complete ownership—source, infrastructure configuration, and documentation.
React, TypeScript, Django REST, PostgreSQL—the same stack running Assessor HMS today.
The engineers in your discovery call write your code. No bait-and-switch to junior teams.
Let's build
Explore our products or request a consultation — a 30-minute call is usually enough to know if we're a fit.
