Livepeer Mental Model

Livepeer is a crypto‑economic coordination protocol that secures a global, on-demand GPU network optimized for low-latency video and AI, and exposed through developer‑friendly platforms and applications. You can think of Livepeer as a decentralised serverless GPU fabric with a cryptoeconomic control plane, where services are exposed through a set of developer-friendly products and applications. Livepeer is akin to how you would access and build on traditional cloud providers, for example, social media is powered by on an underlying infrastructure, which you access through a set of products and applications (e.g. Twitter, Instagram, Facebook). Livepeer’s crypto-economic primitives and decentralised compute mesh provide additional benefits to the system such as censorship resistance, economic security, and trustless coordination.

Infra Layers

Protocol

A crypto‑economic protocol that secures and coordinates the network. (incentives, staking, governance, payments)

the protocol provides trust, coordination and payment mechanisms

Livepeer Protocol

Network

A global GPU network that performs the actual compute work. (supply, routing, performance)

the network supplies compute, routing, and verification

Orchestrators Gateways

Applications and Platforms

A set of developer‑facing tools and applications (APIs, SDKs, apps) which expose the network’s capabilities in a usable way.

the platforms expose the network’s capabilities in a usable way.

Gateways Platforms

Livepeer as an OSI-Like Stack

One of the traditional ways to map infrastructure architectures is with the OSI model. While this model doesn’t map perfectly to decentralised systems - and is also being rapidly transformed by AI, the framework is still useful for understanding the different layers and how they interact. Livepeer can be roughly pictured as an OSI stack where the “cloud control plane” is replaced by a cryptoeconomic protocol, and persistent storage is optional, external, and secondary to real-time streamed compute.

Network & Protocol Stack

Think of this as the global decentralized open compute substrate.

Layer 1: Physical Compute & Resource Layer

“Raw atoms”

What it is:

GPUs, CPUs, memory, bandwidth
Heterogeneous hardware (consumer → data‑center grade)
Power, latency, geographic placement

Livepeer Context:

Hardware is contributed and owned by independent operators
Capacity is surfaced to the network via orchestrator infrastructure

Not Livepeer‑specific:

NVIDIA, AMD, bare metal, cloud VMs

Who provides it:

Orchestrators (GPU operators)
Gateways (in some cases - depending on deployment)

Livepeer does not own infrastructure. It indexes and incentivizes it.

Layer 2: Transport & Media Substrate

“Bits move”

What it is:

Video transport, chunking, codecs, streaming primitives
Frame-level + segment-level delivery
Peer discovery, routing, and delivery paths

Livepeer context:

Segment-based processing and delivery patterns
Low-latency media delivery is a core competence (“video DNA”)
Gateway-mediated delivery patterns (client/server hybrid)

Who provides it:

Gateways (as the primary network-facing media/API surface)
Orchestrators (as the execution endpoints)
Underlying Internet transport (TCP/UDP/HTTP/WebRTC etc.)

Key Idea:
This is where Livepeer differs from generic GPU clouds: it is built around media-native transport patterns.

Layer 3: Distributed Execution Network

“Who Actually does the work?”

What it is:

Distributed job routing + load balancing
Service discovery and selection
Capacity-aware and performance-aware execution selection

Livepeer context:

Orchestrator selection and routing mechanisms
Segment/task model: work can be broken into independently computable units
Execution endpoints expose pricing/fees and performance characteristics

Who provides it:

Orchestrators (provide execution + advertise capability)
Gateways / clients (initiate and route work via protocol/network rules)

Key Idea:
The network decides who executes; the protocol incentivizes honest participation.

Layer 4: Crypto-Economic Coordination Layer

“Coordination, Trust, Provenance”

What it is:

On‑chain logic that secures and coordinates the network
Cryptoeconomic primitives that align incentives
Work/role coordination, reputation signals, and network rules enforcement

Livepeer Context:

On-chain protocol + off-chain coordination patterns that:
- allow permissionless participation
- coordinate stake-weighted influence and selection
- align behavior with network goals

Who provides it:

Ethereum smart contracts (on Arbitrum L2)
Blockchain network (Arbitrum L2)
Network participants (orchestrators, delegators, gateways) operating under protocol rules

Key Idea:
This is the “brain” that replaces a centralized cloud control plane. It incentivizes correct behavior, but does not run jobs.

Layer 5: Economic & Security Layer

“Why anyone behaves” (incentives alignment, game theory)

What it is:

Cryptoeconomic primitives that align incentives
Game‑theoretic mechanisms that ensure correct behavior
Incentives for participation and penalties for misbehavior

Livepeer Context:

LPT staking + delegation
Inflation-based rewards (protocol issuance)
Fee capture and distribution (usage-based)
Slashing (where enabled) to penalize malicious/incorrect behavior
Governance processes (LIPs, voting, treasury stewardship)

Who provides it:

Protocol participants:
- Delegators (stake delegation / security backing)
- Orchestrators (service provision under stake)
- Governance participants (proposal + voting + stewardship)

Key Idea:
Security is achieved via economic incentives + cryptographic verification, not trust in a single operator.

Layer 6: Data & State Layer

“What persists”

What it is:

The data plane around jobs: segments, manifests, logs, receipts
Temporary + derived artifacts needed for execution and verification

Livepeer Context:

Livepeer is intentionally light on storage
Video segments and state are often ephemeral and pipeline-driven
Long-term storage is typically external (object stores, CDNs, decentralized storage)

What persists:

Video segments (temporary)
Manifests, logs, receipts
Verification metadata

Who provides it:

Broadcasters / application operators (sometimes own long-term storage)
External storage providers (S3, GCS, IPFS, Arweave, etc.)
Not the Livepeer chain

Key Idea:
Livepeer coordinates compute over data, not long-term data custody.

Platform and Application Stack

Layer 7: Platform Services

“Batteries included”

What it is:

Managed services that abstract protocol/network complexity and make it easy to build on Livepeer
Operational tooling: dashboards, analytics, key management, billing abstraction
Provides features such as stream management, analytics, key management, billing abstraction

Livepeer Context:

Hosted/managed gateway experiences
Templates, pipelines, and reference apps
Ecosystem-led products that package the network into a usable platform

Who provides it:

Livepeer ecosystem teams (Inc, Foundation-funded projects, community teams)
Gateway operators offering service layers on top

Key Idea:
This is where the network meets user needs. Products are opinions about access-they are not the protocol and not the network.

Examples:

Livepeer Studio
Streamplace
Daydream
and anyone who builds on top of the Livepeer protocol and network

See More Products & Platforms

Layer 8: Developer Interfaces

“How builders integrate”

What it is:

APIs, SDKs, client libraries, docs, example repos

Livepeer Context:

Gateway APIs
SDKs (JS, Python, etc.)
BYOC-style integrations (containerized apps connecting to the stack)

Who provides it:

Product teams and open-source contributors
Gateway implementations exposing consistent interfaces

Key Idea:
This layer collapses network/protocol complexity into stable developer primitives.

See the Showcase

Layer 9: Developer Applications

“What builders ship”

What it is:

End-user applications and services built on top of Livepeer
The final layer is where the end-user applications and services are built.
This is where the magic happens and is what most users will interact with.

Who provides it:

Independent developers, studios, ecosystem teams
Anyone who builds end-user applications on top of Livepeer or Livepeer Platform services

Examples: Decentralized Twitch alternatives, AI video apps, surveillance/vision pipelines, Metaverse/XR video. */}

Key Idea:
This is where the end-user applications and services are built. Applications are plural and replaceable; the network remains the substrate.

See the Showcase

Layer 10: End User

“Humans and (increasingly) AI Agents”

What it is:

Viewers, creators, AI consumers.

Livepeer Context:

Users typically never see
- orchestrators,
- staking/delegation,
- protocol mechanics.

Who provides it:

The applications and experiences (Layer 9)

Key Idea:
End users are the ultimate beneficiaries of the network, but they don’t need to know or care about the underlying technology. Success means protocol mechanics disappear behind great UX.

End users never see orchestrators, stakes, or protocol mechanics.

Middleware & Integrations

Livepeer replaces persistent storage coupling with streamed, ephemeral compute coordination.

The “joining layer” is: Protocol-level orchestration, segment-based streaming, economic guarantees.

Not Kafka. Not Airflow. Not Kubernetes. But conceptually: A decentralized serverless GPU fabric with a cryptoeconomic control plane.

About Livepeer

Core Concepts

Livepeer Protocol

Livepeer Network

Resources

The Livepeer Stack and Mental Model

Livepeer Mental Model

Infra Layers

Livepeer as an OSI-Like Stack

Network & Protocol Stack

Platform and Application Stack

Middleware & Integrations

About Livepeer

Core Concepts

Livepeer Protocol

Livepeer Network

Resources

​Livepeer Mental Model

​Infra Layers

​Livepeer as an OSI-Like Stack

​Network & Protocol Stack

​Platform and Application Stack

​Middleware & Integrations

Livepeer Mental Model

Infra Layers

Livepeer as an OSI-Like Stack

Network & Protocol Stack

Platform and Application Stack

Middleware & Integrations