{"meta":{"title":"Self-hosted runners","intro":"You can host your own runners and customize the environment used to run jobs in your GitHub Actions workflows.","product":"GitHub Actions","breadcrumbs":[{"href":"/en/actions","title":"GitHub Actions"},{"href":"/en/actions/concepts","title":"Concepts"},{"href":"/en/actions/concepts/runners","title":"Runners"},{"href":"/en/actions/concepts/runners/self-hosted-runners","title":"Self-hosted runners"}],"documentType":"article"},"body":"# Self-hosted runners\n\nYou can host your own runners and customize the environment used to run jobs in your GitHub Actions workflows.\n\nA self-hosted runner is a system that you deploy and manage to execute jobs from GitHub Actions on GitHub.\n\nSelf-hosted runners:\n\n* Give you more control of hardware, operating system, and software tools than GitHub-hosted runners provide. Be aware that you are responsible for updating the operating system and all other software.\n* Allow you to use machines and services that your company already maintains and pays to use.\n* Are free to use with GitHub Actions, but you are responsible for the cost of maintaining your runner machines.\n* 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.\n* Receive automatic updates for the self-hosted runner application only, though you may disable automatic updates of the runner.\n* Don't need to have a clean instance for every job execution.\n* Can be physical, virtual, in a container, on-premises, or in a cloud.\n\nYou 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 [Disabling or limiting GitHub Actions for your organization](/en/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization#limiting-the-use-of-self-hosted-runners). Finally, enterprise-level runners can be assigned to multiple organizations in an enterprise account.\n\n## Next steps\n\nTo set up a self-hosted runner in your workspace, see [Adding self-hosted runners](/en/actions/how-tos/manage-runners/self-hosted-runners/add-runners).\n\nTo find information about the requirements and supported software and hardware for self-hosted runners, see [Self-hosted runners reference](/en/actions/reference/runners/self-hosted-runners)."}