Ryan Hurst Joins M42 as Principal

Ryan has been part of the M42 journey for a while now — present for a lot of the conversations, engagements, and work that shaped where the company is today. Formalizing that as Principal is less an announcement than an acknowledgment of what's already been true.

Two years ago, we started from a simple but difficult premise: the infrastructure most organizations rely on for identity, transport security, and trust was designed for environments with shared control and stable boundaries. That assumption breaks badly in the fragmented, multi-domain systems that define modern defense and coalition networks. It's the core problem M42 was built to solve.

Ryan understood that tension without much explanation. His work has consistently sat at the intersection of cryptography, identity, and trust infrastructure, not as theory, but as systems that have to hold up in production at scale.

His background includes:

  • Leading Cloud Security and Trust Services at Google, including founding Google Trust Services, one of the world's largest certificate authorities
  • Helping build Let's Encrypt, which made HTTPS the default for the web
  • Advancing Certificate Transparency and Binary Transparency, now standard mechanisms for ecosystem integrity
  • Building and managing Microsoft's Root Program, leading Cryptography in Windows, and contributing to standards including EAP-TLS and PKIX
  • Leading recovery and rebuilding at GlobalSign following the DigiNotar incident
  • Building systems managing over $100M in Bitcoin at 21.co

He currently works through Peculiar Ventures with teams building in AI, security, encryption, and identity.

What's mattered to us is how Ryan thinks about problems — specifically, where assumptions about control and uniformity break down when systems move from controlled environments into real ones. That perspective has shaped how we've approached architecture, practioner and warfighter requirements, and the design of QHx from early on.

His Principal role reflects the level at which he operates with the company. Internally, he continues as Special Advisor, working directly with leadership on architecture, engineering direction, and strategy.