Durable Regression Testing

Turn Real Events into
Repeatable Replay Cases.

Save a captured webhook or normalized email with one fixed target and deterministic assertions. The case survives source retention, and every run keeps immutable evidence of what was sent, what came back, and why it passed or failed.

A Regression Check Built from Production Reality

Replay Cases replace one-off, memory-based retesting with reusable checks owned by the endpoint.

Fixed, Safe Target

Each case version owns one encrypted target. Runs cannot override it, and target safety is checked again before sending.

Deterministic Assertions

Require expected status codes or a status class, a strict JSON subset, or both. No scripts, regex, or hidden coercion.

Immutable Run Evidence

Every rerun creates a new record with bounded outbound, response, assertion, timing, and usage evidence.

From Capture to Durable Check

Cases work with captured webhooks and normalized email events, and remain runnable after the original event expires.

1

Save the real event

Start from a request detail or replay workflow, choose the fixed target, and name the case.

2

Define the expected result

Require a status result, a type-strict JSON subset, or both before the case can run.

3

Run and inspect

Run from the web UI, REST API, or MCP and inspect the retained evidence for every attempt.

Available on Every Account Plan

Replay Cases are included during the selected plan trial and after activation. Existing cases remain readable after a downgrade, but new saves pause while the account is over its limit.

Pro

10Replay Cases

Team

50Replay Cases

Business

200Replay Cases

Make Every Fix Repeatable

Save the event that exposed the bug, lock in the expected result, and rerun it whenever the handler changes.