{"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/enterprise-server@3.17/actions","title":"GitHub Actions"},{"href":"/en/enterprise-server@3.17/actions/concepts","title":"Concepts"},{"href":"/en/enterprise-server@3.17/actions/concepts/runners","title":"Runners"},{"href":"/en/enterprise-server@3.17/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* 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 organized into groups to restrict access to specific workflows, organizations, and repositories. See [Managing access to self-hosted runners using groups](/en/enterprise-server@3.17/actions/how-tos/manage-runners/self-hosted-runners/manage-access).\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/enterprise-server@3.17/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 get hands-on experience with the policies and usage of self-hosted runners, see [Getting started with self-hosted runners for your enterprise](/en/enterprise-server@3.17/admin/managing-github-actions-for-your-enterprise/getting-started-with-github-actions-for-your-enterprise/getting-started-with-self-hosted-runners-for-your-enterprise)\n\nTo find information about the requirements and supported software and hardware for self-hosted runners, see [Self-hosted runners reference](/en/enterprise-server@3.17/actions/reference/runners/self-hosted-runners)."}