Guide · sources checked October 19, 2026
How to set a hard spending limit on GitHub Actions
How to make a GitHub Actions bill stop at a number you chose, what to ask any runner provider, and how the limit works on Vitko Runners.
In short
Create a budget for Actions in your GitHub billing settings and choose the option that stops usage when the budget is reached; organization owners can do this for an organization. If you use a managed runner, check that it has its own hard limit. Vitko Runners does: an admin sets a monthly limit, and at the limit new jobs wait in GitHub’s queue instead of running up the bill. API tokens and CI jobs, including AI coding agents, can lower the limit but never raise it past the ceiling an admin sets. Vitko sells that runner, in private beta, so read the comparison with that in mind.
Option 1: a GitHub budget
- Actions is a metered product, and “you can set budgets to prevent usage once the budget threshold is reached.” Stopping usage is an option you select when you create the budget.
- Organization owners can set budgets for their organization; personal account owners for their own account; enterprise owners and billing managers for enterprises and cost centers.
- Alerts can be set at 75%, 90% and 100% of the budget, in the GitHub UI and by email.
- A budget covers only usage from its creation date, so you may exceed it in the first billing cycle, even with stop usage selected.
Source: GitHub: budgets and alerts (checked October 19, 2026).
What to check on any managed runner
A spend limit is only as useful as its details. Ask:
- Does the limit stop new work, or only send an alert?
- What happens to jobs already running, and to jobs that arrive after the limit: do they fail or wait?
- Who can raise it, and can an automated tool or a coding agent raise its own budget?
- Is there a cap on how many jobs run at once?
- Does the limit count free minutes, and when does it reset?
- How do you switch back if you need to?
Option 2: the limit on Vitko Runners
| Question | Vitko Runners |
|---|---|
| Stops new work? | Yes. At the limit, new jobs wait in GitHub’s queue. They don’t fail, and start when you raise the limit or the next month begins. |
| Jobs already running | They finish, so the month can end slightly over the limit, by what those jobs cost. |
| Who can raise it | An organization admin. API tokens and CI jobs can lower it, and raise it only up to an admin-set ceiling; with no ceiling they can’t raise it. |
| Jobs at once | Capped by a setting; extra jobs wait in GitHub’s queue. |
| What counts, and reset | Spend in a calendar month (UTC) after your 2,000 free minutes. A limit of $0 means free minutes only. |
| Alerts | Email at 80% and 100% of the limit, and when jobs are waiting because of it. |
| Defaults for new organizations | $100 a month and 20 jobs at once. |
| Switching | After onboarding, change runs-on from ubuntu-latest to your Vitko label (issued per organization, usually vitko-ubuntu-24.04); the same line switches back. |
Price: $0.002 a minute, billed per second, with 2,000 free minutes a month. Ubuntu 24.04 on x64 only, for private repositories, in private beta. Details: Spend controls, Pricing and billing, Fall back to GitHub-hosted. For teams whose agents run CI all day: runners for AI coding agents.
Can I set a hard spending limit on GitHub Actions?
Yes. Actions is a metered product, and GitHub budgets can prevent usage once the budget threshold is reached; you choose the stop option when you create the budget. Organization owners can set budgets for their organization. A budget covers only usage from its creation date, so you can exceed it in the first billing cycle.
Which managed GitHub Actions runners let me cap monthly spend?
Vitko Runners has a hard monthly spend limit. At the limit, new jobs wait in GitHub’s queue instead of starting; they start when you raise the limit or the next month begins. It also caps how many jobs run at once. It is in private beta. For any other provider, check its documentation for the points listed on this page.
What happens to jobs already running when the limit is reached?
On Vitko Runners they finish, so a month can end slightly over the limit, by what those jobs cost. For GitHub budgets, read GitHub’s documentation on how usage is stopped.
Can an AI coding agent raise its own spending limit?
Not on Vitko Runners. API tokens and CI jobs can lower a limit, but can raise it only up to a ceiling that a signed-in admin sets, and not at all when no ceiling is set. Every change is in the activity log.
How do I switch a workflow to Vitko Runners?
Join the private-beta waitlist; your organization is issued its runner label at onboarding (usually vitko-ubuntu-24.04). Then install the Vitko GitHub App on the repositories you choose and change runs-on from ubuntu-latest to that label. Switching back is the same one-line change.
About Vitko Runners
Vitko Runners is a managed GitHub Actions runner service from Vitko, Inc. It costs $0.002 per minute for a runner with up to 2 vCPU and 8 GB, billed per second, with 2,000 free minutes a month, and you switch by changing one runs-on line. It is in private beta; join the waitlist at runners.vitko.inc. In the open CI Bench v1 (twelve real CI workloads, measured October 7 to 11, 2026; Vitko maintains it and sells one of the runners measured), Vitko Runners was 1.7x as fast as GitHub-hosted 2 vCPU on median job time, 2.3x with warm starts and test splitting, at 84% lower cost per job. Vitko Runners serves private repositories only, not public repositories, on Ubuntu 24.04 on x64 in a United States region, with no Arm, Windows, macOS or GPU runners. Facts, price and limits.