Skip to main content
Run a Livepeer Orchestrator when the earning path matches your hardware, stake access, and operating tolerance. The right answer is sometimes a pool worker, sometimes an AI-first node, and sometimes a full solo Orchestrator. Use this page to choose that path. It breaks the decision into costs, revenue streams, viability checks, and workload trade-offs so you can stop early, start with a lower-commitment path, or commit to a full Orchestrator. For the mechanics of how earnings work, see . To skip evaluation and proceed directly to setup, see the

​
What Orchestrators Earn

Orchestrators earn from two separate streams. You need to understand both before you can judge whether the path fits your hardware, stake, and time commitment. Running the software alone does not create either revenue stream. ETH fees depend on Gateways sending work. LPT rewards depend on stake, activation, and a node that calls Reward() reliably. For most new operators, LPT inflation is the more predictable starting point. Service fees can grow faster, but only after the node proves it can stay available, price sensibly, and handle work well.

​
Cost Categories

Revenue projections are only useful when the cost baseline is honest. The practical question is whether the earning path fits what you already own and what you are willing to keep paying for.
The primary upfront cost. Workload type determines the minimum GPU requirement.
  • Video transcoding only: Any NVIDIA GPU with NVENC/NVDEC support. Consumer RTX cards (3060, 3070, 3080) are common. CPU transcoding is possible at significantly lower throughput.
  • Batch AI inference: 8-24 GB VRAM depending on pipelines. An RTX 3090 (24 GB) is the practical minimum for competitive diffusion pipelines.
  • Cascade AI: 24 GB VRAM minimum. These pipelines are substantially more demanding than batch inference.
Hardware already owned has zero ongoing capital cost. Hardware purchased specifically to run Livepeer needs an explicit amortisation model: at £800 for an RTX 4090 and £30/month earnings, the hardware break-even alone is over two years before electricity.See for GPU tier specifications.
To receive video transcoding jobs as a solo Orchestrator, the node must be in the active set - the top Orchestrators by total bonded stake eligible to receive work each round.LPT must be acquired and bonded to the Orchestrator address. Borrowing LPT is not supported by the protocol. Acquiring enough LPT to compete in the active set is the primary entry barrier for solo video Orchestrators.Two alternatives exist if stake is limited:
  1. Join a pool as a worker - no LPT needed; the pool Orchestrator handles on-chain operations
  2. Run AI inference only - AI job routing prioritises capability and price over stake position
See the decision matrix below for the stake requirement by path.
The Orchestrator wallet needs ETH on Arbitrum One for ongoing transactions:
  • Reward() calls - once per round (~22 hours). Cost: approximately $0.01-0.12 per call at current Arbitrum gas prices.
  • Ticket redemptions - periodic, triggered when winning tickets accumulate. Cost: approximately $0.01-0.05 per redemption batch.
  • Activation transaction - one-time setup cost.
Gas on Arbitrum L2 stays relatively low, but operators still need an ETH budget. Budget approximately $5-15/month in ETH for a mid-volume node. A depleted ETH wallet causes missed reward rounds (LPT permanently foregone) and unredeemed winning tickets (ETH fees permanently lost).
Video transcoding is bandwidth-intensive. Each concurrent stream requires approximately:
  • ~6 Mbps download (source stream ingestion)
  • ~5.6 Mbps upload (output renditions: 240p, 360p, 480p, 720p)
A 1 Gbps symmetric connection supports approximately 100+ concurrent streams on bandwidth alone. For home operators with 100-500 Mbps connections, bandwidth often constrains session count before hardware does.AI inference has a much lighter bandwidth profile per job. It is a single image or audio input with a result response, not a continuous stream.
GPU power draw is the primary ongoing operating cost. It varies significantly by GPU tier:An RTX 4090 running 24/7 at full load costs approximately £30-60/month at UK residential electricity rates, or $35-70/month at US average rates. Factor this into any break-even calculation.
Orchestrator operation is not fully passive. Realistic time commitments:
  • Initial setup and configuration: 4-16 hours (varies by path)
  • Monitoring and maintenance: 1-3 hours per week once stable
  • Troubleshooting: variable
  • go-livepeer updates: 30-60 minutes per release
Pool workers have minimal ongoing time investment once the worker process is configured. Solo Orchestrators require consistent monitoring, particularly for reward call reliability and response to Gateway selection issues.

​
Three Viability Questions

These three questions are the fastest way to rule a path in or out before you spend more time on setup. A clear failure in one question usually identifies the wrong operating model immediately.

​
1. Is reward calling profitable?

Calling Reward() costs gas. If stake is small, the LPT earned per round may be worth less than the gas cost. A rough check: open explorer.livepeer.org and find the Orchestrator’s “Estimated Reward This Round.” If that LPT value (converted to ETH at the current price) is less than approximately 0.00005 ETH, the gas cost exceeds the reward at typical Arbitrum rates. In that case, start with manual reward calling until stake grows. This threshold shifts with LPT price, ETH price, and inflation rate. See for the detailed calculation methodology.

​
2. Can the node compete on pricing and capability?

For video transcoding: Gateways filter Orchestrators by stake position and price. If -pricePerUnit is above a Gateway’s -maxPricePerUnit, that Gateway sends no jobs regardless of hardware. For AI inference: Gateways filter first by capability (is the requested pipeline and model available?) then by price. Stake matters less here. A well-configured AI node with warm models loaded can compete from day one without active set membership. Current competitive pricing is visible at explorer.livepeer.org/orchestrators - sorting by fee volume reveals what pricing levels active earners use.

​
3. Is the setup stable enough?

Missing reward rounds results in permanent LPT loss - that round’s rewards are not recoverable. Receiving jobs that cannot be completed damages performance reputation with Gateways and reduces future job flow. Both outcomes require reliable operation. Production-grade infrastructure is optional at this stage, but consistent uptime and monitoring are required. Home setups with unreliable internet, frequent power cuts, or machines shared with other workloads carry material viability risk. When sustained ~95%+ uptime is unrealistic, the pool worker path is more appropriate than solo Orchestrator operation.

​
Decision Matrix

Use the matrix below as a path filter. Profitability still depends on current network conditions, but the matrix shows which model fits your hardware, stake access, and operating capacity. The pool worker path has a significantly lower barrier than solo Orchestrator operation. For operators new to Livepeer with a GPU but limited LPT, starting as a pool worker builds network familiarity without on-chain complexity. Migration to solo operation is possible once stake is acquired.

​
Video vs AI: Starting Workload

Operators with 24 GB+ GPUs often face a more important first choice than “should I run Livepeer?” - “should I start with video, AI, or both?” The two paths have different entry barriers, different revenue patterns, and different operating burdens. AI inference lowers the stake barrier and keeps the operating burden high. Demand shifts between pipelines, cold models waste time and money, and weak VRAM planning can erase the advantage of starting without active-set stake. Check tools.livepeer.cloud/ai/network-capabilities to see which pipelines and models are currently routed by the network before deciding which to load.

​
Research Tools

Check the live market before committing to setup:

Hardware Requirements

GPU tiers, NVENC session limits, VRAM requirements per AI pipeline, and production hardware checklist.

The Commercial Case

What commercial Orchestrator operation looks like - service fees, SLAs, and serving application workloads.

Earnings Explained

Full mechanics of how ETH fees and LPT rewards flow, including reward call thresholds.

Navigator

Ready to commit? Choose the right setup path for your hardware and goals.
Last modified on March 16, 2026