Skip to main content
Page is under construction.

Check the github issues for ways to contribute! Or provide your feedback in this quick form
An orchestrator is a supply-side operator that contributes compute resources (predominately GPU resources) to the network. They receive jobs, perform transcoding or AI inference, and get compensated via LPT rewards + ETH fees.

Orchestrator Role

In the early days of Livepeer, orchestrators were solely responsible for transcoding video. Today, as the Livepeer network has evolved from a video streaming network to a real-time AI video network, the role of orchestrators has greatly expanded beyond “just transcoding” with it. Today’s orchestrators are general purpose GPU compute providers that transcode video, run AI inference pipelines and custom workloads, manage staking and rewards, vote in governance, and even host novel services like AI avatars and agent workloads. This multi-faceted responsibility makes them critical to Livepeer’s vision as a unified compute layer for real-time AI workloads as well as a key component of the network’s strategic roadmap and a core partner for novel production applications to be developed and deployed. See more: Orchestrator-Delegate Dual Role

Orchestrator Types

There are two main types of orchestrators on the Livepeer Network:
  • GPU nodes that perform video transcoding
  • AI nodes that perform AI inference
  • Custom workloads ie. BYOC pipelines or application-specific workloads
BYOC pipelines are a recent addition to the AI node type that allows AI nodes to run arbitrary containers for processing tasks on the Livepeer network.

Orchestrator Setup Options

Anyone with a GPU can monetise their compute resources on the Livepeer Network, whether you want to add your GPU to the network for passive income in idle times, or you want to run a full-fledged business. If you’re a hobbyist, the best place to start is by contributing your GPU to an Orchestrator pool. If you’re a data center or want to have full control over your node, you can setup your own Orchestrator node.
Last modified on February 18, 2026