---
title: "Runners"
url: https://docs.catalyst.zoho.com/en/pipelines/help/catalyst-pipelines.yaml/build-the-pipeline/runners/
description: "Learn about the Catalyst Pipelines runners in detail, the associated keywords and sample code snippets."
last_updated: 2025-05-30T11:24:59Z
service: Pipelines
type: general
related_links:
  - name: "Configure the Pipeline"
    url: /en/pipelines/help/catalyst-pipelines.yaml/implementation
---

# Build the Pipeline

In this section we will be discussing about the various pipeline components in detail, their usage in the `catalyst-pipelines.yaml` file, how to incorporate these components directly from the Catalyst console and build a Catalyst pipeline. Let us get started!

# Runners

## Introduction

A runner is an agent or computing resource that executes the jobs defined in a pipeline. Catalyst runners offer a robust and flexible infrastructure for efficiently and reliably building, testing, and deploying software applications.
You can define the required runners for the pipeline as key-value pairs using the `runners` keyword. 

The runner configurations supported by Catalyst Pipelines are listed below:

<table class="content-table">
        <thead>
            <tr>
                <th>Runner config</th>
                <th>RAM Storage</th>
                <th>CPU Capacity</th>
                <th>Disk Space</th>
            </tr>
        </thead>
        <tbody>
            <tr>
                <td>`Low`</td>
                <td>1 GB</td>
                <td>0.8 vCPU</td>
                <td>2 GB</td>
            </tr>
            <tr>
                <td>`Medium`</td>
                <td>2 GB</td>
                <td>1.2 vCPU</td>
                <td>4 GB</td>
            </tr>
            <tr>
                <td>`High`</td>
                <td>4 GB</td>
                <td>2.0 vCPU</td>
                <td>8 GB</td>
            </tr>
            </tbody>
</table>

> **Note:**

1. Defining a runner is not mandatory. If a runner is not specified, the `medium` config runner is taken by default to execute the jobs. 
2. You can define runners at the pipeline level, stage level, or job level. In case of multiple definitions, the one specified at the lowest level (i.e., job) takes precedence. 

### Properties of a Runner 

<table class="content-table">
        <thead>
            <tr>
                <th>Key</th>
                <th>Value</th>
                <th>is Mandatory</th>
            </tr>
        </thead>
        <tbody>
            <tr>
                <td>Runner name (The runner variable name used to access the runner)</td>
                <td></td>
                <td>Yes</td>
            </tr>
            <tr>
                <td>`config-id`</td>
                <td>The ID of the required runner configuration. 
                    `Low` = `config-id` : 1

                    `Medium` = `config-id` :2

                    `High` = `config-id` : 3
                </td>
                <td>Yes</td>
            </tr>
            </tbody>
</table>

### YAML Code Snippet for Runner 

```yaml
runners:
  runner1:
    config-id: 2
  runner2:
    config-id: 3

```

### Global Configuration 

You can also define the runners at the pipeline level, if required. This runner configuration will be accessible to all the stages and jobs. You can configure a runner at the pipeline level as follows:

```yaml
pipeline-runner:runner1
```