> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-discovery-discovery/api-security-testing/ast-basics-and-workflow/runners-and-cli.md).

# Runners and CLI

Compare Traceable CLI and runners, and choose an installation method for runners that execute application security testing scans

<details>

<summary>Updates (October 2026 to December 2026)</summary>

* *November 2026:* Updated the page to add the endpoints that the Traceable CLI and runners connect to, along with their ports, protocols, and purposes. For more information, see [Network requirements](#network-requirements).

</details>

Runners are nothing but Traceable CLI installed on your server as a service. They form the execution backbone of application security testing by enabling scans to run within your infrastructure and communicate results back to the Traceable platform.

## Traceable CLI versus runner

The following table compares Traceable CLI and runner on various parameters, along with their use case and recommendations:

| Parameters     | Traceable CLI                                                                                                                                                 | Traceable Runner                                                                                                                                                                                                                                                                                             |
| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Integration    | It is designed to integrate with CI systems, allowing jobs to be triggered and run on a CI runner. It is a quick way to run scans from local or remote hosts. | It is designed to integrate with job schedulers and CI/CD systems, allowing the CI pipeline to trigger the scan and delegate the actual running to the Traceable runner.                                                                                                                                     |
| Execution      | It executes synchronously, running tests immediately as they are invoked.                                                                                     | It executes asynchronously, consuming the job queue.                                                                                                                                                                                                                                                         |
| Configuration  | It is usually a part of the script setup.                                                                                                                     | It requires a runner pool, which is typically set up using Helm charts or similar deployment tools.                                                                                                                                                                                                          |
| Use Case       | It is ideal for pre-commit hooks, pre-deploy checks, and other stages in the development pipeline where immediate feedback is required.                       | It is ideal for scheduling regular security scans, batch jobs, or handling multiple requests asynchronously.                                                                                                                                                                                                 |
| Recommendation | It is recommended for use in small to medium-sized projects that require immediate results on simple security tests.                                          | <p>It is recommended for use in either of the following scenarios:</p><ul><li>When working with large projects requiring complex security testing, most attack coverage and tests run for longer durations.</li><li>When you want to run periodic exhaustive tests as daily/weekly scheduled jobs.</li></ul> |

***

## Network requirements

The Traceable CLI and runners make outbound connections to the endpoints in the following table. You need to allow these connections through your firewall or proxy before you install the CLI or a runner.

<table><thead><tr><th width="180.4210205078125">Endpoint</th><th width="57.8619384765625">Port</th><th width="166.8497314453125">Protocol</th><th width="132.41845703125">Required</th><th>Purpose</th></tr></thead><tbody><tr><td><code>api.traceable.ai</code></td><td>443</td><td>gRPC over TLS (HTTP/2)</td><td>Always</td><td>This endpoint is used for runner management, scan operations, and telemetry.</td></tr><tr><td><code>api.traceable.ai</code></td><td>443</td><td>HTTPS (HTTP/1.1)</td><td>Always</td><td>This endpoint is used for uploading and downloading API specifications and Postman collections.</td></tr><tr><td><code>app.collab.tr4t.io</code></td><td>443</td><td>HTTPS</td><td>Always</td><td>This endpoint is used for the collaborator channel during active scans. The collaborator is a Traceable-controlled server that receives callbacks from the target application to detect vulnerabilities that do not produce observable HTTP responses.</td></tr><tr><td><code>s3.amazonaws.com</code></td><td>443</td><td>HTTPS</td><td>Always</td><td>This endpoint is used for the CLI version check at startup.</td></tr><tr><td><code>8.8.8.8</code></td><td>53</td><td>TCP</td><td>Always</td><td>This endpoint is used for the internet connectivity probe at startup, with no data exchanged.</td></tr><tr><td><code>dl-cli.pstmn.io</code></td><td>443</td><td>HTTPS</td><td>Postman integration only</td><td>This endpoint downloads the Postman CLI binary.</td></tr></tbody></table>

{% hint style="info" %}
The domains that you allow depend on the cluster that hosts your Traceable account:

* Use the domain of your cluster, for example `app.us1.traceable.ai`, instead of `api.traceable.ai` so that the CLI or runner connects to the cluster that hosts your account.
* For the EU region, use `eu.collab.tr4t.io` together with `app.collab.tr4t.io` so that the collaborator channel works for scans that run in that region.
* For the APAC region, use `apac.collab.tr4t.io` together with `app.collab.tr4t.io` so that the collaborator channel works for scans that run in that region.
  {% endhint %}

Go to [CLI Pre-checks and Installation](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-discovery-discovery/api-security-testing/ast-basics-and-workflow/runners-and-cli/cli-pre-checks-and-installation.md) to verify that a host can reach the Traceable platform.

***

## Runner installation methods

You can download and install a runner using either of the following methods:

* Through the Traceable platform
* As a service using the `install.sh` script
* Using Helm chart
* On AWS ECS using CloudFormation or Terraform

However, before installing a runner, you must ensure that you have the necessary software and hardware requirements. Go to [Software and Hardware Requirements](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-discovery-discovery/api-security-testing/ast-basics-and-workflow/runners-and-cli/software-and-hardware-requirements.md) for details. Once you have the necessary requirements, you can install the runner. For the steps to do this, go to [Installing a Runner](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-discovery-discovery/api-security-testing/ast-basics-and-workflow/runners-and-cli/installing-a-runner.md).

Traceable also allows you to set up custom certificates for runners according to your requirements. Go to [Set up custom certificates for runners](https://developer.harness.io/web-application-and-api-protection-waap-discovery-discovery-discovery-discovery/api-security-testing/ast-basics-and-workflow/runners-and-cli/traceable-cli-config.md#set-up-custom-certificates-for-runners) for details.

{% @harness-feedback/feedback %}
