How It Works

Hybrid CDN + Rilla Delivery (Simplified)

Loading diagram

1. Integrate the Peer SDK

   The Peer SDK sits between your player, your CDN, and eligible peers. It intercepts video segment requests so Rilla can decide when to use your CDN, when to use peer-assisted delivery, and when to fall back instantly.

   • Your player keeps requesting video from your CDN.
   • The SDK intercepts segment requests in the delivery path.
   • When peer delivery is not suitable, playback stays on your CDN.

2. Hybrid delivery enables P2P video

   For viewers with the SDK installed, Rilla enables both CDN and peer-assisted video delivery. Your CDN remains the reliable baseline, while peer delivery adds capacity when viewer and network conditions allow.

   • Peer-assisted delivery is used only when eligibility, timing, and policy allow.
   • Your authentication, entitlements, and access rules remain authoritative.
   • Rilla can interleave CDN and peer delivery during playback.

   The viewer experience does not change.

   Rilla adds P2P delivery without disrupting playback quality.

3. A Peer Network forms as viewers join

   As more viewers watch the same stream rendition, eligible viewers can become part of the delivery layer. This creates additional capacity from the live audience when conditions support it.

   • Each stream rendition can form its own peer network, such as HD or 4K.
   • Rilla uses your existing auth and entitlements; the SDK registers with the AI Orchestrator.
   • More concurrent viewers can create more delivery capacity.

4. AI Orchestration optimizes for capacity, cost, and quality

   The AI Orchestrator continuously controls which viewers can connect, share video, and organize into the optimal network topology. It optimizes delivery against cost, latency, and quality guardrails.

   • Rilla evaluates timing, suitability, network conditions, and guardrails.
   • Viewers only receive or relay encrypted video when approved.
   • Peer decisions optimize usable capacity and CDN load while protecting and enhancing playback quality.

5. CDN fallback protects playback continuity

   Peer delivery is only used when it supports the viewing experience. If peer delivery falls short, playback continues through your CDN while Rilla adapts.

   • Playback stays anchored to a CDN-capable path.
   • Load shifts back to your CDN when needed.
   • Peer delivery resumes when conditions improve.

6. CDN deflection measures offload

   Deflection is the percentage or volume of played video bytes delivered through Rilla rather than directly from your CDN infrastructure. Peak demand shows up as measurable offload, not only higher CDN-served traffic.

   • Rilla compares Rilla-enabled cohorts to CDN-only control groups using real playback traffic.
   • Deflection is measured alongside playback guardrails on CDN deflection and quality under load.

Summary

Rilla adds a controlled peer-assisted layer to your existing video delivery stack.

• Peer SDK: intercepts segment requests in the playback path.
• Hybrid delivery: uses your CDN, peer-assisted paths, or both.
• Peer Network: forms from eligible viewers as the audience joins.
• AI Orchestration: optimizes peer decisions for capacity, cost, and quality.
• CDN fallback: protects and enhances playback continuity.
• CDN deflection: measures played-byte offload versus CDN-only controls.