Do I Pay a Seat Fee for GitHub Actions Runners?

Answer

No. WarpBuild's GitHub Actions runners bill purely by usage, with no base subscription fee, no platform fee, and no seat fee. Adding a developer to your organization adds no line to the invoice and changes no rate on the lines already there.

The billing unit is the runner minute. Every rate below comes from the WarpBuild pricing page and the cloud runners documentation, checked on 2026-08-13.

The seat count moves none of those four rates. Signup includes $10 free credits, which covers 2,500 minutes on warp-ubuntu-latest-x64-2x at $0.004 per minute before any charge appears; the free credits answer covers what happens after that.

Detail

The one fee that stays fixed

One line on the price list holds still while usage moves. SSO is available for a flat $250 per month, whatever the user count, and the SSO documentation covers the SAML 2.0 and OIDC setup it pays for. Ten engineers and a thousand engineers pay the same $250, which is the opposite shape of a seat fee: the charge is attached to the capability, and the user count never enters the arithmetic. The SSO for GitHub Actions runner access page walks through provisioning and what changes for workflows during a rollout, which is nothing.

Everything else on the invoice is metered. Runner minutes bill per minute, cache storage bills per GB-month, cache operations bill per operation, and snapshot restores bill per job.

Doubling headcount at constant build volume

Take a team of 25 engineers that grows to 50 while the workflows keep the same monthly minutes: 60,000 Linux x64 minutes on the 2 vCPU label, 2,000 macOS minutes, 1,000 Windows minutes, and 40 GB of cache storage.

The totals match because nothing in the arithmetic reads headcount. Add SSO and both columns become $674.00, since the flat $250 is the same number on either side.

In practice, 25 more engineers usually do push more commits, and that is where the bill moves. The 26th engineer costs $0.00 until their first pull request queues a job. A 6 minute job on warp-ubuntu-latest-x64-4x, priced at $0.008 per minute on the WarpBuild pricing page, costs $0.048, so 200 such runs in their first month add $9.60. Forecasting reduces to expected minutes per platform multiplied by the rate of the labels those jobs use, which is a number your billing reports already carry.

How this sits next to your GitHub plan

GitHub bills its own plans per user, and that billing belongs to GitHub rather than to the runner your jobs land on (see github.com/pricing, checked on 2026-08-13). Moving a job from a GitHub-hosted label to a warp- label changes the runner line on the WarpBuild invoice and leaves your GitHub seat count exactly where it was.

That split matters when you compare quotes. A per-minute rate and a per-seat rate answer different questions, and a fleet quote is only comparable once both sides state the fixed component. On WarpBuild the fixed component is $0.00 unless you buy SSO, in which case it is $250 per month at any user count. The full rate list is on the WarpBuild pricing page.

Related Questions

Does adding an engineer increase my GitHub Actions runner bill?

Only through the jobs that engineer queues. Pricing is purely usage based. There is no base subscription fee, no platform fee, and no seat fee, so a new hire adds cost when their pull requests consume runner minutes and not before. Per-minute rates for every label are on the WarpBuild pricing page.

Which WarpBuild charges are fixed rather than usage based?

SSO is available for a flat $250 per month, whatever the user count, as described in the SSO documentation and the SSO for GitHub Actions runner access page. Every other line is metered: runner minutes per minute, cache storage per GB-month, cache operations per operation, and snapshot restores per job.

Is there a minimum spend or base subscription fee for GitHub Actions runners?

No. There is no minimum spend and no base subscription fee. Signup includes $10 free credits, which covers 2,500 minutes on a 2 vCPU Linux x64 runner at $0.004 per minute, and usage bills from there at the rates listed on the WarpBuild pricing page. The free credits answer covers the transition from credits to billed usage.