CI runners + Terraform runs
Fast GitHub Actions runners and OpenTofu runs on one platform. One meter, one bill, and a single view of everything a commit set in motion. Pay for the compute you used — not per seat, not per resource.
One line for CI. A hostname for infrastructure. We open the pull request for you.
What we can prove
The category settled on $0.004. We run on high-clock bare metal we buy rather than rent, so the same job costs a quarter less before it has run any faster.
Our published rate. Compare against any competitor's pricing page.
Cache and sticky-disk storage is $0.05/GB-month against $0.50 elsewhere, and a static IP is $10/month against $100. Storage on disks we already own should not be a margin business.
Our rate card against Blacksmith's published pricing, Aug 2026.
A test suite and a terraform apply draw from the same allowance at the same rate, because they are the same thing: minutes on a sized machine. One bill, one number to forecast.
1 run-minute = one minute of a 2 vCPU / 8 GiB machine.
What you will not find here is a speed multiplier. We run on faster hardware and we believe your jobs will finish sooner — but until we have published a benchmark you can re-run, with the repository, the commit, the machine size and the cache state written down, we are not going to put a number on it. Everyone else's is modelled.
One timeline
One commit. Two test jobs and a production apply, joined by the SHA that caused them. When a deploy goes wrong at 4pm, the run that let it through is the row above it — not a different tab, a different vendor and a different bill.
Nobody else can show you this. A CI vendor sees your tests and stops at the merge. A Terraform platform sees your infrastructure and has no idea what produced it. We run both, so the causal chain survives — and so does the bill, which arrives once, in one unit, for both.
One meter
$10 per organisation per month, including an allowance of run-minutes, then per minute above it. No per-seat charge — invite everyone. No per-resource charge — your estate can be as large as it likes.
Queue wait. Sandbox cold start. Provider downloads from our mirror. Control-plane API calls. State reads and writes.
That list exists because a minute-based meter has an obvious hazard: if the platform is slow, we get paid more. So the clock starts when your code starts and stops when it exits. Every second of latency we introduce is on our side of the line, and every second we remove costs us money. You should not have to take our word for it — the meter is built so the incentive runs the right way on its own.
Feature parity
Your workflows do not change. Same YAML, same actions, same secrets, same logs in the GitHub UI — you change the runner label and everything else carries on working.
The third column is the one worth reading. Every platform comparison you have seen lists only the first two, which is why none of them help you decide. If something in that column is load-bearing for you, we would rather you found out here than three weeks into a migration.
Where we actually differ
A comparison table that wins every row is not a comparison, it is a brochure. Here is where we are genuinely ahead, and where a competitor or your own hardware matches us.
| Capability | runners.io | CI vendors | Terraform platforms | Self-hosted |
|---|---|---|---|---|
| CI runs and infrastructure runs on one timeline Requires running both. Nobody else does. | Yes | No | No | No |
| One meter across both | Yes | N/a | N/a | No |
| Billed per resource under management HCP Terraform charges for the size of your estate, whether or not you touch it. | Never | N/a | Yes | No |
| Per-seat pricing | Never | No | Varies | No |
| EU region available today Blacksmith's region selector offers US West only; the rest are marked Soon (Aug 2026). | Yes | Not yet | Yes | Yes |
| State diff, rollback and recovery window HCP Terraform's states screen is a flat list of version IDs. | Yes | N/a | No | No |
| Cache hit rate, not just cache size | Yes | No | N/a | Build it |
| One microVM per job, destroyed after Genuinely equal. Firecracker under a jailer, never reused between jobs. | Yes | Yes | Yes | Depends |
| Single-core performance Self-hosted bare metal matches this. Anyone claiming otherwise is selling you something. | Yes | Yes | N/a | Yes |
| Someone else runs it at 3am | Yes | Yes | Yes | No |
Getting here
Connect your GitHub organisation, pick the repositories, and we raise a pull request that changes the runner labels and the Docker build steps. Nothing runs on our machines until you merge it, and reverting is the same button any other PR has.