Documentation menu
Dashboard & analytics
Managed runners
Team & notifications
Billing & plans
Workflow files
Limits and concurrency
Job duration limits, concurrency, architecture support, disk sizes, and custom runner configuration limits per plan.
In short
- A Latchkey CI job can set timeout-minutes up to 180 (30 by default), a CLI job runs for up to 3 hours, and a Latchkey on GH runner for up to 4 hours from its start, or up to 8 when the job is still running at 4.
- 40 concurrent busy runners per workspace to start.
- Linux x86_64 only: no Windows, macOS, arm64, or GPU host runners today.
- Runners are single-use; persist outputs with artifacts and caches.
The numbers#
| Limit | Value |
|---|---|
| Maximum job duration | A Latchkey CI job can set timeout-minutes up to 180 (30 by default), a CLI job runs for up to 3 hours, and a Latchkey on GH runner for up to 4 hours from its start, or up to 8 when the job is still running at 4. |
| Concurrent jobs | Set by plan: Developer 20, Launch 40, Scale 80 busy runners per workspace, Enterprise by contract (idle warm and parked runners do not count); a trial runs at the Launch number |
| Spend limit | None by default; an owner or admin sets one in US dollars on the Billing page. At the limit Latchkey refuses new jobs, holds queued ones and stops running ones, GitHub Actions jobs on Latchkey runners included; it resets with the calendar month. |
| Operating system | Ubuntu 24.04 LTS only (no Windows or macOS runners) |
| Architecture | x86_64 (amd64) only; no arm64 host runners (arm images can be cross-built with docker buildx) |
| Disk | 100 GB (small, medium, large), 200 GB (xlarge), 100 to 500 GB for custom configurations |
| Custom runner configurations | Developer and Launch: 2, Scale: 10, Enterprise: unlimited |
| Region | Runners run in AWS us-east-1 |
What to do when you hit one#
The numbers only matter on the day one of them bites. What to change on your side when that happens:
timeout-minutes up to 180 (30 by default), a CLI job runs for up to 3 hours, and a Latchkey on GH runner for up to 4 hours from its start, or up to 8 when the job is still running at 4, so treat the cap as a hard ceiling, not a budget. Split the work into parallel jobs (each gets its own runner), or move it up a size so the same work finishes sooner.Two of these deserve a why. The job time limits, and the 8-hour hard cap on Latchkey on GH, are the same backstop that keeps self-healing retries from ever running up your bill: together they guarantee that a hung job cannot hold a machine, or your invoice, indefinitely. And the concurrency limit counts busy runners only, which is easy to misread: a warm pool sitting idle costs you none of your concurrency slots, so warm capacity never competes with your real jobs.
Custom runner configurations#
From the Runners page, you can create custom configurations with their own latchkey-<name> labels, choosing CPU/memory shape and disk size. The AI Scan flow analyzes your workflows and proposes the right configuration; its image is then built automatically and you are notified when the runner is ready to use. Until the image build completes, jobs targeting that label wait in the queue.
The full decision guide, including when a custom shape beats a preset and what it costs, is in Custom runners with AI Scan.
Good to know#
- Runners are single-use: one job per machine, destroyed afterward. Anything you write to local disk is gone when the job ends; use artifacts or caches for persistence.
- GitHub-hosted runner labels (
ubuntu-latestand friends) keep working side by side; you can migrate one job at a time. - If you need GPU, Windows, macOS, or arm64 hosts, keep those specific jobs on GitHub-hosted or other runners for now and mix freely within the same workflow.
Q.01What is the maximum job duration on a Latchkey runner?
A Latchkey CI job can set timeout-minutes up to 180 (30 by default), a CLI job runs for up to 3 hours, and a Latchkey on GH runner for up to 4 hours from its start, or up to 8 when the job is still running at 4. A job that needs longer should be split across jobs that hand work to each other through artifacts, because a single job approaching the limit is usually doing work that could run in parallel.
Q.02How many jobs can I run at once?
Each plan sets it: Developer 20, Launch 40, Scale 80 concurrent busy runners per workspace, and a trial runs at the Launch number. Enterprise limits are set by contract. If you regularly queue behind your number, the next plan up raises it.
Q.03Do Latchkey runners support Windows, macOS or ARM?
Not today. Latchkey runners are Linux x86_64 only, with no Windows, macOS, arm64 or GPU hosts. Those jobs can stay on GitHub-hosted or other runners and mix freely inside the same workflow, so this does not block adoption for the rest of your pipeline.