BuildPulse

BuildPulse is a CI and test-health platform for teams tracking flaky tests, coverage, build activity, and engineering metrics. Its flaky-test tools find issues across branches and pull requests, rank them by engineering time affected, and allow teams to quarantine tests. Detection can use JUnit XML from an existing test runner through 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, with 7-, 30-, and 90-day views. The service also offers CI runners described as replacements for hosted GitHub Actions, Semaphore, and CircleCI runners, along with AI code review. Listed connections include GitHub and Bitbucket, Jira, and Slack. BuildPulse says it processes test results, coverage reports, and CI metadata rather than storing complete source-code copies. It does not currently report DORA metrics. Pricing starts at $99/mo, with a 14-day trial and no free plan.

BuildPulse brings flaky-test detection, coverage, CI metrics, runners, and AI code review into one service. Its stated focus is CI and test health, not DORA reporting.

BuildPulse suits engineering teams that want to monitor test health and CI activity across repositories. It may also fit teams seeking flaky-test quarantine, coverage trends, or CI runners.

BuildPulse suits engineering teams that want to track flaky tests and CI health across repositories while keeping their existing test runners. Its low-friction test reporting is a practical strength, but its metrics stop short of DORA reporting.

Overview

BuildPulse brings flaky-test detection and quarantine, coverage trends, repository metrics, CI runners and AI code review together. Flaky-test detection uses JUnit XML from an existing runner and takes one workflow step, with no test annotations or SDK. That makes it a good fit for teams seeking more visibility without rewriting their test setup.

The service operates on test results, coverage reports and CI metadata rather than storing full copies of source code. It runs on AWS in the United States and encrypts data in transit. BuildPulse describes at-rest encryption for object storage and DynamoDB, while native DocumentDB storage encryption is still under evaluation. SOC 2 Type I attestation is in progress; Type II is planned.

Key features

Flaky-test detection and quarantine

BuildPulse follows flaky tests across branches and pull requests, ranks them by engineering time, and lets teams quarantine them. Ranking by disruption helps teams prioritize the failures that consume the most time, while quarantine offers a way to manage them. The product names frameworks including Jest, Vitest, RSpec, pytest, Playwright, Go test, JUnit and xUnit.

Coverage and CI metrics

Coverage trends are available by branch and file, using LCOV or Cobertura XML. Repository dashboards track pass rate, test volume, build duration, flaky-test disruption and recent builds across 7-, 30- and 90-day views. These measures give teams a focused view of CI and test health; they do not provide DORA metrics.

Runners and integrations

BuildPulse Runners are positioned as drop-in replacements for hosted runners from GitHub Actions, Semaphore and CircleCI. The integration ecosystem includes GitHub and Bitbucket for source control, Jira for issue tracking and Slack for notifications. BuildPulse also names GitLab CI, Jenkins, Buildkite, Travis CI and other CI/CD systems among its integrations.

AI code review

AI Code Review is an invite-only beta at $29 per seat per month, with 50 reviews per seat monthly and an additional $0.75 per review. The per-seat allowance sets a clear starting limit, though teams with heavier review volume should account for the extra charge.

Pricing

BuildPulse has no general free plan. The paid Startup plan begins at $99 per month, matching the stated starting price, and the listed plans are billed yearly.

• BuildPulse Runners: free, with 3,000 free minutes every month, then per-minute pricing. Linux x64 and Linux arm64 are supported, with 2–64 vCPU sizes and no minimums. This can suit teams evaluating or adopting the runners; usage beyond the monthly allowance is billed per minute.
• AI Code Review: $29 a month, billed at $29 per seat per month, with 50 reviews per seat monthly and $0.75 per additional review. It is invite-only beta, so access is limited.
• Startup: $99 a month, billed $1,188 yearly, with 3,000,000 tests per month, one organization and five user seats. It fits a small team that can stay within those caps.
• Team: $249 a month, billed $2,988 yearly, with 10,000,000 tests per month, multiple organizations and 30 seats. It adds room for larger teams and more than one organization.
• Growth: $499 a month, billed $5,988 yearly, with 30,000,000 tests per month, multiple organizations and unlimited seats. Priority email support and a dedicated onboarding session make this the more supported option for growing teams.
• Enterprise: custom pricing and contract and invoicing terms, with unlimited tests, custom organizations, unlimited seats, dedicated onboarding and priority support. A DPA is available on request.

Team includes email support. Startup, Team and Growth have monthly test quotas and seat limits, while Enterprise removes the test and seat caps. The 14-day trial provides a way to evaluate the paid service; there is no free general-use tier.

Platforms

BuildPulse supports web and API access. Its self-hosted deployment option is unavailable, which rules it out for teams that require deployment within their own environment.

Who it's for

BuildPulse is best suited to engineering teams that want to find and prioritize flaky tests, monitor coverage and CI trends, and keep the reporting workflow close to existing runners. Startup is the natural fit for a small organization within five seats and three million tests monthly; Team and Growth accommodate multiple organizations, with Growth removing the seat cap. Teams that need DORA metrics, self-hosting, or a general free plan should look elsewhere.

Pros and cons

• Pro: Flaky-test detection needs only JUnit XML and one workflow step, avoiding annotations and an SDK.
• Pro: Branch and file coverage trends pair with repository metrics and multiple time windows for a useful CI health view.
• Pro: Runner pricing includes 3,000 free minutes each month and supports Linux x64 and arm64 workloads.
• Con: Startup is capped at five seats and three million tests monthly, which may require an upgrade as usage grows.
• Con: There is no general free plan, and runner minutes beyond the allowance incur per-minute charges.
• Con: BuildPulse does not report DORA metrics and cannot be self-hosted.
• Con: SOC 2 Type I is still in progress, and native DocumentDB at-rest encryption remains under evaluation.

Alternatives

Choose Bitbucket Pipelines if a free forever plan, up to five users and unlimited public and private repositories better match your needs; its free tier includes 50 build minutes per month.

HyperExecute is worth considering if you want a free testing tier with 300 minutes and up to two concurrent sessions on Windows or Linux VMs.

TeamCity may suit teams seeking a free forever on-premises option with unlimited users, three build agents and 100 build configurations.

Testery offers a free Growth tier with 10 test execution hours, 10 parallel runners, reporting and analytics, then charges $1.20 per hour.

Buildkite is an alternative for teams that want a free tier with up to five users, 10 concurrent jobs and 2,000 Linux vCPU minutes monthly.

Captain is another option for teams looking at flaky-test management.

CircleCI may be a better fit if you want a freemium CI platform; its Performance plan starts at $15 per month and includes 30,000 credits and five active users.

Cypress offers a free Starter tier with 10 users and 500 test results per month, which may suit teams whose needs fit within those limits.

Compare other options in Test Flakiness Management Software and Test Analytics Software.

Verdict

Choose BuildPulse if your team needs practical flaky-test controls and focused CI health reporting with minimal changes to an existing test workflow. Its JUnit XML setup, coverage trends and repository metrics make that case clearly. Look elsewhere if DORA reporting, self-hosting or a general free plan is essential.