GitHub Actions runners
Keep your workflows.
Cut runner costs.
Choose your runner, change one label, and keep building in GitHub Actions. Sprintbox handles the machines; your team keeps shipping.
Standard from $0.002/min · Basic from $0.00125/min
2 vCPUs · Linux x64 · USD
Start with your workflow
Keep your steps. Choose your runner.
name: Build and test
on: [push, pull_request]
jobs:
build:
runs-on: sprintbox-standard-2
steps:
- uses: actions/checkout@v7
- uses: actions/setup-node@v7
with:
node-version: '24'
- run: npm ci
- run: npm testStandard is the recommended default. Choose sprintbox-basic-2 for Basic. Compare runner labels.
Runner pricing
More of your budget.
Less spent on runner minutes.
Two runner families. One straightforward choice in your workflow. Compare paid Linux x64 rates at the same vCPU count.
Standard
RecommendedOur default runner family for your builds and tests.
sprintbox-standard-2Basic
Lowest per-minute priceA lower-cost option when the per-minute rate comes first.
sprintbox-basic-2| vCPUs | GitHub-hosted | Sprintbox Standard | Sprintbox Basic |
|---|---|---|---|
| 2 | $0.006 | $0.002 | $0.00125 |
| 4 | $0.012 | $0.004 | $0.0025 |
| 8 | $0.022 | $0.008 | $0.005 |
| 16 | $0.042 | $0.016 | $0.010 |
Rates checked 25 October 2026. GitHub pricing source · All Sprintbox sizes and labels
What would your runner minutes cost?
For the same number of billable minutes on each service.
Enter a whole number of minutes from 0 to 100,000,000.
10,000 billable minutes · 2 vCPUs
- GitHub-hosted
- $60.00
- Paid runner minutes
- Sprintbox Standard
- $20.00
- $40.00 less per month
- Sprintbox Basic
- $12.50
- $47.50 less per month
Rate estimate, not a performance benchmark. Equal vCPU counts do not imply equal runtime. Actual costs depend on execution time and per-job billing; taxes, storage and GitHub plan fees are excluded. See Sprintbox billing.
GitHub’s standard runners are free for public repositories, and private repositories receive included minutes based on their plan. This comparison uses paid rates after those allowances; Sprintbox charges still apply. GitHub’s larger runners require Team or Enterprise Cloud and do not use included minutes. GitHub billing details.
Performance in your project
Your build is the benchmark.
A dependency-heavy test suite and a CPU-heavy build put different demands on a runner. Start with a workflow your team runs every day.
Try Sprintbox on your workflow- 01
Keep the workload consistent
Use the same commit, dependencies and vCPU count. Compare cold and warm caches separately.
- 02
Measure the whole experience
Track queue and startup time alongside build and test execution. Repeat runs to account for variation.
- 03
Compare cost per completed job
Use measured runtime and billed minutes to choose the runner that fits your project.
Three steps to your first run
Your workflows stay in GitHub. Sprintbox handles the runner and gives your team a place to manage it.
1. Create your workspace
Create an account and complete billing setup before connecting GitHub.
2. Connect your repositories
Install the GitHub App and choose which repositories it can access.
3. Update your runner label
Use
sprintbox-standard-2inruns-onand start a job. Follow the quickstart.
Know what’s running.
See what’s running and manage the resources around each job, without losing track of your repositories.
Open your workspace- Active jobs
- Follow runner allocation and open the associated workflow job on GitHub.
- Repositories
- Review connected accounts and repositories. Manage app access through GitHub.
- Runner choice
- Choose Standard or Basic directly in your workflow. Explicit labels keep your selected family consistent.
- Usage
- Review recorded runner charges and the resources allocated to active jobs.
Before you connect
A few practical details about using Sprintbox with GitHub Actions.
Do I need to rewrite my workflows?
Your workflows stay in GitHub Actions. Once setup is complete, change runs-on to the runner label enabled for your workspace. Check that your jobs’ operating system and tool requirements match the selected runner.
Which repositories can Sprintbox access?
You select repository access when installing the GitHub App. You can review and change that access through GitHub’s installation settings.
Where do I find runner availability and billing?
Read the runner guide to choose a label, and open your Sprintbox workspace to review usage and billing. Runner availability depends on the enabled profiles and capacity.
Can I keep using my existing build tools?
Your jobs still use GitHub Actions steps and actions. Keep the setup steps for your languages and dependencies, and confirm compatibility with your chosen runner environment.