Saltar al contenido principal
¡Hora del sombrero de negocios! Como se discutió en la sección de Economía de Gateway, los Gateways en Livepeer actualmente no ganan protocolo tarifas - por diseño.

Gateway Economics

Read about Gateway Economics Here
 En su lugar, los Gateways se encuentran en la capa de demanda, control y producto de la red Livepeer. No son solo enrutadores de servicios; también son donde realmente viven los negocios, productos, SLA, cumplimiento, y las relaciones con los clientes. Aquí es donde los clientes se conectan, se aplica la política, se modelan las cargas de trabajo y se construyen negocios reales.
Running a gateway is a strategic infrastructure decisionReasons include both technical and product needs.

​
Modelo mental del producto

Puertas de enlace
  • tener relaciones con clientes
  • controlar la entrada y la demanda
  • dar forma a la fiabilidad y la latencia
  • permitir cumplimiento y ventas corporativas
  • proporcionar diferenciación de producto
En cada mercado maduro de infraestructura (nube, CDN, pagos, telecomunicaciones), el plano de control y el borde capturan valor duradero incluso cuando la ejecución se convierte en un commodity (es decir, por los Orchestrators en el caso de Livepeer). Si los orchestrators son “fábricas”, los gateways son los puertos, oficinas de aduanas y empresas de logística.

​
¿Por qué ejecutar un Gateway?

A continuación se presentan algunas de las razones por las que podrías decidir ejecutar un Livepeer Gateway - agrupadas en categorías claras de negocio y técnicas.
Change to Cards?

​
1) Direct Usage & Platform Integration

Reasons related to using a gateway as part of your own product or operations.
  • Run your own workloads – Process your own video or AI content end-to-end with full control over ingestion, routing, retries, and delivery.
  • Ensure SLAs on orchestrators – Enforce latency, availability, retries, and failover through explicit orchestrator selection and routing logic.
  • Embed in a larger platform – Use the gateway as internal infrastructure powering a broader media or AI product rather than exposing protocol primitives.

​
2) Economics & Monetization

Reasons related to where money is made or saved.
  • Service-layer monetization – Charge end users more than orchestrator cost for reliability, compliance, convenience, or performance guarantees.
  • Avoid third-party gateway fees – Eliminate routing fees, pricing risk, and policy constraints imposed by another gateway operator.

​
3) Demand Control & Traffic Ownership

Reasons related to owning and shaping demand.
  • Demand aggregation & traffic ownership – Own ingress, customer relationships, usage data, and traffic predictability across apps or customers.
  • Workload normalization – Smooth bursty demand into predictable, orchestrator-friendly workloads.

​
4) Reliability, Performance & QoS

Reasons related to making the system work in real production environments.
  • QoS enforcement & workload shaping – Control routing, retries, failover, and latency vs cost trade-offs beyond protocol defaults.
  • Geographic request steering – Route users to regionally optimal orchestrators to reduce latency and improve reliability.

​
5) Security & Compliance

Reasons related to enterprise and production requirements.
  • Enterprise policy enforcement – IP allowlists, audit logs, authentication, rate limits, and deterministic behavior.
  • Cost-explosion & abuse protection – Prevent buggy or malicious clients from generating runaway compute costs.

​
6) Product Differentiation & UX

Reasons related to building differentiated products on top of the protocol.
  • Product differentiation above the protocol – Custom APIs, SDKs, dashboards, billing abstractions, and AI workflow presets live at the gateway layer.
  • Stable API surface – Shield customers from protocol or orchestrator churn with versioning and controlled change.

​
7) Observability & Feedback Loops

Reasons related to seeing and improving the system over time.
  • Analytics & feedback loops – Visibility into request patterns, failures, latency distributions, model performance, and customer behavior.

​
8) Strategy, Optionality & Ecosystem Power

Reasons related to long-term leverage and positioning.
  • Strategic independence – Avoid pricing, roadmap, availability, or censorship risk from other gateway operators.
  • Future optionality – Early positioning if gateway incentives or economics evolve in the future.
  • Ecosystem influence – Gateways shape standards, surface protocol gaps, and influence real-world usage patterns.
Last modified on March 1, 2026