Free Best fit
— Keeps 7 days at most
- 3 services
- 5M events a month
- 7-day retention
- Unlimited replays
- Community support
Deterministic replay for backend teams
Fenwright records the events your services already emit. When something breaks, you open the hour, drag through it event by event, and see exactly what the system held — then bisect to the event that caused it.
npm install @fenwright/recorder 340 backend teams · rated 4.8/5 by 212 engineering leads · 14-day trial, no card
Live demo, recorded data
Drag the head, step event by event, or jump to a moment. The state on the right is refolded from the recording every time.
Head at t+20:15
Event log
State at the head
Folded from 14 of 26 events. Drag back and the state is refolded from 02:00, so it always matches.
Replays are free
You pay for events recorded and days kept. Replaying, diffing and bisecting never cost extra.
10 minutes to first hour
One library, one call at start-up. Your first window is replayable the moment it closes.
99.9% ingest, in writing
Miss it in a calendar month and the next month is free. You do not have to ask.
Redacted at source
Fields you name are dropped inside your process. They never cross the wire.
Plans
Every plan has the whole product. What changes is how many events you keep and for how long.
Free
free for good, no card
Three services, five million events a month and a week of history. Enough to replay the bug that has been annoying you since Tuesday.
See the Free plan
From £290
a month, 50M events included
Unlimited services, fifty million events included, up to ninety days of retention, and diff and bisect across any two hours.
See the Team plan
From £1,900
a month, billed annually
Five hundred million events included, up to a year of retention, SSO and audit log, a choice of region, and a self-hosted option.
See the Enterprise plan
Why we built it
In 2021 an incident review at a London payments company ran for four hours, and the one question nobody could answer was what the queue held at 02:18. The recording existed only in three people’s memories. Fenwright is the tool they wrote so that never happens again.
How it works
No agent, no proxy, no change to how traffic flows. The recorder is a library you ship with the service.
Install the recorder
One library and one call at start-up. Keys are scoped to a single service.
Record every event
Requests, queue messages and queries are buffered off the request path and shipped in batches.
Replay any hour
Open a window in the browser or pull it to your laptop and step through it event by event.
Bisect to the cause
Diff a bad hour against a good one and let bisect name the first event where they part.
Usage pricing
Move the slider to your monthly event volume and pick how long to keep it. The cheapest plan that fits is marked.
A busy API service emits roughly 1–3M events a day. Replays, diffs, bisects and seats are never charged.
Free Best fit
— Keeps 7 days at most
Team Best fit
£290 a month
Enterprise Best fit
£1,900 a month
Compared
Keep your log search and your APM. Fenwright answers the question they were not built for: what did the system hold at that moment?
| Feature | Fenwright | Log search | APM tracing |
|---|---|---|---|
| State at any moment | Yes Folded from every event | No Lines, not state | Partial Per request only |
| Reproduce on a laptop | Yes Pull any window | No Read-only | No Read-only |
| Find the first bad event | Yes Bisect two hours | Partial By hand, with queries | Partial Slow spans only |
| Cross-service timeline | Yes One ordered log | Partial If clocks agree | Yes Via trace IDs |
| Cost of looking | Yes Replays are free | No Billed per query | Partial Sampled to save cost |
| Personal data kept out | Yes Dropped at source | Partial Masked on arrival | Partial Depends on agent |
Results
4.8 out of 5 from 212 engineering leads
MTTR down 63%
“We stopped arguing about what the queue was doing at 02:14 and started replaying it. Median time to resolve went from 3 h 10 to 70 minutes in one quarter.”
11 min to root cause
“Bisect pointed at a missing index before the incident channel had finished its first round of guesses. The write-up quotes offsets instead of memories.”
4 flaky bugs closed
“Four race conditions that had lived in our backlog for a year. Each one reproduced on a laptop from a recorded hour, first try.”
£0 per replay
“Our log vendor bills every query, so nobody looks twice. Here replays are free, and people replay the hour before they open a ticket.”
Journal
FAQ
Type a word to filter. Anything missing goes straight to an engineer.
Product
The events your services already emit — requests, queue messages, database calls, deploy markers — written by a small recorder library as they happen. Nothing is proxied and no traffic changes path.
Product
No. A log search finds lines. A replay folds every event in a window into state, so you can stop at any offset and see what the system actually held: queue depth, workers, latency, the value of a field.
Product
Yes. `fenwright pull` downloads any window as newline-delimited JSON and `fenwright replay` runs it locally against your code. The export is unlimited on every plan.
Product
Anything you did not record, and third-party responses such as a card network’s reply. Those are re-fetched at replay time and marked on screen, so a replayed number is never passed off as historic.
Setup
About ten minutes per service: install the library, add one call at start-up with a service key, deploy. The first hour is replayable as soon as it closes.
No question matches that. Write to us and a person who builds the product will answer.
Install the recorder on one service. The first hour is replayable the moment it closes, and Free never asks for a card.
npm install @fenwright/recorder