Company
Krutho is an authorization company.
We are building infrastructure that lets the receiving system evaluate established authority where it makes the decision.
One question helps guide the work:
What actually needs to participate when this decision is made?
It is one way Krutho tests inherited dependencies against the responsibility and requirements of a particular decision.
Krutho exists to make participation in an authorization decision a consequence of what that decision requires, rather than something inherited by default.
Authority remains governed. Decisions happen where they belong.
Built to be tested.
A different architecture has to survive more than a diagram.
Krutho is being developed through working implementations, controlled demonstrations and concrete decision scenarios.
The architecture is tested against specific decisions and conditions, with evidence available for the parts we have exercised.
The people leading Krutho.
Krutho brings together experience across authorization, identity, security, architecture, product, strategy and design.
Anthony Maley
CEO
Anthony has built and led technology businesses, carrying new capability from early exploration through to commercial use. He works across technology, product and commercial development, and his part of this is finding where a capability opens something that was not available before, then pushing that opportunity until it is real.
Kristof Sajdak
CTO
Kristof is a systems architect working in distributed systems and the structures a complex idea needs in order to hold up in practice. On Krutho that is the authority model itself: what a verifier has to hold, what a credential has to carry, and the conditions the system must still satisfy when the center cannot be reached.
Daniel Donoghue
Chief Design Officer
Daniel is a design director working across brand, product and digital systems. His work turns what a technology makes possible into something an organization can understand and operate, giving an emerging model form and shaping the product and system around the change it is meant to create.
Building from the decision.
What actually needs to participate when this decision is made?
Sometimes the answer includes the systems that established what the decision relies on. Sometimes it does not.
Krutho makes that an architectural choice.