Docs
Limits and FAQ
Limits
| Pay as you go | Pro | Team | |
|---|---|---|---|
| vCPUs at once | 4 | 8 | 16 |
| Biggest machine | 4 vCPU | 8 vCPU | 16 vCPU |
| Cache per repository | 10 GB | 10 GB | 10 GB |
- A job can run for up to 6 hours, as on GitHub’s runners.
- Runners are Linux. There are no macOS or Windows runners yet.
- A cache no job used for seven days is removed.
Enterprise sets its own limits. For more vCPUs on any plan, email [email protected].
FAQ
Do I have to change my workflows?
Only the runs-on line. Actions, secrets, environments, services: containers and caches work as they do on GitHub’s runners, because the job still runs GitHub’s own runner software.
Is a machine shared between jobs?
No. Each job gets a fresh machine that’s removed when the job ends. What a job leaves behind, outside the cache, is gone with it.
What happens when I hit the vCPUs-at-once limit?
New jobs wait and start, oldest first, as soon as running ones end. Nothing fails.
Can I use Checklane for some jobs and GitHub’s runners for others?
Yes. Only jobs with a Checklane label run on Checklane. The rest of the workflow stays on whatever it asks for. The dashboard also shows the jobs still on GitHub’s runners, so you can compare.
Why was my first run not faster?
The first run on Checklane starts with an empty cache. Later runs restore what it saved. See Caching.
What if my card fails or I reach my spend limit?
A failed charge doesn’t stop your jobs while Stripe tries again. At your spend limit, new jobs wait until you raise it. See Billing.
How do I stop using Checklane?
Change runs-on back and uninstall the GitHub App. You can cancel your plan and delete your organization in the dashboard.
Something’s not working
Email [email protected] with a link to the run. A person reads every email.