self-host →

What are your CI minutes actually costing you?

Punch in your monthly GitHub Actions minutes and see the bill on GitHub-hosted runners next to the same workload on self-hosted RunsOn — real EC2 spot prices in your own AWS account, no per-minute markup.

RunsOn deploys as one CloudFormation stack in about 10 minutes, and the commercial license is free for 15 days.

toggle a platform off by setting its minutes to 0

Start from a common setup

Not sure where to begin? Load a typical CI shape and tweak from there — the calculator updates instantly.

Per-runner cost, by size

GitHub-hosted vs RunsOn $/min for every runner size — across architectures and instance generations. Pick spot or on-demand and set your gp3 root volume to match your setup.

arch
generation
pricing
gp3 root gb mb/s
runner instance RunsOn / min GitHub / min you save RunsOn CPU GitHub CPU CPU vs GitHub
1cpu t8i.medium $0.0007 $0.0020 3× 3,201 2,269 +41%
2cpu m8a.large $0.0009 $0.0060 7× 3,849 2,269 +70%
4cpu m8a.xlarge $0.0015 $0.0120 8× 3,849 2,269 +70%
8cpu c8id.2xlarge $0.0024 $0.0220 9× 3,212 2,269 +42%
16cpu c8id.4xlarge $0.0043 $0.0420 10× 3,212 2,269 +42%
32cpu c8id.8xlarge $0.0091 $0.0820 9× 3,212 2,269 +42%
48cpu c8a.12xlarge $0.0099 — — 3,846 ——
64cpu c8i-flex.16xlarge $0.0126 $0.1620 13× 3,209 2,269 +41%
96cpu c8id.24xlarge $0.0165 $0.2520 15× 3,212 2,269 +42%
spot prices (7-day average, cheapest zone) · us-east-1 · incl. 30GB gp3 @ 400 MB/s billed by AWS, to the second

How this is calculated

01Where do the prices come from?+
RunsOn figures are real EC2 prices in us-east-1, including a 30 GB gp3 root volume — spot by default (the cheapest zone's price, averaged over 7 days), with an on-demand toggle. GitHub figures are GitHub-hosted per-minute rates. Both are normalized to $/min and multiplied by your minutes. See the full runner cost table.
02Does the estimate include the RunsOn license?+
Yes. The yearly total adds the flat Commercial license ($350/yr) on top of compute, so the savings shown are net of what you pay RunsOn. Compute itself is billed by AWS, directly to your account — there is no per-minute markup.
03Why is self-hosted so much cheaper?+
You pay AWS spot prices for the exact instance a job needs, only while it runs, instead of a fixed per-minute rate with a margin baked in. On Linux from 2 vCPU up, that comes to 5–15× under GitHub-hosted per minute, disk included. Faster CPUs also mean jobs finish sooner, which compounds the saving.
04What about caching, data transfer, and queue time?+
This calculator covers compute, which dominates the bill. RunsOn's S3-backed cache lives in your account (no egress to a third party), and faster runners cut wall-clock time further. Storage and transfer are typically cents per job.

Now get that number on your own AWS bill.

“A drastic reduction in our CI/CD costs, which have decreased from $1,400 per month with GitHub Runners to just $70 per month.” — Mandeep Singh, DevOps Engineer, DarioHealth

Deploy one CloudFormation stack, move a slow job with a one-line label change, and watch it land on a Spot instance you own. The trial is 15 days of the real product.