Freedom251 › CI Failure Analysis And Flaky Test Tools
BuildPulse
What BuildPulse is
BuildPulse is a CI and test-health platform offering flaky-test detection and quarantine, code coverage, engineering metrics, CI runners, and AI code review. It finds flaky tests across branches and pull requests, ranks them by engineering time, 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 over 7-, 30-, and 90-day periods. BuildPulse lists GitHub and Bitbucket for source control, Jira for issues, and Slack for notifications; its runners are described as replacements for hosted runners from GitHub Actions, Semaphore, and CircleCI. It says it processes test results, coverage reports, and CI metadata rather than full source-code copies. The page says it does not currently report DORA metrics. Startup costs $99 a month, and there is no free plan; a 14-day trial is listed.
Who it suits
It suits engineering teams seeking visibility into flaky tests, coverage, and CI activity, including teams using the named source-control and issue-tracking integrations.
What it does well
- Detects and ranks flaky tests across branches and pull requests.
- One workflow step connects existing runners via JUnit XML.
- Coverage trends appear by branch and file.
- Repository metrics include 7-, 30-, and 90-day views.
- Processes CI metadata rather than full source-code copies.
What to know first
- No free plan is listed.
- Startup costs $99 a month.
- DORA metrics are not currently reported.
- Self-hosted deployment is not available.
Limits
The Startup plan costs $99 a month and includes 3,000,000 tests monthly, one organization, and five user seats. BuildPulse Runners include 3,000 free minutes monthly, then use per-minute pricing. AI Code Review is an invite-only beta with 50 reviews per seat monthly; additional reviews cost $0.75 each.
Plans
| Plan | Billed and limits | Price |
|---|---|---|
| BuildPulse Runners | 3,000 free minutes every month, then per-minute pricing · Linux x64 and Linux arm64 · 2–64 vCPU sizes · no minimums | Free |
| Runner 2x | usage-based per minute · 2 vCPU · 8 GB RAM | Free |
| Runner 4x | usage-based per minute · 4 vCPU · 16 GB RAM | $0.01, paid once |
| Runner 8x | usage-based per minute · 8 vCPU · 32 GB RAM | $0.02, paid once |
| Runner 16x | usage-based per minute · 16 vCPU · 64 GB RAM | $0.03, paid once |
| Runner 32x | usage-based per minute · 32 vCPU · 128 GB RAM | $0.06, paid once |
| Runner 64x | usage-based per minute · 64 vCPU · 256 GB RAM | $0.13, paid once |
| Team | $2,988 billed yearly · 10,000,000 tests/month · multiple organizations · 30 user seats · REST API · MCP server · Slack alerts · email support | $249 a month |
The first 8 of 12 plans, as buildpulse.io lists them, read 7 Oct 2026. The maker's own page has the final word. Every plan
Getting started
- Open the BuildPulse website.
- Choose a plan; a 14-day trial is available.
- Connect an existing test runner by sending JUnit XML in one workflow step.
- Use the web or API platform to access BuildPulse.
- For flaky-test detection, review results across branches and pull requests; for coverage, provide LCOV or Cobertura XML.
Verdict
BuildPulse focuses on test reliability and CI health, with coverage tracking and runner options alongside flaky-test analysis. Teams should note its listed starting price and that its engineering metrics do not include DORA reporting.
Questions
How much does BuildPulse cost?
The Startup plan is $99 a month, billed yearly at $1,188. Team is $249 a month, Growth is $499 a month, and Enterprise uses custom contract and invoicing terms. BuildPulse Runners include 3,000 free minutes each month, then charge per minute; AI Code Review is $29 per seat per month, with $0.75 per additional review.
Is there a free plan or trial?
There is no general free plan, but BuildPulse offers a 14-day trial. BuildPulse Runners separately include 3,000 free minutes each month.
Which platforms does BuildPulse support?
The listed platforms are web and API.
Which testing frameworks are supported?
Examples include Jest, Vitest, RSpec, pytest, Playwright, Go test, JUnit, and xUnit. The supported-framework list also names Elixir, TestNG, Cypress, Jasmine, Karma, Mocha, TestCafe, Nightwatch, PHPUnit, Minitest, and ScalaTest.
Does BuildPulse integrate with source control and team tools?
It lists GitHub and Bitbucket for source control, Jira for issue tracking, and Slack for notifications. Its CI/CD integration list includes GitHub Actions, Bitbucket Pipelines, GitLab CI, Jenkins, Buildkite, CircleCI, Travis CI, and Semaphore.
What do the paid plans include?
Startup includes 3,000,000 tests per month, one organization, and five seats. Team includes 10,000,000 tests, multiple organizations, and 30 seats; Growth includes 30,000,000 tests, multiple organizations, and unlimited seats. Enterprise includes unlimited tests, custom organizations, unlimited seats, and dedicated support.
Facts from BuildPulse's own pages
- AI code review
- The AI reviewer checks pull requests for correctness bugs, missing edge cases and obvious regressions and is offered in early access. · buildpulse.io, 15 Oct 2026
- API authentication
- API calls use bearer tokens formatted as bp_ followed by 64 hexadecimal characters, and API access requires an eligible plan. · platform.buildpulse.io, 15 Oct 2026
- 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. · buildpulse.io, 7 Oct 2026
- CI providers
- BuildPulse Runners are described as drop-in replacements for GitHub Actions, Semaphore, and CircleCI hosted runners. · buildpulse.io, 7 Oct 2026
- 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. · docs.buildpulse.io, 15 Oct 2026
- 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. · buildpulse.io, 15 Oct 2026
- Company
- BuildPulse describes itself as a small team of engineers that has shipped production CI tooling at scale. · buildpulse.io, 7 Oct 2026
- 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. · linkedin.com, 15 Oct 2026
- Company legal name
- The privacy policy identifies the service operator as BuildPulse LLC. · buildpulse.io, 15 Oct 2026
- Compliance
- BuildPulse says SOC 2 Type I attestation is in progress and Type II is planned; Enterprise pricing lists a DPA available on request. · buildpulse.io, 7 Oct 2026
- Compliance status
- The pricing comparison lists SOC 2 Type I as in progress for Enterprise and a DPA available on request. · buildpulse.io, 15 Oct 2026
- Coverage
- Coverage tracking supports LCOV and Cobertura XML and displays trends per branch and file. · buildpulse.io, 7 Oct 2026
- Coverage tracking
- Coverage reporting provides branch and file trends and supports lcov and cobertura reports. · buildpulse.io, 15 Oct 2026
- Data handling
- BuildPulse says it operates on test results, coverage reports, and CI metadata rather than storing full copies of source code. · buildpulse.io, 7 Oct 2026
- Documentation depth
- The documentation includes runner quickstarts, remote Docker builders, caching, test-result upload, notifications, monorepos, framework guides and CI-provider guides. · docs.buildpulse.io, 15 Oct 2026
- Engineering metrics
- Engineering metrics include pass rate, build duration and flaky-test disruption by repository. · buildpulse.io, 15 Oct 2026
- Flaky-test detection
- The product automatically identifies flaky tests from CI results without annotations or an SDK. · buildpulse.io, 15 Oct 2026
- Flaky tests
- It detects flaky tests across branches and pull requests, ranks them by engineering time, and lets users quarantine tests. · buildpulse.io, 7 Oct 2026
- Independent GitHub presence
- GitHub verifies the BuildPulse organization controls buildpulse.io and lists public repositories for the test reporter, GitHub Action and CircleCI orb. · github.com, 15 Oct 2026
- 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. · github.com, 15 Oct 2026
- Integrations
- Official integrations include GitHub and Bitbucket source control, Jira issue tracking and Slack notifications. · buildpulse.io, 15 Oct 2026
- 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. · g2.com, 15 Oct 2026
- MCP integrations
- The MCP server exposes flaky-test history, CI runs and coverage to Claude Desktop, Cursor, ChatGPT, Windsurf, VS Code Copilot and Zed. · buildpulse.io, 15 Oct 2026
- Notable limits
- Engineering metrics cover CI and test health; the page says BuildPulse does not currently report DORA metrics. · buildpulse.io, 7 Oct 2026