| Limit | Default | Can change |
|---|---|---|
| Concurrent jobs | 200 | Lower it yourself in Settings; request a higher limit. |
| Job duration | 6 hours | Same as GitHub-hosted. Use timeout-minutes to go lower. |
| Free minutes | 3,000 Linux minutes per month | No |
| Monthly spend limit | None | Set it in Settings. |
| Windows and macOS | Off | Request access. |
| Active API tokens | 50 per account | Revoke unused ones. |
| Alert email addresses | 20 per account | No |
What happens at the concurrency limit
Jobs above the limit wait in the queue and start as soon as a running job finishes. They are not rejected and they are not billed while waiting. The dashboard shows queued jobs and the median queue time for the month.
What happens at the spend limit
New jobs are not started once the month's spend reaches the limit; they wait in the queue, marked Spend limit reached in the dashboard. Jobs already running finish normally.
Not supported yet
- GitHub Enterprise Server. Runloft works with github.com accounts and organizations.
- Static outbound IP addresses.
- GPU machines.