Why we built Tenurex
We've been the ones scrambling for evidence at 11pm before an auditor call. There's a better way.
The story behind Tenurex
Andre spent years running security and compliance programs at fintech companies, overseeing SOC 2 and ISO 27001 audits from the inside. He saw the same pattern every time: engineers interrupted for two weeks to produce evidence that was already six months stale. He founded Tenurex in 2025 to replace that cycle with continuous, API-native monitoring. Philadelphia-based, independently funded.
The Tenurex team
How we work
Read-only as a philosophy
We never take write access. If Tenurex can observe a control state without touching it, that's what we do. This isn't just a security feature — it's how we think about trust.
Evidence should be verifiable, not decorative
Audit evidence that can't be traced to a real system state is theater. Every piece of evidence Tenurex generates includes the source, the timestamp, and the test that produced it.
Built for compliance professionals, not lawyers
We don't speak in abstract compliance language. Tenurex maps controls to the systems your engineers actually run, with terminology your team already uses.