Lost edits, double submits, old data on screen. We find them in your app for US$500, or your money back.

We use your app like an impatient user on a slow connection and report every bug we can reproduce, each with the steps, a recording and a fix.

What we look for

Three things your users see, and one cause.

All three happen when answers arrive in an order the code did not expect. We change the order on purpose.

Old data on screen

How it happensA slow answer to an earlier request replaces a newer one.

How often we found it35 of the 92 bugs we confirmed in open-source apps.

An edit that is lost

How it happensTwo saves cross, and the older one is written last.

How often we found it13 of the 92.

Sent twice

How it happensA second click goes out before the first answer is back, and both are accepted.

How often we found it10 of the 92.

Other bugs on the way

How it happensThe same cause in another shape, and ordinary bugs we noticed.

How often we found it18 with the same cause, 14 ordinary, 2 neither.

What you get

For every bug we reproduce, six things.

The steps

What it isWhat to click, in order.

What it is forYou can check it by hand.

The order

What it isWhich response arrived before which, and the seed that replays it.

What it is forIt reproduces every time.

A recording

What it isThe page going wrong, on video.

What it is forYour team sees what a user would see.

The cause

What it isThe lines in your code where the order goes wrong.

What it is forThe fix is a small change, not a search.

A fix

What it isA pull request, or a patch if you prefer.

What it is forYou review it like any other change.

A regression test

What it isA Playwright test that fails before the fix and passes after it.

What it is forThe bug stays fixed.

How it goes

Five working days, and a person checks every finding.

You pay and point us at the app

What happensOne payment by card. No subscription, no account.

What we need from youA staging address with a test login, or a repository that starts with one command.

We hunt

What happensAn AI agent uses your app in Chromium while GenClass delivers responses late and in other orders.

What we need from youNothing. Test data only, never production.

A person confirms

What happensSomeone on our side reproduces each finding by hand. The rest is left out.

What we need from youNothing.

You get the report

What happensWithin five working days of the day we can sign in to the app. Nothing reproduced: a full refund, and what we tried.

What we need from youAn address for the report, and a reviewer for the pull requests.

What we have found so far

46 open-source apps hunted. 45 had a bug we could reproduce.

Maintainers have fixed 16 of the 45 reports, among them Gitea, React Admin, Keystone, LibreChat, Langflow, AnythingLLM, Memos, Notesnook and Umami.

Not every bug was GenClass's

The numberOf the 92 bugs we confirmed, GenClass flagged 45.

What it means for youYou are buying the hunt and its result, not a claim about one tool.

The explorer has false alarms

The numberIt flagged a correct page in 197 of 745 reordered runs.

What it means for youA person confirms every finding before you see it.

We ask first now

The numberThose 45 reports were sent without asking, and some maintainers objected (issue 173).

What it means for youA hunt happens only when you ask, and the report goes only to you.

Questions

Before you buy

What kind of app can you hunt?

A web app that talks to an API: React, Next.js, Vue, Nuxt, Svelte, Angular or plain JavaScript. We need to reach it, or start it from its repository with one command.

Do you see our users' data?

No. We work on a staging or development copy with test data. We will not ask for production.

What counts as "nothing reproducible"?

A finding counts when the same steps and the same order of responses make the page end up wrong every time, and a person on our side has seen it. With no such finding you get the full payment back. An ordinary bug we notice is in the report but does not count as a finding.

Is this a subscription?

No. One payment for one hunt on one app.

Our app cannot leave our network. Now what?

Write to mehar@genclass.dev. The hunt can run inside your network on terms we agree.

Who is behind this?

Daybot Solutions Inc., in Canada. Your card statement will say DAYBOT.CA. The terms and the privacy policy cover a hunt.