Python execution explainability

Your Python code produced a result. Retrace shows you why.

Retrace records continuously, at under 1% overhead*, so the evidence exists before anyone asks. When a result is questioned, trace it back to the inputs that produced it.

Illustrative checkout example

  1. Mon · order 18339£188.40 completed
  2. Mon · order 18340£96.12 completed
  3. Tue · order 18342£424.60 completed; the recording the engineer opens
  4. Wed · order 18343£310.75 completed
  5. Wed · order 18344£58.90 completed

Recording · always on · under 1% overhead*

Engineer opens Tuesday's recorded run

Order 18342 completed normally on Tuesday. On Thursday a customer asked about it. Retrace had already recorded it.

On supported workloads. Overhead depends on how much I/O an application performs.

Provenance · illustrative example

Why is this value what it is?

Select a result in a recorded run. Provenance follows it back through the operations and inputs that produced it, all the way to what the run actually received.

What the run received

What the code did

Combined

Start here

Selected result£424.60
checkout.py:42Order total216.84 + 207.76 = 424.60
pricing.py:118 · thread AItems 1–22 × 100.00 × 1.0842 = 216.84
Recorded · 09:14:02.118Rate service response · initial raterate = 1.0842
Thread B · background refreshThe rate changed here, mid-order.
Recorded · 09:14:02.131Rate service response · after refreshrate = 1.0388
pricing.py:118 · thread AItems 3–42 × 100.00 × 1.0388 = 207.76
The finding

This order used two exchange rates.

Items 1–2 at 1.0842, items 3–4 at 1.0388 after a background refresh. Using the initial rate of 1.0842 for all four items would have produced £433.68.

The source says this could happen. Only the recording shows it did.

Illustrative example.

The questions behind the investigation

An unexpected result deserves an explanation.

Agents and automation

An agent took an unexpected action.

Your trace has the model and tool responses. Provenance shows which value decided the branch that became the action.

See how this works for an agent →

Historical calculations

A price, bill or decision is challenged.

The calculation succeeded, but its inputs may have changed since. Provenance traces this result back to the inputs that produced it.

See how to explain a past result →

CI and SDK support

A failure is hard to reconstruct.

A CI test passes on rerun, or a customer's integration fails and nobody can reproduce it. Replay the original run, not a new attempt.

See the failed-test replay walkthrough →

How it works

Record continuously. Explain results later.

Recording runs alongside your Python application in your environment, always on. When a result is questioned, cloud Replay and Provenance explain the recorded run, with VS Code on your machine as the developer interface.

While your application runs

Your application

Recorded continuously: external calls, returned values, exceptions and thread ordering.

The recording

The external interactions and ordering needed to reconstruct the execution.

When a result is questioned

Cloud Replay

Return to the recorded run and step forwards and backwards through it in VS Code.

Provenance

Select a result to see the inputs, operations and source locations that produced it.

The evidence already exists.

Because recording is always on, nobody needs to predict which run will be questioned. A run can report success and still need explaining later.

Private preview

Start with one Python worker or workflow.

We record one worker or workflow continuously, then explain the next result your team questions. Every pilot includes Provenance.

Runtime and dependencies
Retrace runs on CPython 3.11–3.15 on 64-bit Linux and macOS. We check your libraries, native extensions and concurrency against the current build. See all requirements →
Recording and data
Recording runs in your environment, and by default nothing is uploaded automatically. Replay and Provenance run in Retrace's cloud. We agree how recordings reach Replay, which runs to keep and who may inspect the data.
A useful first investigation
We choose a concrete question and agree how to judge the explanation. If you want AI-assisted investigation, we agree how it can access the evidence.

Talk to the founders

What was difficult to establish?

Tell us about an investigation your team found difficult: an unexpected agent action, a disputed result, or a Python failure that was hard to explain.

We'll discuss what happened, what your existing tools recovered, and what evidence was missing.

A 25-minute conversation

Bring a recent example. If there is a fit, we'll agree one Python worker or workflow to record and investigate together.

A past incident tells us what to record, so the next one is explained.

We use what you send to respond to your enquiry. See the privacy notice. Prefer email? Write to henry@retracesoftware.com.

Building a better way to understand software execution.

Retrace is built in London by Henry Yates and Nathan Matthews. We work with engineering teams to explain the results their Python systems produce.

FoundersHenry Yates and Nathan Matthews
AdviserYury SelivanovCPython core developer, author of async/await (PEP 492), creator of uvloop
Backed byPreston-Werner Ventures