CI runners for GitHub Actions, CircleCI and Semaphore
One fleet of newer AMD EPYC machines, three CI providers, one price list. Change one line in your pipeline and the job runs here: 2x faster than GitHub-hosted at half the cost, and cheaper than CircleCI's and Semaphore's own machines size for size. The first 3,000 base minutes every month are free.
2x
faster than GitHub-hosted on the same jobs, measured at 4 vCPU
33%
less per minute than GitHub at 2 vCPU: $0.004 against $0.006
3,000
free base minutes every month, at every size
64
vCPU at the top, on x64 and arm64
Pick your CI
Managed self-hosted GitHub Actions runners, 2x faster at half the cost
Self-hosted GitHub Actions runners without the hosting: change the runs-on label on a job and it runs on newer AMD EPYC hardware at $0.008 a minute for 4 vCPU instead of GitHub's $0.012. Same workflow, same secrets, same actions. The speed is measured in public and the first 3,000 base minutes every month are free.
runs-on: bp-ubuntu-latest-x64-4xCircleCI self-hosted runners, 1.7x faster and up to 73% less a minute
CircleCI self-hosted runners, managed for you. Keep CircleCI, point a job's resource class at BuildPulse and it runs on our machines through CircleCI's own self-hosted runner, 33% less a minute than CircleCI's Linux VM at 2 and 4 vCPU and 1.7x faster than its Large, measured. Pipelines, contexts and approvals stay where they are.
resource_class: your-namespace/bp-x64-4xSemaphore self-hosted agents, up to 30% less a minute with the fee included
Semaphore self-hosted agents, managed for you. Keep Semaphore, point a block's agent type at BuildPulse and it runs on our machines through Semaphore's own self-hosted agent, up to 30% less a minute than Semaphore's f1 machines even after Semaphore's $0.0025 self-hosted fee, with sizes up to 64 vCPU where Semaphore's x86 machines stop at 4. Pipelines, promotions and secrets stay in Semaphore.
type: s1-bp-x64-4xPrices, benchmarks and the calculator
How BuildPulse runners work
The hardware, the caching, the per-org usage analytics, and the public benchmarks behind every speed claim on this site.
GitHub Actions cost calculator
Pick a CI, an architecture and a size, and see a month on their machines next to the same jobs on ours, free allowances taken off on both sides.
BuildPulse vs GitHub-hosted runners
The October benchmark, per-minute prices by size, free minutes on both sides, and the one-line change.
BuildPulse vs Depot
Per-minute prices size by size on x64 and arm64, what BuildPulse adds, and where Depot may fit better.
CircleCI and Semaphore setup guide
Step-by-step setup for both, with prices next to each vendor’s own machines.
Common questions
Which CI providers do BuildPulse runners support?
GitHub Actions, CircleCI and Semaphore, on the same machines at the same per-minute prices. On GitHub Actions you change the runs-on label, on CircleCI the resource class, and on Semaphore the agent type. Everything else in the pipeline stays where it is.
How much do BuildPulse runners cost?
From $0.004 a minute for 2 vCPU on x64, billed per minute with no minimums and no plan. The first 3,000 base minutes every month are free, at every size, and no credit card is needed to use them.
Are BuildPulse runners faster than GitHub-hosted runners?
Yes, and the measurement is public: 2x faster on the same jobs at 4 vCPU in a benchmark you can rerun from its repository. With the cheaper minute counted, the same work costs half as much.
Is this self-hosting?
No. Each job runs on a fresh machine that is discarded when the job ends, and BuildPulse runs the fleet. There are no instances to patch and no autoscaler to tune; on CircleCI and Semaphore the machine joins through the vendor’s own self-hosted runner or agent.
Move one job and time it
Point one job at a BuildPulse machine and compare the run times for a day. Everything else in your pipeline stays where it is.
3,000 free minutes every month · No credit card required