Skip to main content
Livepeer offers multiple paths for developers depending on how you want to engage with the network. Whether you’re bringing compute workloads, consuming existing AI pipelines, or contributing to the core Go implementation, there’s a clear path for you.

​
Pick Your Path

Workload Provider

Bring your own compute workloads to the Livepeer network by running a gateway or interacting with smart contracts directly.

Workload Consumer

Consume existing pipeline workloads running on the Livepeer network — no infrastructure setup required.

Core Contributor

Contribute directly to go-livepeer, the Go implementation that powers the Livepeer network.

​
Path 1: Workload Provider

As a Workload Provider, you bring compute workloads to the Livepeer network. You define what gets processed — whether that’s an AI inference pipeline, a video transcoding job, or something entirely custom — and route it through Livepeer’s orchestrator network. There are two approaches depending on your needs.

​
Option A: Traditional Route (Gateway + BYOC)

The standard path runs your own gateway and uses BYOC (Bring Your Own Container) sidecar containers alongside the go-livepeer main container.

Run your own gateway

Set up a Livepeer gateway node that routes workloads to orchestrators on the network.

Gateway Quickstart

Get your gateway node running in minutes.

Engineer your BYOC containers

Build sidecar containers that run alongside the go-livepeer main container. BYOC lets you define custom workloads that orchestrators execute on their GPUs.

BYOC Documentation

Learn how to build and deploy BYOC sidecar containers.

Deploy workloads through your gateway

Once your gateway is running and your BYOC containers are built, deploy your workloads to the network through your gateway.

AI Pipelines Overview

Understand the full AI pipeline architecture.

​
Option B: Custom Smart Contract Interaction

If you want more control, you can interact with Livepeer’s smart contracts directly — bypassing the standard gateway flow to build custom orchestration logic.

livepeer-ops

Infrastructure tooling for deploying and managing Livepeer workloads with custom smart contract interactions.

Embody Pipeline

A reference implementation showing how to build a custom pipeline that interacts with Livepeer contracts directly.
You’re not limited to these two options. Providers can fork livepeer-ops, extend the Embody pipeline, or build entirely custom implementations. The smart contract interface is open — use it however fits your architecture.

​
Path 2: Workload Consumer

As a Workload Consumer, you use existing pipeline workloads that are already running on the Livepeer network. You don’t need to set up infrastructure or deploy containers — you connect to available pipelines and consume their output.

​
Available Pipelines

Daydream (DaS Scope)

Consume Daydream pipeline workloads on the Livepeer network.
Link coming soon

Embody Pipeline

Consume Embody pipeline workloads for real-time avatar and VTuber applications.
Link coming soon

​
Path 3: Core Contributor

As a Core Contributor, you work directly on go-livepeer — the Go implementation that powers gateways, orchestrators, and the protocol itself. This path is for developers who want to improve the network at the infrastructure level.

go-livepeer

The official Go implementation of the Livepeer protocol. Clone the repo and start exploring.

Contribution Guide

Guidelines for contributing to Livepeer — coding standards, PR process, and how to get your changes merged.
Last modified on March 1, 2026