The repro is in the box

Most frontend bugs arrive as a screenshot, a stack trace, and a sentence that starts with “it just.” The person who saw it has already moved on. The person who has to fix it was not in the room.

Reprobox is built for that gap. It is a frontend incident recorder. You drop in an SDK. When something breaks, the last stretch of the session is already in the box: the repro, not a reconstruction.

The job is not to describe the bug. The job is to hand someone the moment it happened.

What it is

Reprobox records the recent life of a frontend session so an engineer can play it back. The window we talk about in the product is the last ~60 seconds. That is enough to see what the user did, what the app did, and where it fell over. It is not a year of telemetry and it is not a promise to watch every click forever.

It is SDK-first. The recorder lives with the app. There is no “install our browser extension and hope the customer has it.”

What it is not

It is not a sandbox. It is not an error tracker with a session replay bolted on as a feature row. It is not an AI product that summarises the mystery so you never have to look.

If you need a place to file exceptions, keep the tool you already have. Reprobox is for the slice of the incident that those tools still make you reconstruct by hand.

Why it sits in this house

Braid’s rule is one job per product. Reprobox’s job is the repro. That is why it has its own site, its own name, and its own customers. The house page will not pretend it is a platform module.

When you want the product, go to reprobox.app. Privacy and terms for Reprobox live with Reprobox, not in a footer on the house.

The test

A good Reprobox session is one you can hand to someone who was not there and watch them stop asking “can you send a recording?” The repro is in the box. That is the whole pitch.