Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.livepeer.org/llms.txt

Use this file to discover all available pages before exploring further.

A ComfyStream instance running locally or on a remote server can receive jobs from the Livepeer network by registering with an orchestrator as a BYOC (Bring Your Own Compute) container. Once registered, the orchestrator advertises the live-video-to-video capability to gateways, and incoming real-time AI jobs are forwarded to the ComfyStream service over the trickle protocol. This page assumes a ComfyStream instance is already running and accessible. See for installation and startup.

​
Requirements

  • A running go-livepeer orchestrator node
  • A ComfyStream instance accessible from the orchestrator over HTTP
  • The orchestrator’s aiModels.json configuration file
The orchestrator and ComfyStream can run on the same machine or on separate hosts provided the orchestrator can reach the ComfyStream HTTP port.

​
Registering with the Orchestrator

​
Dynamic Parameters

The trickle protocol supports sending parameter updates to a running pipeline without restarting the stream. The orchestrator proxies POST /live/video-to-video/update calls from the gateway to the ComfyStream service. ComfyStream passes these updates to the running workflow as ComfyUI node parameter overrides. This allows clients to change prompt text, ControlNet strength, sampler settings, or any other node value while the stream is active. The update request body is a JSON object mapping node IDs to parameter values. The exact schema depends on the workflow; refer to the workflow JSON for node IDs and parameter names.

​
Remote Deployments

For ComfyStream running on a separate GPU server, the orchestrator must be able to reach the ComfyStream HTTP port. Common setups include:
  • Same host: http://127.0.0.1:8188
  • LAN: http://<local-ip>:8188
  • Cloud with Cloudflare Tunnel: use the Cloudflare Tunnel URL as the url value in aiModels.json
The trickle protocol transmits video segments over HTTP. No UDP ports are required for the orchestrator-to-ComfyStream path; UDP is only needed for the WebRTC path between the end client and the gateway. Your ComfyStream instance is now a registered BYOC capability on the network. Gateways route live-video-to-video jobs to it via the AI Service Registry.

Workflow Authoring

Building and starting a ComfyStream instance with a ComfyUI workflow.

BYOC Overview

The general BYOC container interface that ComfyStream implements.

Real-Time AI Overview

Cascade architecture and the full request flow through gateway and orchestrator.

PyTrickle Overview

Python SDK alternative for custom processing logic without ComfyUI.
Last modified on May 19, 2026