Skip to main content

Most developer tasks (calling AI pipelines, uploading assets, testing playback) require only an API key or a gateway endpoint. A full local Livepeer stack is necessary when developing node software, testing custom BYOC containers against a real orchestrator, or working through payment flows without spending real ETH.

Choosing a Development Path

Community Gateway (No Setup)

The public community gateway at https://dream-gateway.livepeer.cloud accepts unauthenticated AI inference requests for development. It routes requests to active mainnet orchestrators; no account or deposit is required.
This is appropriate for prototyping and initial integration testing. For sustained development load, run a local gateway to avoid rate limiting.

Installing go-livepeer

Download a pre-built binary from the go-livepeer releases page:
macOS (Apple Silicon):
After installation, verify with livepeer --version and livepeer_cli --version. Most developers start with the community gateway and never need local infrastructure. If you do need it, local gateway is the next step.

Local Gateway

Running a go-livepeer broadcaster node locally connected to mainnet.

Local Orchestrator

Running a local orchestrator for testing BYOC containers and payment flows.

Tooling and Metrics

Prometheus metrics and the livepeer/monitor container for local node observation.
Last modified on May 19, 2026