About me
A few words about my work, how I think about identity and what I share here.
The IAM architect#
Identity is rarely the most visible part of a system. Yet it determines who can access what, how applications trust one another and what happens when a user journey breaks. That intersection of security, user experience and architecture is what interests me.
I work with IAM, SSO and Keycloak because solid identity foundations make products safer, but also easier to evolve and operate.
The consultant#
I enjoy concrete problems: a platform that is hard to evolve, an integration that will not scale, authentication journeys that have become too complex, or teams that need to regain control of their IAM.
My role is to bring clarity back to these systems, then help teams build a solution they understand, can maintain and can trust.
The engineer#
I stay close to the code and to operations. Keycloak, identity protocols, cloud, Kubernetes and automation are the tools I use to turn an architecture into a platform people can actually run.
I favour solutions that are explicit, documented and testable: solutions that hold up through change, incidents and time.
The open-source contributor#
The projects on this site are extensions of questions I encounter in the field. They let me explore ideas, make certain problems easier to test and share work that may be useful to other teams.
I also contribute to the Keycloak project and publish technical notes on my blog.
To discuss identity, Keycloak or a concrete security challenge, get in touch.
