BuildPulse vs Oobeya
BuildPulse
buildpulse.io
Oobeya
oobeya.ioSide by side
| Figure | BuildPulse | Oobeya |
|---|---|---|
| Price from | $29/mo | — |
| Free plan | Yes | — |
| Free trial | Yes | — |
| Open source | — | — |
| Web | Yes | Yes |
| Windows | Yes | — |
| macOS | Yes | — |
| Linux | Yes | — |
| API | Yes | Yes |
| Self-hosted | — | Yes |
| Plans published | 12 | 3 |
| Spec score · Test Analytics Software | 9.3 (#2) | 7.4 (#21) |
| Company | BuildPulse describes itself as a small team of engineers that has shipped production CI tooling at scale. | Oobeya identifies its headquarters as Marietta, Georgia, USA, and lists its founding year as 2022. |
| Compliance | BuildPulse says SOC 2 Type I attestation is in progress and Type II is planned; Enterprise pricing lists a DPA available on request. | Oobeya states that SOC 2 Type I certification is complete, its SOC 2 Type II audit is in progress, and its operating model is GDPR-conscious. |
| Data handling | BuildPulse says it operates on test results, coverage reports, and CI metadata rather than storing full copies of source code. | The Trust Center states that Oobeya does not store customer source code and offers data residency, retention, deletion, and team- and user-level privacy controls. |
| Integrations | Official integrations include GitHub and Bitbucket source control, Jira issue tracking and Slack notifications. | Oobeya lists 40+ integrations across seven categories, including project management, SCM and CI/CD, AI coding, quality and security, testing, monitoring, and identity. |
| 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 Trust Center lists SSO, RBAC, audit logging, least-privilege access, 24/7 infrastructure monitoring, and daily backups with point-in-time recovery. |
| Support | Team includes email support, Growth includes priority email support and a dedicated onboarding session, and Enterprise includes dedicated onboarding and priority support. | Oobeya offers self-service documentation and email support, while its pricing page lists onboarding, training, Customer Success, and enterprise support and SLA options for paid packages. |
| What it does | BuildPulse connects to CI systems to analyze test reliability, pipeline performance, coverage and CI cost. | Oobeya connects software delivery signals so organizations can analyze delivery performance, quality, productivity patterns, bottlenecks, and AI adoption impact. |
Plans
BuildPulse
- BuildPulse RunnersFree
- Runner 2xFree
- Runner 4x$0.01, paid once
- Runner 8x$0.02, paid once
- Runner 16x$0.03, paid once
- Runner 32x$0.06, paid once
- Runner 64x$0.13, paid once
- AI Code Review$29 a month
- Startup$99 a month
- Team$249 a month
Oobeya
- EnterprisePriced on request
- Enterprise AIPriced on request
- StarterPriced on request
In their own words
BuildPulse
BuildPulse is a CI and test-health platform for tracking flaky tests, coverage, build activity, and engineering metrics. It detects flaky tests across branches and pull requests, ranks them by engineering time affected, 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 across 7-, 30-, and 90-day periods. BuildPulse also offers CI runners described as replacements for hosted runners from GitHub Actions, Semaphore, and CircleCI, along with AI code review. Connections include GitHub, Bitbucket, Jira, and Slack. BuildPulse says it processes test results, coverage reports, and CI metadata rather than keeping full source-code copies. Pricing starts at $99 a month for Startup; there is no free plan, though a 14-day trial is listed.