Join the waitlist
The Fairlead Recorder extension icon

fair·lead, n. The fitting a line runs through so it does not chafe.

Recorder for teams: The same report from every tester, filed to your issue tracker.

An admin sets recording and redaction once, in the project. Every tester follows it and files from the side panel, evidence attached.

Join the waitlistSample bundle ZIP

Review captured content before sending it.

The recorder panel docked beside the page under test, filing a bug report
Filing from the side panel, to a new issue or an existing one, with screenshots attached. Development build.

Free. Forever.

The extension and its team features cost nothing. No plan, no trial, no seat fee.

One project setup reaches every tester.

An admin sets the recording scope, the redaction keys and the storage policy once, in the project. Each tester's extension receives them when it signs in, so the whole team captures and redacts the same way.

A signed-in tester cannot edit these settings from the extension. Changing them is a project change, made in one place.

What a tester's extension receives from the project. Sample values.
project     checkout-web
record      shop.example, *.shop.example
network     api.shop.example
redact      authorization, set-cookie, session_token,
            customer.email, card_number
storage     Save recorded data in Data Plane: on
            Data Plane: Fairlead cloud
file to     Jira  SHOP
            GitHub  your-org/checkout-web

Swipe the diagram

Your project in Fairleadscope · redaction keys · storage policyon sign-inYour browser. Redaction happens here.Capturesteps · HAR · consoleReview evidencethe project's keysReportreviewed by youissue text and chosen screenshotsBridgekeeps no copyYour tracker or TMSJira · GitHub · Azure · Otherthe reporta written description, on requestYour Data Planestores the project's reportsFairlead cloud or your ownrequest IDsadded during capture, third-party requests includedRequest destinationsyour backend logs the IDs
The project's settings come down to the extension when it signs in. Automatic redaction covers selected keys and structures; inspect the remaining content. While recording, the extension adds request IDs to the page's requests, third-party ones included, so your backend can log them. The issue text and chosen screenshots go through Bridge to your tracker. The report goes to your project's Data Plane, the service that stores reports and can write a description from one.
Your project in Fairleadscope · redaction keys · storage policyon sign-inYour browser. Redaction happens here.Capturesteps · HAR · consoleReview evidencethe project's keysReportreviewed by youissue text, screenshotsBridgekeeps no copyYour tracker or TMSJira · GitHub · Azure · OtherreportdescriptionYour Data Planestores the project's reportsFairlead cloud or your ownrequest IDsduring capture, third-party includedRequest destinationsyour backend logs the IDs
The project's settings come down to the extension when it signs in. Automatic redaction covers selected keys and structures; inspect the remaining content. While recording, the extension adds request IDs to the page's requests, third-party ones included, so your backend can log them. The issue text and chosen screenshots go through Bridge to your tracker. The report goes to your project's Data Plane, the service that stores reports and can write a description from one.

Find a recorded request in your backend logs.

While recording, the extension sends x-fairlead-reproduction-id with intercepted requests. Optional issue and per-request identifiers help narrow the search when your application logs them.

Header injection is not restricted by the project's capture rules, so the identifiers also reach third-party requests. Recording on your own sends none. Configure and check correlation.

Illustrative server log, filtered by a reproduction ID
$ logs --since 2026-08-27 | grep fl-8c31f0a2

13:14:29.442Z POST /api/promo/apply  200 142ms
13:14:31.756Z GET  /api/cart         200  61ms
13:14:31.761Z WARN promo.apply: cart recalculated
              without discount   order=88213
In the tester's browser09:14:22.104navigate /checkout09:14:28.010type SAVE2009:14:29.442click button.promo-apply09:14:31.700navigate /summaryreproduction ID: fl-8c31f0a2In your server log13:14:29.442Z POST /api/promo/apply 200 142ms13:14:31.761Z WARN promo.apply: cart recalculated without discount
Illustrative connected session. Recorder sends x-fairlead-reproduction-id; your application must log it before you can search for it. Account-free sessions do not send correlation headers. Action-to-request associations remain timing-based leads.
In the tester's browserclick button.promo-applystep 4 · 09:14:29.4423 steps before, 1 afterreproduction ID: fl-8c31f0a2connected requests, including third-party originsIn your server log13:14:29.442Z POST /api/promo/apply 200 142ms13:14:31.761Z WARN promo.apply: cart recalculated without discount order=88213Match a recorded request to a logged identifier.
Illustrative connected session. Recorder sends x-fairlead-reproduction-id; your application must log it before you can search for it. Account-free sessions do not send correlation headers. Action-to-request associations remain timing-based leads.

The issue comes with a way into your logs.

Every request the tester recorded carried x-fairlead-reproduction-id down to your backends. Log it, and a developer finds where that QA session entered your system, in traces and logs, instead of guessing from a screenshot.

Your services need to log the headers; that is a one-time setup. When the tester picks the issue before recording, requests also carry its key, so the issue number finds them too.

Reproduction ID
One per session, on every recorded request. Search traces and logs for it to find the session's entry points. It is kept in the stored report.
Title and description
Written by the tester, or generated from the stored report and then edited before filing.
The Fairlead block
The tester's reproduction notes, in a fenced block of their own. If an existing description conflicts, review it in the tracker before choosing append or replacement.
Screenshots
The included images. Pixels are not automatically masked; inspect each image before submission.

What it files to today.

An admin connects the destination once, in Control Plane. Testers never enter tracker tokens.

Jira
A new issue or an existing one, with the tester's text and the screenshots they select. Filing an issue
GitHub
A new issue or an existing one, with the tester's text and the screenshots they select. Filing an issue
Azure DevOps
A new issue or an existing one, with the tester's text and the screenshots they select. Filing an issue
Test management
No direct connection yet. Attach the downloaded evidence to the case or run by hand. Attaching evidence to a TMS

You choose where reports are kept.

The Data Plane is the service that stores your project's reports and writes descriptions from them. Each project names one, and where it runs is your choice.

Run by Fairlead
The Fairlead cloud Data Plane. Reports are stored on Fairlead-operated servers.
Run by you
A Data Plane your organization runs and enrols, inside your own infrastructure. Fairlead's servers never hold the report.
Or not kept at all
A project can turn storage off. Nothing is sent to a Data Plane, and there is no generated description. Filing to the tracker still works.

On your own or with your team

It is the same extension. The difference is whether it signs in to a project. The Recorder on its own

Swipe the table

On your ownWith your team
AccountNoneA Fairlead account in your team's project
SettingsBuilt in. Recording stays on the site you start onSet by the project for every tester
RedactionBuilt-in rules, plus manual reviewProject rules, plus manual review
The report goes toA file you downloadYour project's Data Plane, unless storage is off
Filing an issueYou attach the file yourselfFrom the side panel, to Jira, GitHub or Azure DevOps
Written descriptionNot availableGenerated from the stored report
Session ID in your logsNo headers sentIdentifiers sent during recording; backend logging required

Who made it

We are backend developers. For years we were on the other end of the handoff, across dozens of apps and millions of lines of code: a screenshot, a sentence, and no way to find the request in the traces and logs. We built the capture side of the answer. The reproduction ID exists because it is the thing we always wanted and never got.

Fairlead is a product of Allyx, Inc. The report covers what we need as backend developers. If your team's bar is different, a QA step or a field the report should carry, tell us: Email

Free. Forever.

The extension and its team features cost nothing. No plan, no trial, no seat fee.

Join the waitlist