BuildPulse Runners
BuildPulse Runners run your GitHub Actions, CircleCI, and Semaphore CI jobs 2x faster at half cost, using optimized infrastructure - change one line to get started.
We use GitHub’s self-hosted functionality to run builds on our infrastructure that’s optimized for CI-type workloads. As a foundation, we’ve tuned VMs and block storage which increases baseline performance and also cuts costs in half. We then also provide a toolkit to further speed up your builds, like powerful remote docker builders, docker layer caching, dependency caching, and more. With all of these combined, we’ve seen 2x+ performance improvements.
Why BuildPulse?
Any CI System: Seamlessly integrates with (without replacing) your existing CI system – GitHub Actions, CircleCI, and SemaphoreCI – with minimal configuration.
Performance: We use GitHub’s self-hosted functionality to run builds on our infrastructure that’s optimized for CI-type workloads. As a foundation, we’ve tuned VMs and block storage which increases baseline performance and also cuts costs in half.
Cut CI Cost: We price runners at half the cost of GitHub’s hosted runners. BuildPulse runners also consume less minutes due to better performance, so you'll likely see > 50% cost savings.
1-line Change: Faster than your next build takes to finish. BuildPulse uses the same images and build environment as GitHub Actions, CircleCI, and Semaphore CI - just point your workflow files to our infrastructure.
Unlimited Concurrency: BuildPulse jobs don't compete against each other for resources. You can run as many jobs as you want in parallel.
Fast Cache: We have co-located caching available at all levels - Docker image layers, application dependencies, and artifacts. This means your builds are faster and more reliable.
Toolkit: Building blocks to further speed up your pipelines.
Instant Observability: Built-in Prometheus endpoints providing seamless integration with your existing monitoring tools.
Security: SOC 2 Type 2-compliant, and your builds are network- and compute- isolated.
White-glove Support: Dedicated, proactive assistance ensuring smooth operations.
Customizable Images and Machine Configurations: Bake your own images or choose optimized templates tailored specifically for your uilds.
Do we replace your CI system?
No. We use GitHub Actions / CircleCI / Semaphore CI self-hosted functionality to run your builds on our infrastructure.
Other than faster builds, there are no changes to your developers' workflows - you can continue using your CI system as-is.
Getting Started
There are 2 steps to enabling BuildPulse Runners for your CI system.
Login to BuildPulse and install the BuildPulse GitHub App to your organization account. This allows BuildPulse to register runner agents with your account and authorize them to run your jobs.
Change your workflow files to use the BuildPulse runner.
See the Quickstart guide for more info.
Security
BuildPulse Runners runs each job in a network- and compute- isolated environment with ephemeral VMs that leave behind a clean state after every run.
BuildPulse is SOC 2 Type 2 certified - please contact sales@buildpulse.io for more information.