Skip to main content
This is the canonical quickstart for running a transcoding orchestrator.

Step 1: Create and fund your ETH account

You need an Arbitrum One ETH account for on-chain Livepeer operation.
1

Create a keystore

Use go-livepeer to initialize a keystore path:
./livepeer -network arbitrum-one-mainnet -ethKeystorePath ~/.lpData/keystore
Store your keystore and passphrase securely.
Never commit keystore files or passphrase files to version control.
2

Fund your account on Arbitrum One

Add ETH to your account for gas and ticket payments.

Step 2: Prerequisites

Step 3: Configure and run

Use this compose template as a baseline and replace placeholders.
If you are running CPU-only transcoding, remove GPU-specific runtime settings.
Start the node:

Step 4: Register as an orchestrator

Step 5: Verify your node

Your orchestrator should appear in the Livepeer Explorer.

Testing end-to-end with a Gateway

Once both services are running, verify an end-to-end transcoding session.

Gateway Quickstart

Use this to run gateway-side setup and stream validation.

Orchestrator Job Types

Compare transcoding, realtime AI, and batch AI paths.

Install go-livepeer

Full install options and advanced flags.

Connect to Arbitrum

RPC selection and network connection guidance.

CLI flags reference

Full orchestrator flag reference.
Last modified on April 7, 2026