Managing self-hosted runners

You can host your own runners and customize the environment used to run jobs in your GitHub Actions workflows.

Your self-hosted runners can communicate with GitHub

The following processor architectures and operating systems are supported for the self-hosted runner application.

There are some limits on GitHub Actions usage when using self-hosted runners. These limits are subject to change.

You can add a self-hosted runner to a repository, an organization, or an enterprise.

You can automatically scale your self-hosted runners in response to webhook events.

Scripts can automatically execute on a self-hosted runner, directly before or after a job.

You can customize how your self-hosted runner invokes a container for a job.

You can configure the self-hosted runner application as a service to automatically start the runner application when the machine starts.

You can configure self-hosted runners to use a proxy server to communicate with GitHub.

You can use labels to organize your self-hosted runners based on their characteristics.

To use self-hosted runners in a workflow, you can use labels or groups to specify the runner for a job.

You can use policies to limit access to self-hosted runners that have been added to an organization.

You can monitor your self-hosted runners to view their activity and diagnose common issues.

You can permanently remove a self-hosted runner from a repository or organization.