Triage

400 raw playtest reports.
12 issues a developer can fix.

Repro sits between your testers and your issue tracker. It clusters duplicate reports as they arrive, watermarks every build it serves, and pays testers once per bug rather than once per message.

What it does

Six things, done plainly

No model calls, no vector database, no dashboard of charts nobody reads.

Four signals, one decision

Wording, position in the scene, console signature and hardware are scored separately. When they disagree, the report waits for a human.

Duplicates collapse on arrival

A report joins an existing issue as it lands. Nobody triages a backlog of the same bug written twenty ways.

Every frame carries its source

A build session embeds the tester's identifier in pixel luminance. A leaked lossless frame names who it came from.

Noise is caught, not counted

Questions, chat and empty submissions are scored as noise and kept out of the occurrence counts rewards are paid against.

One bug, one payout

Rewards attach to a verified issue, not to a submission. Ten testers finding the same crash split one verification.

Runs with the Wi-Fi off

Clustering, watermarking and scoring are all local. There is no model to call and nothing to wait for.

Triage

The collapse is the product

In the seeded campaign, 400 reports resolve to 12 issues. Every one of those merges is a duplicate a developer never has to read twice.

400
reports in
12
issues out
0
scored as noise
Security

Three layers, and what each one cannot do

Every claim below is followed by its limit, in the same size text. A security page that only lists strengths is telling you half of something.

Access tokens are signed with HMAC-SHA256, expire after 15 minutes, and bind to the tester's browser.

A tester who shares their screen while playing has shared the build. Binding proves who held the link, not who watched it.

Exported frames carry an invisible watermark in pixel luminance that survives 2× and 3× downscaling.

It does not survive lossy JPEG, heavy filters, or a phone photographing a monitor. When the mark is gone this is said plainly rather than guessed.

The NDA is recorded against a legal name and a timestamp before a build is ever served.

It is a record of agreement, not a technical control. It establishes accountability; it does not stop a capture card.

Rewards

Ten testers, one crash, one payout

Rewards attach to a verified issue rather than to a submission. Finding a bug someone already found is still worth something — but it is not worth ten times the bug.

Tester 04
First to report the lift crash
+120
Tester 11
Same crash, confirmed duplicate
+15
Tester 32
Same crash, confirmed duplicate
+15
Issue verified
One payout, split by contribution
150 total

Coins are redeemed for rewards the studio provides. They are not money and Repro does not exchange them for any.

Point your next playtest at it

The seeded campaign is loaded and the board is live. Nothing here needs an account you do not already have.