BuildPulse vs FlakyWatch
BuildPulse
buildpulse.ioFlakyWatch
flakywatch.devSide by side
| Figure | BuildPulse | FlakyWatch |
|---|---|---|
| Price from | $29/mo | $29/mo |
| Free plan | Yes | Yes |
| Free trial | Yes | Yes |
| Open source | — | — |
| Web | Yes | Yes |
| Windows | Yes | — |
| macOS | Yes | — |
| Linux | Yes | — |
| API | Yes | — |
| Plans published | 12 | 3 |
| Spec score · Test Flakiness Management Software | 9.4 (#2) | 7.8 (#15) |
| Integrations | Official integrations include GitHub and Bitbucket source control, Jira issue tracking and Slack notifications. | The site lists GitHub Actions and GitHub issues; Slack integration is marked coming soon on the Team plan. |
| Security | BuildPulse says it runs on AWS in the United States and encrypts data in transit; its page describes encryption at rest for object storage and DynamoDB while saying native DocumentDB storage encryption is still being evaluated. | The privacy policy states that data is encrypted in transit and at rest, production systems have access controls, and the service uses least-privilege access and regular security audits. |
| Setup | Flaky-test detection uses JUnit XML from an existing test runner and requires one workflow step, without test annotations or an SDK. | The site says setup uses the FlakyWatch GitHub App and a workflow step to upload JUnit XML artifacts, with no agents or config files required. |
| Support | Team includes email support, Growth includes priority email support and a dedicated onboarding session, and Enterprise includes dedicated onboarding and priority support. | FlakyWatch lists email support on Starter, priority support on Team, and says it aims to respond to inquiries within 48 hours during business days. |
| What it does | BuildPulse connects to CI systems to analyze test reliability, pipeline performance, coverage and CI cost. | FlakyWatch monitors GitHub Actions test results, detects and classifies flaky tests, estimates CI and developer time costs, and tracks them as GitHub issues. |
Plans
BuildPulse
- BuildPulse RunnersFree
- Runner 2xFree
- Runner 4x$0.01, paid once
- Runner 8x$0.02, paid once
- Runner 16x$0.03, paid once
- Runner 32x$0.06, paid once
- Runner 64x$0.13, paid once
- AI Code Review$29 a month
- Startup$99 a month
- Team$249 a month
In their own words
BuildPulse
BuildPulse is a CI and test-health platform for tracking flaky tests, coverage, build activity, and engineering metrics. It detects flaky tests across branches and pull requests, ranks them by engineering time affected, and lets teams quarantine them. Detection can use JUnit XML from an existing test runner with one workflow step, without annotations or an SDK. Coverage tracking accepts LCOV and Cobertura XML and shows trends by branch and file. Repository views include pass rate, test volume, build duration, flaky-test disruption, and recent builds across 7-, 30-, and 90-day periods. BuildPulse also offers CI runners described as replacements for hosted runners from GitHub Actions, Semaphore, and CircleCI, along with AI code review. Connections include GitHub, Bitbucket, Jira, and Slack. BuildPulse says it processes test results, coverage reports, and CI metadata rather than keeping full source-code copies. Pricing starts at $99 a month for Startup; there is no free plan, though a 14-day trial is listed.
FlakyWatch
FlakyWatch monitors GitHub Actions test results, classifies unstable tests, estimates CI and developer time costs, and tracks flakes as GitHub issues. Users upload JUnit XML through the FlakyWatch GitHub App and a workflow step; the service says agents and configuration files are unnecessary. Supported runners include pytest, Jest, JUnit, RSpec, and other JUnit-compatible tools. Tests receive stable, flaky, broken, or newly unstable labels with confidence scores. Generated GitHub issues include classification, impact, and recommended next steps, and can reopen when a flake returns. Dashboard metrics include blocked runs, main failures, affected branches, and cost per test. An optional weekly email digest reports new unstable tests, cost trends, and open issues. The free plan costs nothing and covers one repository with 14-day history. Starter costs $29 a month for five repositories and 30-day history; Team costs $79 a month for 20 repositories and 90-day history. Slack and CSV export are marked coming soon on Team.