Find the commit that made your test flaky.
Culprit watches your CI, tells genuine flakes from real failures, and bisects your history to the commit that introduced the flake.
Free during the alpha · read-only CI access
Illustrative product facts, not adoption claims.
Everyone knows the test is flaky. Nobody knows when it broke.
So it gets skipped, and stays skipped, forever.
Watch runs, tell flakes from failures, blame the PR.
Connect CI
Point Culprit at your GitHub Actions runs. It reads results you already produce.
Detect
It scores tests by pass/fail instability and surfaces the genuine flakes, not the real breaks.
Blame
It bisects the suspect range to one commit and posts a linkable report on the PR.
A linkable blame report, right on the PR.
Which test, which commit, which author, how often it fails.
Flaky test introduced in this pull request.
Wedge on GitHub Actions now.
Buildkite, CircleCI, and GitLab CI are on the roadmap.
Free while we prove it works.
A planned $15–25 per committer per month when it does.
Free while we prove Culprit can attribute a fixed test to its bisect output.
- Flake vs. real-failure detection
- Automatic commit bisect
- Linkable PR blame report
- No card required
Planned $15–25 / committer / month at launch
Questions an engineer asks before trusting an auto-bisect tool.
How do you tell a flake from a real failure?
A test that fails, then passes on a plain re-run with no code change, is treated as a flake. A test that fails consistently is a real failure, and Culprit leaves it alone.
Does it slow down my CI?
Which CI systems do you support?
What access do you need?
Stop re-running. Start fixing.
Join the alpha and get the commit, not just the flake.
Read-only CI access · GitHub Actions