# What are managed GitHub Actions runners? How they differ from hosted and self-hosted

Managed runners are GitHub Actions runners a vendor operates for you. A table of who owns the machine, patches it, scales it and bills it, against hosted and self-hosted.

By Grant Unwin, published 2026-11-01. Checked against GitHub's documentation on 2026-11-17. The web page: https://www.runners.io/blog/what-are-managed-github-actions-runners

Managed runners are GitHub Actions runners that a vendor operates for you. GitHub still schedules the job and runs your workflow, and you usually point a job at the vendor’s machines by changing 1 line, its `runs-on` label. The vendor patches, scales and bills the machines. They sit between GitHub-hosted runners, which GitHub operates, and self-hosted runners, which you operate. See the sizes and rates of our [managed GitHub Actions runners](https://www.runners.io/runners). Our [GitHub Actions runner size](https://www.runners.io/blog/github-actions-runner-size-guide) guide compares the sizes.

**In short**

- A managed runner is a machine a vendor operates; GitHub still schedules the job, and you change the runs-on label.
- GitHub-hosted runners are operated by GitHub and billed at its per-minute rates, rounded up per job, and free for standard runners in public repositories.
- Self-hosted runners are yours to build, patch and secure, and GitHub's billing page lists their usage as free.
- A managed runner has the vendor's rate card, rounding rule and isolation; we found no GitHub page that covers a vendor's isolation.
- A GitHub larger runner is a GitHub-hosted runner with more cores, not a managed one.

There are 3 ways to get a runner for a GitHub Actions job: GitHub-hosted, self-hosted, and what we call managed, where a vendor operates the machines. GitHub’s own pages describe 2 kinds, hosted and self-hosted, and “managed” is our term for a vendor-run service. The table compares them on what usually decides the choice. We sell managed runners, so weigh what we say about them accordingly; every statement about GitHub’s own runners is from GitHub’s documentation, read on the date this post was last checked.

| Compared on | GitHub-hosted | Self-hosted | Managed |
| --- | --- | --- | --- |
| Who operates the machine | GitHub | You | A vendor |
| Who patches it | GitHub: machine maintenance and upgrades are taken care of for you | You | The vendor, for the machine. Ask who updates the runner software |
| Who scales it | GitHub | You. GitHub recommends autoscaling with ephemeral runners, and does not recommend it with persistent ones | The vendor |
| What you pay for | GitHub's per-minute rate for the runner type, with each job rounded up to a whole minute. Standard runners are free in public repositories, and paid plans include some compute | The machines and the people who run them. GitHub's billing page lists self-hosted runner usage as free | The vendor's rate card and its rounding rule. Ask for both in writing |
| Who sees your code and secrets while a job runs | GitHub | You | The vendor |
| What GitHub says about isolation | A new virtual machine for each runner; single-CPU runners are containers | No guarantee of an ephemeral clean virtual machine | We found no GitHub page that makes an isolation promise for a vendor's runners, so ask the vendor |
| Longest job | 6 hours, or 15 minutes on single-CPU runners | 5 days | Set by the vendor. Ours is up to 6 hours, the same as GitHub's, or a shorter maximum you choose |
| How a workflow picks it | runs-on: ubuntu-latest, or another GitHub label | runs-on with the runner's labels, such as self-hosted | runs-on with the vendor's label; check what each vendor wants. Ours goes in runs-on on its own |

## How are managed runners different from GitHub-hosted runners?

The machine has a different owner, and so does the bill. On GitHub-hosted runners in a private repository you pay GitHub its published per-minute rate once the minutes your plan includes are used, and GitHub rounds each job up to a whole minute; standard runners are free in public repositories. On a managed runner you pay the vendor its rate, under its own rounding rule, and the 2 can differ even at the same price per minute. The [ten questions for choosing a provider](https://www.runners.io/blog/choose-a-github-actions-runner-provider) and the [calculator](https://www.runners.io/calculator) are the way to compare them with your own minutes.

## How are managed runners different from self-hosted runners?

Nobody on your side runs the machines. With self-hosted runners you build, patch, scale and secure the fleet, and GitHub says self-hosted runners can be persistently compromised by untrusted code in a workflow, and it recommends ephemeral runners, for autoscaling and as just-in-time runners that perform at most one job, while warning that re-using hardware can still expose information. A managed runner moves that work to the vendor, and the question moves with it: is the vendor’s machine clean for every job? Ours is. Each job runs in its own virtual machine, which no other job uses and which is destroyed, or rebuilt from our image, when the job ends, with its disk, memory and firmware state erased. Each job gets its own single-use runner registered on your repository for that one job. Only the caches and the sticky disk you keep on purpose outlast a job. To GitHub, ours is an ordinary self-hosted runner. We keep this page to cost, security and trade-offs, and leave how to run a fleet to GitHub’s documentation.

## What do I change in a workflow?

One line per job: the `runs-on` value. The label is the vendor’s, and a workflow can use it for some jobs and GitHub’s for the rest, because `runs-on` is set per job. This keeps the lint job on GitHub and moves the test job to one of our labels:

```yaml
name: ci
on: [push]
permissions:
  contents: read
jobs:
  lint:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v7
      - run: make lint
  test:
    runs-on: runnersio-2vcpu-ubuntu-2404
    steps:
      - uses: actions/checkout@v7
      - run: make test
```

Everything else in the workflow stays as it is. On ours, [`actions/cache` works unmodified](https://www.runners.io/docs/caching/actions-cache), and the [guide to moving from GitHub-hosted runners](https://www.runners.io/docs/getting-started/from-github-hosted-runners) lists what else does and does not carry over. The [migration page](https://www.runners.io/migrate) opens the change as a pull request.

## Is a managed runner the same as a GitHub larger runner?

No. A larger runner is a GitHub-hosted runner with more cores, available on GitHub Team and GitHub Enterprise Cloud, billed by GitHub at its own rates and, unlike a standard runner, billed in public repositories too. GitHub operates it. A managed runner is operated by someone other than GitHub, and billed by them.

## What can go wrong with a managed runner?

Three things are worth knowing before you start. The vendor holds your code and secrets while a job runs, so [what to ask a third-party runner service](https://www.runners.io/blog/is-a-third-party-github-actions-runner-service-safe) is the first reading. If the vendor stops, ask what a job does when its label has no runner. GitHub’s limits page says a job queued for a self-hosted runner is cancelled after 24 hours, but we found no GitHub page that says what happens to a label no runner matches, so test it. And the bill is the vendor’s, with its own rounding, so run your own minutes through it before you move everything.

## Sources

- [GitHub-hosted runners](https://docs.github.com/en/actions/concepts/runners/github-hosted-runners)
- [Secure use reference](https://docs.github.com/en/actions/reference/security/secure-use)
- [Autoscaling with self-hosted runners](https://docs.github.com/en/actions/reference/runners/self-hosted-runners)
- [Using labels with self-hosted runners](https://docs.github.com/en/actions/how-tos/manage-runners/self-hosted-runners/apply-labels)
- [GitHub Actions billing](https://docs.github.com/en/billing/concepts/product-billing/github-actions)
- [Actions runner pricing](https://docs.github.com/en/billing/reference/actions-runner-pricing)
- [Actions limits](https://docs.github.com/en/actions/reference/limits)
- [GitHub-hosted runners reference](https://docs.github.com/en/actions/reference/runners/github-hosted-runners)
- [Runner labels (runners.io documentation)](https://www.runners.io/docs/runners/labels)
- [Security (runners.io documentation)](https://www.runners.io/docs/runners/security)
- [Limits (runners.io documentation)](https://www.runners.io/docs/runners/limits)

## Frequently asked questions

### What are managed GitHub Actions runners?

Runners a vendor operates for you. GitHub still schedules the job and runs your workflow, and you point a job at the vendor's machines by changing its runs-on label. The vendor patches, scales and bills the machines, between GitHub-hosted runners and self-hosted ones.

### How do managed runners differ from GitHub-hosted and self-hosted runners?

Who owns the machine and the bill. GitHub operates hosted runners and bills its per-minute rate; you operate self-hosted ones, which GitHub's billing lists as free; a vendor operates managed ones and bills its own rate under its own rounding rule.

### Do I have to change my workflows to use managed runners?

On runners.io, 1 line per job, the runs-on label, and a workflow can mix our labels with GitHub's because runs-on is set per job. actions/cache works unmodified. Ask any other vendor what it needs.

### Is a managed runner the same as a GitHub larger runner?

No. A larger runner is a GitHub-hosted runner with more cores, on GitHub Team and Enterprise Cloud, operated and billed by GitHub, including in public repositories. A managed runner is operated and billed by someone other than GitHub.
