Skip to main content

About We got tired of rebuilding the truth from tickets.

Identity work looked automated from a distance. Up close, it was still people forwarding requests, repeating clicks and trying to prove what happened after the fact.

Tenriva began in Manchester to give that work a proper record: one place where the request, the decision and what happened next belong together.

Manchester’s skyline: glass towers rising behind Victorian red-brick warehouses and slate roofs.
Manchester, where Tenriva began.

The team

Practitioners before platform people.

We are building from direct experience of Microsoft environments, operational hand-offs and the scrutiny that follows an access mistake. That keeps the product grounded in the work IT teams actually have to complete.

Ugochukwu Ibeawuchi, founder of Tenriva
Ugochukwu IbeawuchiFounder · Product and operations
Chiemeka Madufor, co-founder of Tenriva
Chiemeka MaduforCo-founder · Engineering

Principles

A few rules we refuse to blur.

Make ownership visible
Every important request and approval should have a named person attached.
Automate repetition, not judgement
Software should remove administrative drag without disguising consequential decisions.
Leave a record behind
A finished request should show who asked for it, who approved it and what happened, without a separate reconstruction project.
Say what is not finished
Roadmap, control alignment and certification are different things. We label them accordingly.

Next step

Bring the awkward lifecycle case.

Start the trial and test Tenriva on it yourself. Or book a walkthrough, and we’ll look at who is involved, where it slows down and whether Tenriva fits.