title

intro

redirect_from

versions

contentType

topics

Self-hosted runners

You can host your own runners and customize the environment used to run jobs in your {% data variables.product.prodname_actions %} workflows.

/github/automating-your-workflow-with-github-actions/about-self-hosted-runners

/actions/automating-your-workflow-with-github-actions/about-self-hosted-runners

/actions/hosting-your-own-runners/about-self-hosted-runners

/actions/hosting-your-own-runners/managing-self-hosted-runners/about-self-hosted-runners

/actions/concepts/runners/about-self-hosted-runners

/actions/hosting-your-own-runners

fpt	ghes	ghec
*	*	*

concepts

CI

CD

A self-hosted runner is a system that you deploy and manage to execute jobs from {% data variables.product.prodname_actions %} on {% data variables.product.github %}.

Self-hosted runners:

{% ifversion fpt or ghec %}

Give you more control of hardware, operating system, and software tools than {% data variables.product.prodname_dotcom %}-hosted runners provide. Be aware that you are responsible for updating the operating system and all other software.{% endif %}
Are free to use with {% data variables.product.prodname_actions %}, but you are responsible for the cost of maintaining your runner machines.
Let you create custom hardware configurations that meet your needs with processing power or memory to run larger jobs, install software available on your local network.
Receive automatic updates for the self-hosted runner application only, though you may disable automatic updates of the runner.
Can use cloud services or local machines that you already pay for.
Don't need to have a clean instance for every job execution.{% ifversion ghec or ghes %}
Can be organized into groups to restrict access to specific workflows, organizations, and repositories. See AUTOTITLE.{% endif %}
Can be physical, virtual, in a container, on-premises, or in a cloud.

You can use self-hosted runners anywhere in the management hierarchy. Repository-level runners are dedicated to a single repository, while organization-level runners can process jobs for multiple repositories in an organization. Organization owners can choose which repositories are allowed to create repository-level self-hosted runners. See AUTOTITLE. Finally, enterprise-level runners can be assigned to multiple organizations in an enterprise account.

Next steps

{% ifversion ghec or ghes %} To get hands-on experience with the policies and usage of self-hosted runners, see AUTOTITLE {% else %} To set up a self-hosted runner in your workspace, see AUTOTITLE. {% endif %}

To find information about the requirements and supported software and hardware for self-hosted runners, see AUTOTITLE.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!