Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience our own tag's counts — open to see them
–Visits
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

BuildPulse review

Deep flake analytics and CI reporting for teams managing build-scale test quality.

8.1/10Editor score
BuildPulse8.1 Visit BuildPulse

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

BuildPulse is a cloud platform for engineering teams that analyzes CI and test data. Its core focus is test analytics at build scale: it identifies flaky tests across builds, branches, and commits, provides history and impact metrics, and supports quarantine workflows. Teams can also track repository-level pass rates, test volume, build duration, flakiness, historical quality trends, and code coverage by branch and file. It is aimed at organizations that need a deeper view of recurring test instability than a basic CI result dashboard provides.

Pricing is organized around four plans, with Startup available for $99 per month or $1,188 per year. Startup includes flaky-test detection and quarantine, code coverage tracking, per-repository CI and test metrics, and GitHub, Bitbucket, Jira, and Slack integrations. Team costs $249 per month or $2,988 per year and adds multiple organizations, REST API access, MCP server access, Slack alerts, and email support. Growth costs $499 per month or $5,988 per year and adds unlimited user seats, a dedicated onboarding session, and priority email support. Enterprise includes unlimited tests, API and MCP access, dedicated onboarding, priority support, and custom contract and invoicing terms. A 14-day free trial is available.

The integration footprint fits teams with varied CI environments: BuildPulse supports GitHub Actions, Bitbucket Pipelines, GitLab CI, Jenkins, Buildkite, CircleCI, Travis CI, and Semaphore. Results can be uploaded through JUnit XML or API, while notifications can go to Slack and email, and issues can be linked to Jira. That combination makes BuildPulse a strong fit for teams that need historical failure analysis, coverage tracking, and cross-build flake management alongside existing delivery tools. Teams seeking a free entry point or a simpler, narrowly focused test dashboard should look elsewhere; organizations prioritizing build-scale analytics should consider it.

BuildPulse pros and cons

  • Where it wins
    • Tracks flaky tests across builds, branches, and commits
    • Combines quarantine, history, impact metrics, and root-cause analysis
    • Connects with major CI providers plus Jira, Slack, and GitHub
  • Where it doesn't
    • No free plan; paid access starts at $99 per month
    • Advanced access is split across higher-priced tiers
    • Enterprise pricing uses a custom contract and invoicing terms

BuildPulse fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update