AI Code Review is in early access·Request early access →
✓ Faster runners · Test Intelligence · AI Code Review

CI runners twice as fast at half the cost.

From the team that knows your test suite.

Change one runs-on line. Get faster builds, a smaller bill, and the flaky-test detection, coverage and CI metrics that come with every runner minute.

- runs-on: ubuntu-latest
+ runs-on: bp-ubuntu-latest-x64-4x

3,000 free runner minutes every month. No credit card, no plan required.

Public GitHub Actions benchmark
$0.004/min on x64 2 vCPU
3,000 free minutes a month
No credit card for runners

Runners for GitHub Actions · CircleCI · Semaphore. Test Intelligence on any CI.

Trusted by engineering teams at

  • Canva
  • Replit
  • Carbon Health
  • Brightline
  • Care Of
  • Homebrew
  • RE/MAX
  • Apify
  • Codecademy
  • Prisma
The platform

One platform for the whole CI path.

Run your jobs on faster runners. Trust your tests with flaky detection. Review every pull request with AI. Each piece works alone. Together they are one setup.

RUN

Half the build time, half the cost. One line to switch.

Drop-in replacement for GitHub Actions, Semaphore, and CircleCI hosted runners. Every job in our public GitHub Actions benchmark finished in at least 25% less time and cost at least 50% less. Per-minute billing, no minimums.

- runs-on: ubuntu-latest
+ runs-on: bp-ubuntu-latest-x64-4x
4x runner: $0.008/min vs $0.012 on GitHub Actions
TRUST

Find every flaky test. Then fix it.

Results compared across builds and branches, flaky tests ranked by the engineering time they burn, the worst quarantined so they stop blocking merges. No annotations, no SDK.

●checkout_flow_spec.rb · "applies coupon at checkout"
12.4% · 38 disruptions
●payments.test.ts · "retries idempotently on 503"
8.1% · 21 disruptions
●test_ingest.py · "dedupes concurrent uploads"
5.7% · 13 disruptions
REVIEW

A second reviewer on every pull request.EARLY ACCESS

Flags correctness bugs, missing edge cases, and obvious regressions. Stays quiet about style your linter already handles. Runs on frontier models.

buildpulse-v2reviewed
COMMENTED
Suggestion: NaN passes the typeof check (typeof NaN === 'number' is true), so clamp(NaN, 0, 10) silently returns NaN rather than throwing. Depending on intended use this may be fine, but worth a deliberate choice. (clamp.js:2)

We run BuildPulse on BuildPulse.

Every BuildPulse repo runs on BuildPulse Runners, uploads results to flaky detection, and gets an AI Code Review on every pull request. These are our own dashboards.

PUSH
c4db23b ci: modernize to BuildPulse v2 upload on BuildPulse runners buildpulse-example-jest · main
RUN
job queued for bp-ubuntu-latest-x64-2x
waiting
RUN
running the test suite
running
TRUST
results uploaded · 1 failure: payments.test.ts "retries idempotently on 503"
known flaky (fails 8.1% of runs) → quarantined, build stays green ✓
REVIEW
buildpulse-v2 reviewing the pull request
reading diff
walkthrough + verdict posted on the PR, findings taught by replying in-thread ✓
One push, all three products. This is our own pipeline. PUSH, RUN and REVIEW link to the real artifacts.
Runners

Switch in one line. Keep your CI.

Your workflows, your caches, your secrets and your provider stay where they are. The job lands on newer hardware with more cores, so it finishes sooner and the minute it runs on costs less. Run both side by side for a day and keep whichever is faster.

GitHub Actions

.github/workflows/ci.yml
jobs:
  test:
-   runs-on: ubuntu-latest
+   runs-on: bp-ubuntu-latest-x64-4x

CircleCI

.circleci/config.yml
jobs:
  test:
    machine: true
-   resource_class: large
+   resource_class: your-namespace/bp-x64-4x

Semaphore

.semaphore/semaphore.yml
agent:
  machine:
-   type: e2-standard-4
+   type: s1-bp-x64-4x

Sizes from 2 to 64 vCPU on x64 and arm64, Docker layer and dependency caches that survive across runs, and nothing to self-host. Billed per minute, no minimums.

Test Intelligence

Test Intelligence, included with every runner minute.

A faster machine still runs your flaky tests. BuildPulse reads the results every job already produces and tells you which failures are real, so a green build means something. It works on any CI, with or without our runners, and without changing a line of test code.

1

Detect.

BuildPulse analyzes results across CI builds to identify flaky tests automatically. No annotations, no SDK, no guesswork. Just connect your repo.

2

Quarantine.

The worst offenders are auto-quarantined so they stop blocking merges and triggering re-runs. Your pipeline goes green while the tests get fixed.

3

Fix.

Test owners get failure patterns, frequency data, and linked commits: everything they need to resolve the root cause, not just mute the symptom.

Model Context Protocol

Ask your CI a question. Get an answer with the data.

The BuildPulse MCP server brings flaky-test history, CI runs with per-test timings (on BuildPulse runners or anywhere else), and coverage straight into Claude, Cursor, and every MCP-aware assistant. No copy-paste between your editor and your dashboard.

claude + buildpulse MCP
you
Find flaky tests
Test history
Recent CI runs
Per-test timings
Repo flakiness
Coverage health
Works with
Claude Desktop
Cursor
ChatGPT
Windsurf
VS Code Copilot
Zed

Simple, predictable pricing.

Runners are billed per minute and need no plan. Test Intelligence plans scale with test volume.

Runners
$0.004/min

3,000 free minutes every month, then per-minute billing with no minimums. No credit card and no plan to start. About half the total cost of GitHub Actions. Start free →

Test Intelligence plans
from $119/mo

Flaky-test detection, coverage and CI metrics. $99/mo billed yearly. Every plan starts with a 14-day free trial, no charge today.

AI Code Review
Early access

AI Code Review pricing is announced at GA. Request early access →

Your next build could run on BuildPulse runners.

Change one runs-on line, run it next to your current runner for a day, and keep whichever is faster. Flaky-test detection, coverage and CI metrics come with the minute.

3,000 free runner minutes every month. No credit card required.

?