The Livepeer Gateway ecosystem is active and growing. This page is a living directory of commercial products, community tools, and infrastructure projects built on Livepeer Gateways - demonstrating what operators and developers are building on the network today.
For the full directory of public Gateway operators with badges and status, see .
Daydream
What it is: An AI video creation platform for creators and builders. Daydream lets users apply AI models to live video streams with low-latency style transfer, motion effects, and generative overlays.
Gateway role: Daydream runs its own AI gateway to route inference jobs to Livepeer AI workers. The gateway handles model selection, pricing, and result delivery. Daydream’s developers work directly with the Livepeer Foundation and are active contributors to the remote signer architecture.
Livepeer Studio
What it is: A developer API and dashboard for video streaming and video-on-demand. Livepeer Studio provides SDKs, an API, and a web console for video workflows - live streaming, transcoding, clip storage, analytics.
Gateway role: Livepeer Studio operates a video gateway that routes RTMP transcoding jobs to orchestrators. Developers who use the Studio API are paying Studio’s service margin; Studio pays orchestrators on their behalf.
- Website: livepeer.studio
- Studio powers video workflows for games, social apps, creator tools, and live event platforms
Livepeer Cloud (Cloud SPE)
What it is: A public gateway service operated by the Livepeer Cloud SPE - a treasury-funded Special Purpose Entity focused on ecosystem adoption. Cloud provides free RTMP and AI inference gateways for developers evaluating Livepeer.
Gateway role: Livepeer Cloud operates multiple public gateways: a video transcoding gateway (RTMP) and an AI inference gateway. These are intentionally accessible without setup cost to drive developer onboarding.
Embody Avatars
What it is: An AI avatar and digital human platform. Embody uses Livepeer AI inference for real-time avatar animation and video generation.
Gateway role: Runs AI inference jobs through Livepeer gateway infrastructure.
What it is: An in-development clearinghouse reference implementation. NaaP (Network as a Platform) provides JWT-based authentication, Developer API Keys, and per-user usage tracking on top of a Livepeer gateway.
What it enables: Multi-tenant gateway access - you operate a gateway, issue API keys to developers, track their usage, and handle billing. Developers never interact with Ethereum or Livepeer contracts directly.
For a deep-dive on the NaaP architecture, see NaaP & Multi-Tenancy.
livepeer-python-gateway (j0sh)
What it is: A Python implementation of the Livepeer gateway client. Enables AI/ML engineers to route Livepeer inference jobs natively from Python without running a Go binary.
What it enables: Python-native gateway integration for ML pipelines, Jupyter notebooks, and Python web applications. Uses the remote signer architecture to handle ETH payments without requiring a Go gateway binary.
What it is: A publicly hosted remote signer endpoint maintained by community operator Elite Encoder. Provides a free ETH signing service for off-chain gateway operators who do not want to manage their own Ethereum infrastructure.
What it enables: Any developer can run an off-chain gateway without holding any ETH, by pointing at this community signer.
- Endpoint:
https://signer.eliteencoder.net/
- Cost: Free (as of community Discord confirmation)
What it is: A community dashboard for monitoring the Livepeer AI network. Shows active orchestrators, their capabilities, pricing, and performance metrics.
What it enables: Gateway operators can use this to identify and filter orchestrators for their workloads, check current market pricing, and monitor network-wide AI capacity.
livepeer.tools was previously the community monitoring site but is currently showing an nginx default page. The active tool is tools.livepeer.cloud.
Owncast integration
What it is: Owncast is an open-source, self-hosted live streaming platform. It supports RTMP input from OBS and other encoders, and can route transcoding through a Livepeer gateway.
What it enables: Self-hosted streamers can use Livepeer for transcoding without cloud provider costs. Owncast + Livepeer gateway is a common setup in the self-hosted streaming community.
- Owncast: owncast.online
- Livepeer + Owncast integration: documented on livepeer.cloud blog
Foundation programmes for builders
AI Video Startup Programme
The Livepeer Foundation runs a programme for startups and teams building AI-powered video products on Livepeer. Accepted teams receive network resources, technical support, and investor introductions.
If you are building a product that routes AI inference through Livepeer (and running a gateway is the operational model), this programme is specifically for you.
SPE (Special Purpose Entity) grants
Multiple gateway operators are funded through treasury proposals to the Livepeer governance process. The pattern is:
- Identify a gap in gateway capacity, capability, or adoption
- Write a proposal describing the work, timeline, and requested budget
- Submit to Livepeer governance for token holder vote
- Execute and report on milestones
Funded SPEs in the gateway operator space include Livepeer Cloud SPE (public gateways), LLM SPE (LLM inference routing), and NaaP (Network as a Platform).
Forum proposals and active SPE discussions: forum.livepeer.org
For the full SPE grant process, see SPE & Grant Models.
| Channel | What it’s for |
|---|
#local-gateways Discord | Primary channel for gateway operators. Remote signer, off-chain mode, SDK development, operational questions. Foundation engineers active. |
#gateway Discord | Secondary gateway channel. Common errors, community workarounds. |
| Livepeer Forum | Long-form questions, SPE proposals, governance. |
| go-livepeer GitHub | Source code, issues, PRs. File issues here for confirmed bugs. |
Video tutorials
Community tutorials and video content will be added here as they are identified. If you have created a tutorial or walkthrough for running a Livepeer gateway, share it in the #local-gateways Discord channel for consideration.
Next steps
