instruction: How do you implement autoscaling for GitHub Actions self-hosted runners?
output: Self-hosted runners - GitHub Docs Skip to main content GitHub Docs Version: Free, Pro, &amp; Team Search or ask Copilot Search or ask Copilot Select language: current language is English Search or ask Copilot Search or ask Copilot Open menu Open Sidebar GitHub Actions / Concepts / Runners / Self-hosted runners Home GitHub Actions Get started Quickstart Understand GitHub Actions Continuous integration Continuous deployment Actions vs Apps Concepts Workflows and actions Workflows Variables Contexts Expressions Reusable workflows Custom actions Deployment environments Concurrency Workflow artifacts Dependency caching Notifications for workflow runs Runners GitHub-hosted runners Larger runners Self-hosted runners Private networking Runner groups Runner scale sets Actions Runner Controller Support for ARC Security Secrets GITHUB_TOKEN OpenID Connect Artifact attestations Script injections Compromised runners Kubernetes admissions controller Metrics Billing and usage How-tos Write workflows Use workflow templates Choose when workflows run Trigger a workflow Control jobs with conditions Control workflow concurrency Choose where workflows run Choose the runner for a job Run jobs in a container Choose what workflows do Use jobs Find and customize actions Use GitHub CLI Add scripts Use secrets Use variables Pass job outputs Set default values for jobs Deploy to environment Run job variations Reuse automations Reuse workflows Create workflow templates Share across private repositories Share with your organization Secure your work Use artifact attestations Use artifact attestations Increase security rating Enforce artifact attestations Verify attestations offline Manage attestations Security harden deployments OIDC in AWS OIDC in Azure OIDC in Google Cloud Platform OIDC in HashiCorp Vault OIDC in JFrog OIDC in PyPI OIDC in cloud providers OIDC with reusable workflows Deploy Configure and manage deployments Control deployments View deployment history Manage environments Review deployments Create custom protection rules Configure custom protection rules Deploy to third-party platforms Node.js to Azure App Service Python to Azure App Service Java to Azure App Service .NET to Azure App Service PHP to Azure App Service Docker to Azure App Service Azure Static Web App Azure Kubernetes Service Amazon Elastic Container Service Google Kubernetes Engine Sign Xcode applications Create and publish actions Manage custom actions Create a CLI action Set exit codes Publish in GitHub Marketplace Release and maintain actions Manage workflow runs Manually run a workflow Re-run workflows and jobs Cancel a workflow run Disable and enable workflows Skip workflow runs Delete a workflow run Download workflow artifacts Remove workflow artifacts Manage caches Approve runs from forks Manage runners GitHub-hosted runners Use GitHub-hosted runners Customize runners View current jobs Connect to a private network Connect with OIDC Connect with WireGuard Self-hosted runners Add runners Run scripts Customize containers Configure the application Use proxy servers Apply labels Use in a workflow Manage access Monitor and troubleshoot Remove runners Larger runners Manage larger runners Control access Use larger runners Monitor workflows Use the visualization graph View workflow run history View job execution time Add a status badge Use workflow run logs Enable debug logging Troubleshoot workflows Administer View metrics Get support Reference Workflows and actions Workflow syntax Events that trigger workflows Workflow commands Variables Expressions Contexts Deployments and environments Dependency caching Reusable workflows Metadata syntax Workflow cancellation Dockerfile support Runners GitHub-hosted runners Larger runners Self-hosted runners Security Secure use Secrets OIDC Limits GitHub Actions Importer Supplemental arguments and settings Custom transformers Tutorials Create an example workflow Build and test code Go Java with Ant Java with Gradle Java with Maven .NET Node.js PowerShell Python Ruby Rust Swift Xamarin apps Authenticate with GITHUB_TOKEN Create actions Create a JavaScript action Create a composite action Publish packages Publish Docker images Publish Java packages with Gradle Publish Java packages with Maven Publish Node.js packages Manage your work Add labels to issues Close inactive issues Add comments with labels Schedule issue creation Store and share data Use containerized services Create a Docker container action Use Docker service containers Create PostgreSQL service containers Create Redis service containers Migrate to GitHub Actions Automated migrations Use GitHub Actions Importer Azure DevOps migration Bamboo migration Bitbucket Pipelines migration CircleCI migration GitLab migration Jenkins migration Travis CI migration Manual migrations Migrate from Azure Pipelines Migrate from CircleCI Migrate from GitLab CI/CD Migrate from Jenkins Migrate from Travis CI Use Actions Runner Controller Quickstart Authenticate to the API Deploy runner scale sets Use ARC in a workflow Troubleshoot GitHub Actions / Concepts / Runners / Self-hosted runners Self-hosted runners You can host your own runners and customize the environment used to run jobs in your GitHub Actions workflows. A self-hosted runner is a system that you deploy and manage to execute jobs from GitHub Actions on GitHub. Self-hosted runners: 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. Are free to use with GitHub 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. 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 Disabling or limiting GitHub Actions for your organization . Finally, enterprise-level runners can be assigned to multiple organizations in an enterprise account. Next steps To set up a self-hosted runner in your workspace, see Adding self-hosted runners . To find information about the requirements and supported software and hardware for self-hosted runners, see Self-hosted runners reference . Help and support Get quick answers! Ask Copilot your question. Ask Copilot Did you find what you needed? Yes No Privacy policy Help us make these docs great! All GitHub docs are open source. See something that&#x27;s wrong or unclear? Submit a pull request. Make a contribution Learn how to contribute Still need help? Ask the GitHub community Contact support Legal © 2025 GitHub, Inc. Terms Privacy Status Pricing Expert services Blog