Company

The people
behind Retrace.

We're building a better way to understand software execution.

Retrace is based in London. We work directly with engineering teams to understand the investigations they need to solve.

Meet the team

Henry Yates, co-founder and CEO of Retrace

Henry Yates

Co-founder & CEO

Henry leads Retrace's commercial strategy, working with customers and partners to bring its technology to real-world engineering problems.

Henry co-founded his first business, Face, in 2002, which was later acquired by Cello PLC. In 2008, he founded Estatecreate, a profitable SaaS business. He was also the first investor in Hyperledger, subsequently acquired by Digital Asset Holdings, where he met Nathan.

Nathan Matthews, co-founder and CTO of Retrace, with a city and hills behind him

Nathan Matthews

Co-founder & CTO

Nathan leads Retrace's technical development and is the inventor of its underlying record-replay and provenance technology.

His background combines game programming with a fascination for how interpreters work. Frustrated that computers couldn't explain what they had done, he conceived Retrace as a way to reconstruct past executions and understand exactly how software arrived at a result.

Daniel Patrascanu with three border collies

Daniel Patrascanu

Test & Tooling Engineer

Daniel develops the test harnesses and engineering tools that support Retrace's development. His work helps the team test changes systematically and check how the software behaves.

Daniel Dinnyes, AI specialist at Retrace

Daniel Dinnyes

AI Specialist

Daniel is Retrace's AI specialist. His engineering work includes deterministic record-replay, Python data observability and provenance.

Why we're
building Retrace.

Software can finish successfully and still produce a result someone questions later. An agent takes an unexpected action. A customer disputes a calculation. A failure disappears when a test runs again.

When the inputs, service responses or execution order have changed, another run may tell a different story. We want engineers to be able to return to the recorded run and inspect the values and code paths behind its result.

Deterministic record and replay is the foundation. Our work on data provenance follows the same question: how was this value created or changed?

See how Retrace works

Advice and backing

Yury Selivanov

Technical adviser

Python core contributor.

Investor

Backing Retrace's work on understanding software execution.

Work directly with the people building Retrace.

We're speaking with engineering teams about difficult investigations. Bring a recent example and we'll explore where a recorded Python execution could help.

Discuss an investigation

A 25-minute conversation.