Question 1

What permissions does the Kleore GitHub App need?

Accepted Answer

Kleore starts with the bare minimum: read-only access to Actions workflow runs. It never sees your source code. When you enable optional features like PR comments, it asks for just the additional permission needed — you approve each one.

Question 2

Do I need to change my CI workflows?

Accepted Answer

Not for the initial report. The zero-config scan works from your existing GitHub Actions data. To see individual flaky tests, you add one step to upload JUnit XML results — a 2-line YAML change.

Question 3

How is the CI cost number calculated?

Accepted Answer

Each flaky rerun costs approximately 30 minutes (20 min rerun wait + 10 min context switch) at $75/hr fully-loaded engineer rate. These are conservative defaults you can customize for your team.

Question 4

Can I use Kleore on a private GitHub repo?

Accepted Answer

Yes. The free tier works on any repo you install the app on, public or private. Your data stays private and is never shared.

Question 5

What makes Kleore different from other CI tools?

Accepted Answer

Most CI tools show you pass/fail. Kleore shows you cost. It translates flaky tests into dollar amounts so you can prioritize fixes and get budget approval. The shareable report makes the problem impossible to ignore.

Blog

Flaky Test Cost Calculator

Kleore vs BuildPulse vs Trunk vs Datadog

How Much Do Flaky Tests Actually Cost?

How to Fix Flaky Tests in GitHub Actions

What Are Flaky Tests? The Silent Killer of CI Pipelines

Stop guessing.
Start measuring.