About
Yakini means certainty.
Yakini (ya-KEE-nee) is Swahili for certainty. We build it so that engineering leaders can know what has really been delivered, and so that work is judged on evidence rather than on status updates.
Why Yakini exists
Decisions are made on status. Status is rarely checked.
What decisions rest on
Software decisions rest on what people report: a ticket in Done, a percentage in a status report, a green line on a roadmap. Checking those claims means reading code, test runs and deployment records that live in different tools, so most of the time nobody does.
Sample dataWhat decisions rest on, and what checking them takes. What Yakini does
Yakini does that checking for each item declared done, and shows its working. It says what the evidence supports, what it contradicts and where it can’t tell, so leaders can rely on what they’re told and engineers can show what they built.
Sample dataThree answers, each with its reason. Fair by design
Because its findings are about work people did, fairness is part of the design: engineers see findings first, can answer them, and are never ranked or scored.
Sample dataA finding, as the engineer whose work it is sees it.
Who builds it
Yakini is built by Intevia Ltd.
Intevia Ltd is based in Nairobi, Kenya. Yakini is new: if you’d like to see it, or to talk about evaluating it with your teams, we’d be glad to hear from you.
Intevia Ltd
The company behind Yakini
- Based in
- Nairobi, Kenya
- Makes
- Yakini, engineering delivery assurance
- Website
- yakini.io
How we work
Four principles, built in.
Yakini publishes findings about work people did. The rules for doing that fairly are built into the product, not left to policy.
Evidence, not status.
A verdict cites code at a commit, an executed test or a delivery record. Claims in tickets are things to check, never evidence.
Abstain rather than guess.
When evidence is missing or out of reach, or the budget runs out, the verdict is Unverified and says why.
Fair to engineers.
Findings stay private to the assignee during a review window. Engineers can add context and challenge any finding.
About delivery, not people.
Yakini never ranks, scores or compares individuals. It reports on work, not on the people who did it.
Contact
How to reach us.
Write to the right address, or use the request form.
See Yakini with your own questions.
We’ll walk you through Yakini with a sample organization, show the evidence behind each verdict, and answer your questions about deployment, security and models.
- Hosted, dedicated or self-hosted
- Your choice of models, self-hosted too
- Pricing set out in a written proposal