> For the complete documentation index, see [llms.txt](https://docs.brainboard.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.brainboard.co/automation/self-hosted-runner.md).
# Self-Hosted Runner
{% hint style="warning" icon="info" %}
This feature is available in the **Enterprise Plan** only.
{% endhint %}
### Overview
**Brainboard**** Runner** is a service that runs all **CI/CD** jobs in your organisation and sends the results back to **Brainboard**. A **self-hosted runner** allows you to run your pipeline jobs in your own infrastructure.
A self-hosted runner created is **global** to your organization and will therefore process all jobs created within your organization, regardless of which project's architecture the jobs belong to, or which user created the job.
One organization can have multiple self-hosted runners, but these runners cannot be shared across multiple organizations.
{% hint style="success" %}
You can use **self-hosted runners** to run jobs in a **private network** or to customize the hardware and software configuration of the machines that run your jobs.
{% endhint %}
{% hint style="info" %} **Brainboard** self-hosted runner will need to be able to communicate with the **Brainboard**** API** to get job information and send the results, so your network needs to allow outbound traffic to the Brainboard API in order for the runner to communicate with Brainboard.
However, you do not need any specific ingress rule, because the **Brainboard**** API** does not communicate with the runner.
{% endhint %}
### Generate runner token
To use the **self-hosted runner**, you first have to generate a **runner token** from the **Brainboard** web application. To get the runner token, you have to be logged in with an account having organization's **`Admin`** or **`Owner`** permissions.
To generate the runner token:
1. Go to the [private self-hosted runner](https://app.brainboard.co/settings/integrations/private-selfhosted-runner?) settings page. On this page, you can create a new runner token or revoke an existing one.
2. Click on the **`New runner token`** button.
3. Click the **`Generate runner token`** button.
4. **Copy** the generated token and save it for the deployment step.
### Deploy self-hosted runner
You can deploy the self-hosted runner in your environment using two methods:
1. Docker-compose
2. Kubernetes