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.

Streamplace is a Livepeer Special Purpose Entity (SPE) building open-source decentralised video infrastructure for social networks, livestreaming platforms, and Web3-native apps. It routes video ingest and processing through Livepeer’s network, signs every segment with C2PA and Ethereum provenance, and ships an SDK that drops into AT Protocol applications. This page exists to route you to the canonical Streamplace documentation. The setup, node install, SDK reference, and integration guides are maintained by the Streamplace team in the .

​
Integration Scenarios

Streamplace solves three integration scenarios that the lower-level Livepeer primitives leave open.
ScenarioWhat Streamplace adds
Bluesky or AT Protocol app needing live videoA node + SDK that emits AT Protocol-compatible video metadata
Decentralised social platform needing provenanceC2PA signing and Ethereum attestation on every video segment
Web3 app needing censorship-resistant streamingSelf-hostable node with Livepeer network transcoding
The integration path is a Streamplace node plus the SDK package documented by the Streamplace team. The node handles ingest, segmentation, provenance signing, and transcoding dispatch to Livepeer; the SDK gives your app a typed client and a React player component.

​
Streamplace and Livepeer

Streamplace runs production BYOC workloads on the Livepeer network. The relationship is:
LayerComponent
ApplicationYour AT Protocol or Web3 app
Video APIStreamplace SDK, StreamplacePlayer React component
NodeStreamplace node binary (ingest, provenance, dispatch)
NetworkLivepeer gateway and orchestrator pool
ComputeBYOC containers running on Livepeer orchestrators
The Streamplace node is the boundary between your application and the Livepeer network. Most developers integrate at the SDK layer and let the node handle the network plumbing. Operators self-host the node for full control; managed deployments use the Streamplace-operated node infrastructure. For context on BYOC as the underlying compute mechanism, see BYOC Overview. For the AI Jobs API path without the AT Protocol layer, see AI Jobs Direct Quickstart.

​
Canonical Setup Path

The canonical setup, including node install, SDK quickstart, metadata schema, and integration examples, lives in the Solutions tab.

Streamplace Overview

Start here: node install, SDK quickstart, provenance configuration, player integration. Maintained by the Streamplace team.
The Solutions overview covers the four steps that get a working integration:
  1. Install the Streamplace node binary
  2. Configure metadata, rights, and distribution policy
  3. Start a livestream via the CLI or SDK
  4. Embed the StreamplacePlayer component with provenance display
Time to first stream is under fifteen minutes following the canonical guide.

​
External Resources

ResourceLink
Streamplace homepagestream.place
Streamplace documentationdocs.stream.place
Streamplace repositorygit.stream.place
Streamplace GitHub mirrorgithub.com/streamplace/streamplace
Streamplace DiscordAvailable via the Solutions overview
For deep technical questions about Streamplace internals, the architecture and provenance documentation at docs.stream.place is the authoritative source. The Streamplace team maintains it directly. Your Streamplace BYOC container is running on the network. The same container pattern works for any Python model; swap the inference logic inside process_frame() and redeploy.

​
AI agent prompt

Build the "Streamplace BYOC Integration" tutorial by following the current Streamplace documentation as the source of truth. Verify the install path from https://stream.place/docs and the active repository metadata from https://github.com/streamplace/streamplace before choosing package names. Create a minimal TypeScript app that connects to a Streamplace node, starts or references a livestream, embeds the Streamplace player component documented upstream, and records the Livepeer/BYOC relationship in comments. Use placeholders for STREAMPLACE_NODE_URL=<node URL>, STREAMPLACE_AUTH_TOKEN=<token if required>, and LIVEPEER_GATEWAY_URL=<gateway URL if required>. Do not assume @streamplace/sdk is published to npm unless the package check succeeds; if it is unavailable, install exactly as the Streamplace docs prescribe.

​
Next Steps

Streamplace Overview

Canonical Streamplace documentation: install, SDK, integration patterns.

BYOC Overview

The general BYOC mechanism Streamplace builds on.

Low-Latency Streaming

Generic WHIP/WHEP path without the AT Protocol layer.

VOD Upload and Playback

Persistent video assets through the Livepeer Asset API.
Last modified on May 19, 2026