
BuildPulse
7.9#3 in ci failure analysis and flaky test toolsFree planFree planWebAPILinuxmacOS
Visit

| Fact | BuildPulse | ReportPortal |
|---|---|---|
| API authentication | API calls use bearer tokens formatted as bp_ followed by 64 hexadecimal characters, and API access requires an eligible plan. | Agents use API keys while the user interface uses JWT tokens, with bearer authentication documented for API requests. |
| Documentation depth | The documentation includes runner quickstarts, remote Docker builders, caching, test-result upload, notifications, monorepos, framework guides and CI-provider guides. | Documentation includes installation, configuration, developer guides, REST API material, plugins, troubleshooting, dashboards, quality gates and release notes. |
| Integrations | Official integrations include GitHub and Bitbucket source control, Jira issue tracking and Slack notifications. | Documented integrations include Jira Server and Cloud, Azure DevOps, Rally, GitLab, Monday, Sauce Labs, Slack, Telegram, LDAP, Active Directory, SAML, JUnit and Robot Framework. |
| Rating on G2 | 3.0 out of 5 from 2 reviews | 4.3 out of 5 from 4 reviews. |
| Rating on GetApp | 0.0 out of 5 from 0 reviews | 0 out of 5 from 0 reviews. |
| Security | BuildPulse says it runs on AWS in the United States and encrypts data in transit; its page describes encryption at rest for object storage and DynamoDB while saying native DocumentDB storage encryption is still being evaluated. | The pricing page displays SOC 2, ISAE 3402, ISO 9001, and ISO 27001 certification badges. |
| Security controls | The security page states that data in transit uses TLS, stored data uses industry-standard encryption such as AES-256, and administrative access requires least privilege, MFA and logging. | The security article describes TLS, encryption at rest, SAML/LDAP/Active Directory SSO, role-based access, scoped tokens, retention rules and audit logs. |
BuildPulse suits engineering teams tracking flaky tests, coverage, and CI activity across repositories. It may be useful to teams that want to quarantine disruptive tests without adding an SDK or test annotations.
ReportPortal suits software teams that want a shared view of automated test results, failure triage and release decisions. It offers a self-hosted community edition as well as SaaS plans.