Account

Spend controls

Built for agent-heavy CI: set a hard monthly spend limit and how many jobs run at once. At the limit, new jobs wait in the queue instead of running up your bill. API tokens and CI jobs can lower a limit but never raise it past the ceiling your admin sets. Email alerts at 80% and 100%.

Monthly spend limit

An organization admin sets it in the dashboard under Settings → Limits. It counts what you spend in a calendar month (UTC) after your free minutes. A limit of $0 means free minutes only. New organizations start at $100 a month.

At the limit, new jobs wait in GitHub’s queue instead of starting. They don’t fail, and they start when you raise the limit or the next month begins. Jobs already running finish, so the month can end slightly over the limit, by what those jobs cost.

Jobs at once

Set how many jobs can run at the same time. Extra jobs wait in GitHub’s queue until a runner is free. New organizations start at 20.

Ceilings for API tokens and CI jobs

An admin, signed in, can set a ceiling for each limit. API tokens and CI jobs can always lower a limit. They can raise it only up to the ceiling, and not at all when no ceiling is set. An automated tool or a coding agent can’t raise its own budget. Every change is in the activity log.

Alerts

Email at 80% and at 100% of the spend limit, and when jobs are waiting because of it. Each alert is sent once a month to your organization’s admins, plus up to 10 addresses you add.