> ## Documentation Index
> Fetch the complete documentation index at: https://docs.livepeer.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Setup Overview

> Default setup path for Livepeer orchestrators running go-livepeer, with redirects for pools and non-default deployment patterns.

This guide is the default setup path for operators who are running an Orchestrator on go-livepeer.

## What this guide does

* Walks through the default setup path most operators should use.
* Breaks setup into clear install, configure, connect, activate, test, and monitor steps.
* Links to the detailed current pages for each step.

## What this guide does not do

* It does not cover pool participation as the primary path.
* It does not replace the detailed AI operations guides.
* It does not cover every split, siphon, or custom deployment pattern in-line.

## Redirects

<CardGroup cols={2}>
  <Card title="Pool redirect" icon="users" href="/v2/orchestrators/guides/join-a-pool" arrow>
    Use this if you are contributing GPU capacity to an existing operator instead of setting up your own node.
  </Card>

  <Card title="Other setups" icon="shuffle" href="/v2/orchestrators/dep-rc-navigator" arrow>
    Use this for split, siphon, and other non-default setup paths that are still being consolidated.
  </Card>
</CardGroup>

## Setup overview

<CardGroup cols={2}>
  <Card title="Requirements" icon="microchip" href="/v2/orchestrators/setup/prepare" arrow>
    Confirm hardware, networking, and operational prerequisites.
  </Card>

  <Card title="Install" icon="download" href="/v2/orchestrators/setup/install" arrow>
    Install go-livepeer using the release path that matches your environment.
  </Card>

  <Card title="Configure" icon="sliders" href="/v2/orchestrators/setup/r-configure" arrow>
    Set the runtime flags that define price, GPU selection, network, and service address.
  </Card>

  <Card title="Connect" icon="plug" href="/v2/orchestrators/setup/sc-connect" arrow>
    Connect the node to Arbitrum and verify RPC reliability.
  </Card>

  <Card title="Test" icon="vial" href="/v2/orchestrators/setup/x-test" arrow>
    Validate the node before and after activation.
  </Card>

  <Card title="Monitor" icon="chart-line" href="/v2/orchestrators/setup/monitor" arrow>
    Track health, rewards, and operational signals once the node is live.
  </Card>
</CardGroup>

## Activation checks

Treat activation as a distinct checkpoint, not just the end of installation.

| Check                | Use this page                                                 |
| -------------------- | ------------------------------------------------------------- |
| Connect              | `/v2/orchestrators/setup/sc-connect`                          |
| Publish and activate | `/v2/orchestrators/unclassified/rcs-connect-activate-publish` |
| Verify               | `/v2/orchestrators/setup/x-test`                              |

<CardGroup cols={3}>
  <Card title="Connect" icon="plug" href="/v2/orchestrators/setup/sc-connect" arrow />

  <Card title="Publish" icon="satellite-dish" href="/v2/orchestrators/unclassified/rcs-connect-activate-publish" arrow />

  <Card title="Verify" icon="circle-check" href="/v2/orchestrators/setup/x-test" arrow />
</CardGroup>