GitHub Actions cost reduction

Reduce your GitHub Actions costs by up to 70%

A drop-in replacement for GitHub-hosted runners. Change one line of YAML, keep your workflows exactly as they are, and pay from $0.0025 per minute instead of $0.008.

30 days free · No credit card required · Up to 6,000 free runner minutes

Where the money actually goes

You pay list price for every minute
GitHub-hosted Linux runners bill at $0.008/min at list price. The same 2 vCPU class on Latchkey is $0.0025/min - up to 70% less for the same work.
You pay twice for flaky failures
A transient registry timeout or an OOM kill fails the job, and you pay for the failed run and the re-run. Latchkey repairs those failures mid-run instead, so the minutes you already spent are not thrown away.
You pay for waiting
GitHub-hosted runners cold start in roughly 30 to 60 seconds. Latchkey cold starts in about 10 seconds, and warm-pool runners pick up in about 5 on the Launch and Scale plans.
You pay to re-download the same dependencies
GitHub caps cache at 10 GB per repository and restores it in serial chunks. Latchkey streams cache from same-region S3 in a single request with multi-threaded compression.

The bill nobody puts on the invoice

Per-minute rates are the visible half of CI cost. The other half is an engineer stopping what they are doing to look at a red build that was never their code: reading the log, recognising the registry timeout or the OOM kill, clicking re-run, waiting again. That time is not on any invoice, and it is the more expensive line.

Latchkey runners repair those failures while the job is still running. The agent diagnoses the cause on the machine, applies the fix, and retries the step, so the build goes green without anyone being interrupted. Self-healing is on by default, there is no separate charge for it, and there is nothing to configure.

The failure never reaches a human
Network timeouts, OOM kills, disk-full errors, missing tools, and config drift are fixed on the runner. Real failures in your code still fail, with the original logs, because those are the ones you want to see.
You stop paying for the same run twice
A transient failure normally costs you the minutes you already burned plus a full re-run. Healing the step in place means the first run is the only run.
Reviews stop stalling
A pull request blocked on a flaky check is a pull request nobody is reviewing. Fewer red builds means less waiting on both sides of the review.
Nobody has to own the pipeline
The work of babysitting CI usually lands on whoever is least able to say no. Automating the mechanical half gives that person their week back.

How self-healing works →

Per-minute rates, side by side

GitHub figures are the published Linux list price. Latchkey runners are Ubuntu 24.04 on x86_64.

Runner sizeGitHub-hostedLatchkeyYou save
2 vCPU / 8 GB$0.0080$0.0025up to 70%
4 vCPU / 16 GB$0.0160$0.0050up to 70%
8 vCPU / 32 GB$0.0320$0.0100up to 70%
16 vCPU / 64 GB$0.0200

Savings compare Latchkey list rates against GitHub-hosted Linux list rates. Your actual saving depends on runner size, minutes used, and how much of your bill is spent on failed runs.

How Latchkey compares

FeatureLatchkeyBlacksmithGitHub Hosted
Price per minutefrom $0.0025/minfrom $0.0040/minfrom $0.0080/min
Savings vs GitHub-70%-50%Baseline
Free minutes/mo (mid tier)4,0003,0003,000
Cold start speed~10s~10s30-60s
AI optimization insights
Cost performance analytics
Dependency cachingBuilt-in S3 streaming25 GB/repo10 GB/repo
AI scan runner images

Switching takes one line

Point runs-on at a Latchkey label. Your steps, actions, secrets, and matrix stay exactly as they are.

jobs:
  build:
-   runs-on: ubuntu-latest
+   runs-on: latchkey-medium
    steps:
      - uses: actions/checkout@v4

Work out your own numbers

Rather than take a percentage on faith, run your own minutes through the calculator, or read the breakdown of where GitHub Actions spend goes.

Questions about cost

How much do Latchkey Runners cost?

Runner minutes are billed by size: latchkey-small (2 vCPU / 8 GB) is $0.0025 per minute, latchkey-medium (4 vCPU / 16 GB) is $0.005, latchkey-large (8 vCPU / 32 GB) is $0.01, and latchkey-xlarge (16 vCPU / 64 GB) is $0.02. Custom runners bill at the xlarge rate. That is up to 70% cheaper per minute than GitHub-hosted runners. Every plan includes free runner minutes each month (2,000 on Developer, 4,000 on Launch, 6,000 on Scale), and usage beyond your included minutes is billed at the per-minute rate.

What plans does Latchkey offer?

Four plans: Developer at $5/month (1 repository, 2,000 free runner minutes, 1 seat), Launch at $19/month (up to 10 repositories, 4,000 free minutes, 1 seat included and extra seats at $5/month), Scale at $49/month (up to 40 repositories, 6,000 free minutes, 5 seats included), and Enterprise with custom pricing. Every plan starts with a 30-day free trial.

Do I need a credit card to start the free trial?

No. Every plan starts with a 30-day free trial with full feature access, and none of them ask for a card up front. Each workspace gets one trial.

What happens if I run out of free runner minutes?

Free minutes reset at the start of every monthly billing period. Once they are used, additional runner minutes are metered at the per-minute rate of the runner size you use. If you are on a card-less trial, new runner jobs are blocked until you add a payment method.

Do you charge for the number of workflow executions?

No. Analytics and monitoring are unlimited within your plan's repository limit; whether you run 10 builds a day or 10,000, monitoring costs the same. Runner minutes are the only metered usage: every plan includes free minutes each month, and usage beyond them bills at the runner's per-minute rate.

Do I need to pay for each developer on my team (per-seat pricing)?

Each plan includes seats: Developer is single-seat with no team members, Launch includes 1 seat, and Scale includes 5. On Launch and Scale you can add seats for $5/month each, so your whole engineering team can access the dashboard and insights.

Latchkey

Stay in the loop

Product updates and CI/CD tips. No spam, unsubscribe anytime.

We use cookies to improve your experience. Privacy Policy