Skip to main content
Page is under construction.

Check the github issues for ways to contribute! Or provide your feedback in this quick form
Livepeer’s core protocol defines the conditions for the network to provide real-time video and AI compute services. The network is the execution layer. It is the actual running system of machines performing work to execute the product vision.
  • Gateways (broadcasters) submit jobs (video or AI) into the network from applications or services
  • Orchestrator nodes (stakers) process and compute the work, and
  • Delegators stake tokens to support governance and security of the network

​
Network Components

​
Node Types

The protocol implementation defines several node roles (not all are formal network actors) that cooperatively execute on the protocol to provide the desired network functions.
  • Broadcaster Node: Centers on LivepeerServer managing rtmpConnections and BroadcastSessionsManager
  • Gateway Node: Adds AISessionManager and AI HTTP handlers on top of broadcaster functionality
  • Orchestrator Node: Uses the orchestrator struct with SegmentChans for job distribution and Recipient for payments
  • Transcoder Node: RemoteTranscoderManager coordinates local or remote transcoding via LocalTranscoder
  • AI Worker Node: RemoteAIWorkerManager manages Docker containers running AI models

​
Core Components

  • LivepeerNode: An interface node implemented by all other node types in the network (gateway/broadcaster, orchestrator, transcoder)
  • Media Server (LivpeerServer): The LivepeerServer manages media processing and serves HTTP/RTMP endpoints, providing
    • RTMP ingestion for live streams
    • HTTP push for video segments
    • HLS playback endpoints
    • Management of active connections
  • Broadcast Sessions Manager:
  • Orchestrator
  • Transcoder
  • AI Gateway
  • AI Workers
Last modified on February 18, 2026