CI Runnerscirunners.org
Guide

How third-party GitHub Actions runners work

Answer in brief

A third-party runner service is, to GitHub, a fleet of self-hosted runners that someone else operates. You install the vendor’s GitHub App on your organisation and change the runs-on label in a workflow. When a job is queued, GitHub notifies the vendor, which starts a clean machine, registers it as a single-use runner for that job and destroys it afterwards. Workflows, actions, secrets and logs stay in GitHub.

By the CI Runners editors · Updated

What happens when a job runs

  • 1. Install. An organisation owner installs the vendor’s GitHub App and chooses which repositories it covers. The app receives webhook events about workflow jobs and permission to register self-hosted runners.
  • 2. Label. You edit a workflow so that runs-on names one of the vendor’s labels, which usually encodes size, architecture and image.
  • 3. Queue. A push or pull request triggers the workflow. GitHub queues the job and sends the vendor a webhook saying a job with that label is waiting.
  • 4. Start. The vendor starts a machine, typically a microVM or VM on its own hardware, and registers it with GitHub as an ephemeral or just-in-time runner.
  • 5. Run. GitHub assigns the job. The runner checks out the code and runs the steps exactly as a GitHub-hosted runner would. Logs stream to GitHub.
  • 6. Destroy. When the job ends the runner deregisters and the machine is deleted.

From the workflow’s point of view nothing else changes: the same actions, the same secrets, the same checks on the pull request.

What a vendor can change

Since the workflow is the same, vendors compete on the machine and what surrounds it:

  • Hardware. Newer or higher-clocked CPUs than the standard hosted runner, more sizes, arm64, sometimes macOS, Windows or GPUs.
  • Price. A lower per-minute rate for the same core count.
  • Caching. A backend for actions/cache in the same data centre as the runners, and Docker layer caching on persistent disks.
  • Images. Most track GitHub’s official runner images so that preinstalled tools match, and some let you bring your own.
  • Visibility. Dashboards for job duration, queue time, flaky tests and cost.
  • Networking. Static egress IPs or private connectivity to your network.

What the vendor can see

The job runs on the vendor’s machine, so anything the job can read, the machine can read: the checked-out source, the secrets passed to steps, the artefacts it builds. That is equally true of GitHub-hosted runners; the difference is which company operates the machine.

Reasonable checks before adopting one:

  • How is one customer’s job isolated from another’s? A dedicated VM or microVM per job is the model to look for.
  • Are runners single-use, and is the disk wiped or destroyed afterwards?
  • What permissions does the GitHub App request, and for which repositories?
  • Where do the machines run, and which compliance reports can the vendor share?
  • How are caches scoped between repositories and branches?

If the answer has to be “inside our own account”, look at runners in your own cloud instead. The security guide goes further.

Switching and switching back

Adoption is deliberately small: one app installation and one line per job. That also makes it easy to trial two vendors on different workflows, and to move back by restoring the original label.

Things that can differ and are worth testing on your own workflows: tools missing from or added to the image, actions that assume GitHub’s network or GITHUB_TOKEN behaviour, the cache backend, and how the service behaves when GitHub itself has an incident. A third-party runner depends on GitHub’s API being up and adds its own availability on top.

Frequently asked questions

Do third-party runners replace GitHub Actions?
No. They replace only the machine a job runs on. Workflows, triggers, secrets, logs and the pull-request checks all remain in GitHub Actions.
How do I switch a workflow to a third-party runner?
Install the provider’s GitHub App on your organisation, then change the runs-on value of each job to one of the provider’s labels. To go back, restore the original label.
Does GitHub charge for jobs that run on third-party runners?
Not today. To GitHub a third-party runner is a self-hosted runner, and GitHub’s billing documentation lists self-hosted runners as free. In December 2025 GitHub announced a $0.002 per minute platform charge for self-hosted runner usage from March 1, 2026, then postponed it; no new date has been published. See CI runner pricing.

Sources

  1. docs.github.com/en/actions/concepts/runners/self-hosted-runners
  2. docs.github.com/en/actions/reference/runners/self-hosted-runners
  3. docs.github.com/en/rest/actions/self-hosted-runners
  4. docs.github.com/en/billing/concepts/product-billing/github-actions
  5. github.blog/changelog/2025-12-16-coming-soon-simpler-pricing-and-a-better-experience-for-github-actions/

Check before you rely on it. Products change quickly, and this page reflects public documentation as of November 22, 2026. Confirm anything that matters in the provider’s own documentation.

Cite this page

CI Runners. (2026). How third-party GitHub Actions runners work. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/guides/how-third-party-github-actions-runners-work/