Does it work with personal GitHub accounts?
Yes. Install the GitHub App on your personal account and use the labels in any of your repositories. Organizations work the same way, and each one has its own free minutes, credits and settings.
Can I use it for some workflows and keep GitHub-hosted runners for others?
Yes. Only jobs whose
runs-on is a Runloft label come to us. Everything else keeps running where it does today.What happens if Runloft is down?
Jobs with our labels wait in GitHub's queue and start when we are back. If you need to move them immediately, change
runs-on back to ubuntu-latest. Live status is on the status page.Do my secrets or logs go through your servers?
No. GitHub sends secrets and the job's steps directly to the runner inside the VM, and logs stream from the runner back to GitHub. Our control plane only sees job metadata from webhooks. See Security and isolation.
Can a job keep something on the machine for the next one?
No. Each job runs in its own microVM, which is deleted afterwards. Use
actions/cache for anything you want to reuse; see Caching.Is it safe for public repositories?
Single-use VMs remove the main risk GitHub describes for self-hosted runners on public repositories, which is a fork leaving something behind on a long-lived machine. Keep approval required for workflows from outside contributors.
Do you support GitHub Enterprise Server?
Not yet. Runloft works with github.com, including GitHub Enterprise Cloud organizations.
Do I need a card to start?
No. The first 3,000 Linux minutes each month are free. Add credits when you need more.
How do I try it on one repository?
When installing the GitHub App, choose Only select repositories, pick one, and change one job to
runs-on: runloft-ubuntu-24.04.