FENWRIGHT

About

We got tired of arguing with graphs.

Fenwright is nineteen people in one office in Aldgate. Three of us spent years on call before we built this, and we still answer the support queue ourselves.

Hands resting above a slim white keyboard on a pale desk

How it started

In the spring of 2021, a payments company in London lost ninety minutes of checkout traffic at two in the morning. The incident review ran for four hours. Everyone had the dashboards; nobody could say what the order queue held at 02:18, when the workers started failing. Three engineers gave three answers, and all of them were sincere.

Two of those engineers, and the SRE who chaired the review, left that summer to build the tool they had wanted in the room: something that keeps every event and can tell you, exactly and repeatably, what the system held at any moment.

We still price it the way we wanted to buy it. You pay for what you record and how long you keep it. Looking is free, because a tool that charges for looking teaches people not to.

A person at a dark desk seen from above, one hand on a white keyboard

Who you will talk to

No account managers. The people who build the product answer the email.

Five years in five lines

  1. 2021 A four-hour incident review, one unanswerable question, and a weekend prototype that recorded a single queue.
  2. 2022 First paying team. Node and Python recorders. Bisect ships after a customer asked for it three times.
  3. 2024 Go and Java recorders, the Frankfurt region, and the first self-hosted Enterprise install.
  4. 2026 340 teams, 1.2 million hours replayed, and still 19 people in one office in Aldgate.
A city skyline seen through the tall windows of a dark office

Come and see the office

We are at Aldgate Works, 14 Goulston Street, London. Enterprise evaluations often start with a morning here and a replay of your own incident.

npm install @fenwright/recorder