{"meta":{"title":"Larger runners","intro":"Organize and govern your workflows with GitHub-hosted larger runners using runner groups, concurrency policies, and granular access controls.","product":"GitHub Actions","breadcrumbs":[{"href":"/en/enterprise-server@3.19/actions","title":"GitHub Actions"},{"href":"/en/enterprise-server@3.19/actions/concepts","title":"Concepts"},{"href":"/en/enterprise-server@3.19/actions/concepts/runners","title":"Runners"},{"href":"/en/enterprise-server@3.19/actions/concepts/runners/larger-runners","title":"Larger runners"}],"documentType":"article"},"body":"# Larger runners\n\nOrganize and govern your workflows with GitHub-hosted larger runners using runner groups, concurrency policies, and granular access controls.\n\n> \\[!NOTE]\n> GitHub Enterprise Server users should use self-hosted runners. GitHub-hosted runners are **not** supported.\n\nTo learn about larger runners, see [the GitHub Enterprise Cloud documentation](/en/enterprise-cloud@latest/actions/concepts/runners/larger-runners)."}