BuildPulse vs QAI
BuildPulse
buildpulse.ioQAI
useqai.devSide by side
| Figure | BuildPulse | QAI |
|---|---|---|
| Price from | $29/mo | $29/mo |
| Free plan | 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 Analytics Software | 9.3 (#2) | 7.6 (#19) |
| Coverage | Coverage tracking supports LCOV and Cobertura XML and displays trends per branch and file. | QAI maps pages, API calls, and paths from Playwright traces and describes its behavioral coverage feature as Playwright only. |
| Integrations | Official integrations include GitHub and Bitbucket source control, Jira issue tracking and Slack notifications. | The site describes GitHub Actions, the GitHub App, Slack alerts, email, and webhooks as integrations or actions. |
| Product | BuildPulse offers CI runners, flaky-test detection and quarantine, code coverage, engineering metrics, and AI code review. | QAI analyzes CI test failures and posts root cause, history, fix suggestions, and merge recommendations on pull requests. |
| 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 QAI needs one workflow step and can return a first result in 60 seconds. |
| Support | Team includes email support, Growth includes priority email support and a dedicated onboarding session, and Enterprise includes dedicated onboarding and priority support. | The Team plan includes priority support, and the pricing page directs questions to the listed support email. |
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.