Runners

CI runners,faster builds at less than half the cost

BuildPulse Runners are a drop-in replacement for GitHub Actions, Semaphore, and CircleCI hosted runners. Modern hardware, smart caching, and per-minute billing: no workflow rewrites, no self-hosting overhead. Every speed claim on this page is measured in public, reproducible benchmarks.

GitHub Actions
# .github/workflows/ci.yml
jobs:
  test:
    runs-on: bp-ubuntu-latest-x64-4x  # ← swap
    steps:
      - uses: actions/checkout@v4
      - run: npm ci && npm test
Semaphore
# .semaphore/semaphore.yml
agent:
  machine:
    type: bp-ubuntu-latest-x64-4x  # ← swap

blocks:
  - name: Test
    task:
      jobs:
        - name: npm test
          commands:
            - npm ci && npm test
CircleCI
# .circleci/config.yml
jobs:
  test:
    machine:
      image: ubuntu-2404:current
    resource_class: buildpulse/bp-ubuntu-latest-x64-4x  # ← add
    steps:
      - checkout
      - run: npm ci && npm test

Built for fast-moving teams

Drop-in replacement

Swap one line in your workflow config: GitHub Actions, Semaphore, or CircleCI. Your pipelines keep working, just faster.

Faster CPUs, more cores

Newer-generation AMD EPYC processors, 2.7x the measured sysbench throughput of GitHub-hosted runners. Real compile, test, and docker workloads finish 1.2-2x faster.

Half the total cost

Per-minute rates 20 to 50% below GitHub, plus measurably faster hardware, so the same workloads cost 54 to 65% less. No surprise bills, no minimums.

Smart caching

Built-in Docker layer, dependency, and build cache that survives across runs.

No self-hosting headaches

No EC2 instances to patch, no autoscaler to tune, no security boundary to worry about.

Per-org usage analytics

See exactly which workflows burn minutes and where to optimize, on every plan. GitHub Actions, Semaphore, and CircleCI minutes tracked separately.

Per-minute pricing, no minimums

Usage-based billing, no commitments. Per-minute rates run 20–50% below GitHub's larger runners, and with ~2× faster hardware, most teams land near half the total cost. arm64 is priced below x86, and Docker builders carry no premium over standard.

Standard runners: x86

RunnervCPURAMStorageBuildPulse $/minGitHub Actions $/minSavings
2x28 GB75 GB$0.004$0.00633%
4x416 GB150 GB$0.008$0.01233%
8x832 GB300 GB$0.016$0.02227%
16x1664 GB600 GB$0.032$0.04224%
32x32128 GB1200 GB$0.064$0.08222%
64x64256 GB2400 GB$0.128$0.16221%

Standard runners: arm64 (Graviton)

RunnervCPURAMStorageBuildPulse $/minGitHub Actions $/minSavings
2x28 GB75 GB$0.0025$0.00550%
4x416 GB150 GB$0.005$0.00838%
8x832 GB300 GB$0.010$0.01429%
16x1664 GB600 GB$0.020$0.02623%
32x32128 GB1200 GB$0.040$0.05020%
64x64256 GB2400 GB$0.080$0.09818%

Docker builder runners: NVMe-backed (same rate as standard)

RunnervCPURAMStorageBuildPulse $/minGitHub Actions $/minSavings
4x416 GB150 GB$0.008$0.01233%
8x832 GB300 GB$0.016$0.02227%
16x1664 GB600 GB$0.032$0.04224%
32x32128 GB1200 GB$0.064$0.08222%

Visibility you do not get from your CI provider

Track minutes per workflow, per repo, and per team. See which jobs are slowest and where the cache is missing. Drill into any run to see the exact bottleneck, across GitHub Actions, Semaphore, and CircleCI.