BuildPulse
buildpulse.io
- Free plan
- Windows
- macOS
- Linux
- Web
- API
What BuildPulse is
BuildPulse is a CI and test-health platform with tools for flaky-test detection and quarantine, code coverage, engineering metrics, CI runners, and AI code review. Its detector finds flaky tests across branches and pull requests, ranks them by engineering time, and lets teams quarantine them. Setup uses JUnit XML from an existing test runner and takes one workflow step, without test annotations or an SDK. Coverage accepts LCOV and Cobertura XML and shows trends by branch and file. Repository metrics include pass rate, test volume, build duration, flaky-test disruption, and recent builds, with 7-, 30-, and 90-day views. The platform lists integrations for GitHub, Bitbucket, Jira, and Slack, and its runners are described as replacements for hosted runners from GitHub Actions, Semaphore, and CircleCI. BuildPulse says it processes test results, coverage reports, and CI metadata rather than storing full source-code copies. Pricing starts at $99/mo, with a 14-day trial and no free plan.
Who it suits
BuildPulse suits engineering teams that want to monitor CI and test health, manage flaky tests, or track coverage across repositories. Teams needing DORA metrics or self-hosted deployment should note those limits.
Good to know, and what to watch
- Flaky-test detection needs one workflow step.
- Coverage trends are available by branch and file.
- Repository metrics include 7-, 30-, and 90-day views.
- Lists GitHub, Bitbucket, Jira, and Slack integrations.
- No free plan; paid plans start at $99/mo.
- Does not currently report DORA metrics.
- Self-hosted deployment is not available.
- Native DocumentDB storage encryption is still being evaluated.
Plans
Every plan and priceEnterprise
BuildPulse Runners
Runner 2x
Runner 4x
14-day trial
Getting started
- Open https://buildpulse.io/
- Start the 14-day trial or select a paid plan from $99/mo
- Connect GitHub or Bitbucket for source control
- Send JUnit XML from an existing test runner through one workflow step
- Connect Jira or Slack if needed
- Configure CI runners or use the listed CI integrations
Limits to check
The Startup plan includes 3,000,000 tests per month, one organization, and five user seats. Team raises this to 10,000,000 tests and 30 seats, while Growth includes 30,000,000 tests and unlimited seats; runners include 3,000 free minutes monthly before per-minute pricing.
The verdict
BuildPulse brings flaky-test management, coverage, and CI metrics together, with a short setup path for JUnit XML. Check the plan limits, DORA metrics gap, and security details against your requirements before choosing it.
Questions people ask
Does BuildPulse have a free plan?
No. Paid plans start at $99/mo and include a 14-day trial.
Which platforms does BuildPulse support?
BuildPulse is available through its API and web service. Self-hosted deployment is not available.
Which integrations are listed?
GitHub and Bitbucket are listed for source control, Jira for issue tracking, and Slack for notifications. CI/CD integrations include GitHub Actions, Bitbucket Pipelines, GitLab CI, Jenkins, Buildkite, CircleCI, Travis CI, and Semaphore.
What does the Startup plan include?
Startup costs $99 a month, billed yearly at $1,188, with 3,000,000 tests per month, one organization, and five user seats.
Does BuildPulse report DORA metrics?
The engineering metrics cover CI and test health, but BuildPulse does not currently report DORA metrics.
How does flaky-test detection connect?
It uses JUnit XML from an existing test runner through one workflow step, without test annotations or an SDK.
What the maker publishes
- AI code review
- The AI reviewer checks pull requests for correctness bugs, missing edge cases and obvious regressions and is offered in early access. source
- API authentication
- API calls use bearer tokens formatted as bp_ followed by 64 hexadecimal characters, and API access requires an eligible plan. source
- CI metrics
- Per-repository metrics include pass rate, test volume, build duration, flaky-test disruption, and recent builds, with 7-, 30-, and 90-day views. source
- CI providers
- BuildPulse Runners are described as drop-in replacements for GitHub Actions, Semaphore, and CircleCI hosted runners. source
- CI-provider support
- Native CI integrations cover GitHub Actions, Bitbucket Pipelines, CircleCI, Travis CI and Semaphore, while other providers can be connected with added configuration. source
- CI runners
- Its hosted runners are presented as drop-in replacements for GitHub Actions, Semaphore and CircleCI runners, with per-minute billing and no minimums. source
- Company
- BuildPulse describes itself as a small team of engineers that has shipped production CI tooling at scale. source
- Company acquisition news
- Founder Sid Dange wrote on LinkedIn that BuildPulse had become a profitable platform used by dozens of enterprises and had been acquired; the post does not name the acquirer. source
- Company legal name
- The privacy policy identifies the service operator as BuildPulse LLC. source
- Compliance
- BuildPulse says SOC 2 Type I attestation is in progress and Type II is planned; Enterprise pricing lists a DPA available on request. source
- Compliance status
- The pricing comparison lists SOC 2 Type I as in progress for Enterprise and a DPA available on request. source
- Coverage
- Coverage tracking supports LCOV and Cobertura XML and displays trends per branch and file. source
- Coverage tracking
- Coverage reporting provides branch and file trends and supports lcov and cobertura reports. source
- Data handling
- BuildPulse says it operates on test results, coverage reports, and CI metadata rather than storing full copies of source code. source
- Documentation depth
- The documentation includes runner quickstarts, remote Docker builders, caching, test-result upload, notifications, monorepos, framework guides and CI-provider guides. source
- Engineering metrics
- Engineering metrics include pass rate, build duration and flaky-test disruption by repository. source
- Flaky-test detection
- The product automatically identifies flaky tests from CI results without annotations or an SDK. source
- Flaky tests
- It detects flaky tests across branches and pull requests, ranks them by engineering time, and lets users quarantine tests. source
- Independent GitHub presence
- GitHub verifies the BuildPulse organization controls buildpulse.io and lists public repositories for the test reporter, GitHub Action and CircleCI orb. source
- Installer support
- The public test-reporter binary is distributed for 64-bit Linux, macOS and Windows, including Linux amd64 and arm64 and macOS amd64 and arm64. source
- Integrations
- BuildPulse lists GitHub and Bitbucket for source control, Jira for issue tracking, and Slack for notifications. source
- Integrations
- Official integrations include GitHub and Bitbucket source control, Jira issue tracking and Slack notifications. source
- Limit: cancellation workflow
- A verified G2 reviewer complained that cancellation could not be completed in the UI and reported unanswered follow-ups after an attempted upsell. source
- MCP integrations
- The MCP server exposes flaky-test history, CI runs and coverage to Claude Desktop, Cursor, ChatGPT, Windsurf, VS Code Copilot and Zed. source
Checked against the maker's pages on 15 Oct 2026.