Performance P2P SDK

Rilla Broadcast-Grade Peer-Assisted Live-Sports Streaming

Intro Overview Capacity & Cost Problem Architecture Broadcast-Grade Core Features Scale Content Protection Latency Management Device Performance Demo: On Device Segment Aware Peer Groups Watermarking ABR Ad Insertion Observability Trial

Segment-level integrationRust runtimeMulti-platform rolloutPlayback and buffer awareIn-player orchestrationCDN fallback protection

Segment-level integration avoids player rewrites

Watch: Architecture

Rilla integrates where playback already requests media segments. The SDK evaluates eligible segment requests, applies Rilla delivery decisions, and leaves existing player, CDN, DRM, ABR, and manifest workflows in place.

This keeps adoption low-risk: POC validation can measure peer-assisted delivery without replacing the player stack or rebuilding delivery infrastructure.

Rust runtime keeps peer delivery lightweight

Watch: Device Performance Watch: Demo on device

Rilla uses a lightweight Rust runtime for the core peer-delivery logic, with platform wrappers exposing the SDK to each supported environment. The Web SDK is exposed as a TypeScript package for browser player integrations.

That architecture keeps performance-sensitive work close to the playback path while preserving native integration patterns for Web, Android, and future Apple SDKs.

Technical specifications: Peer SDK, Architecture.

Multi-platform rollout stays repeatable

Rilla uses one Peer SDK model per platform, then layers player-specific guides on top. The platform SDK carries the peer runtime, orchestration hooks, fallback behavior, and telemetry model; player guides show where that SDK attaches inside supported workflows.

This keeps rollout repeatable. A POC can prove one platform and one player first, then extend through the platform SDK model instead of creating a separate delivery implementation for every player.

Platform SDKs

Web / Browser SDK@rillanetwork/peer-sdk-web

Android SDKComing soon

Apple SDKComing soon

Player Guides

Bitmovin ReactWeb player guide

Shaka PlayerComing soon

ExoPlayerAndroid TV and mobile

View all player guides

Playback and buffer awareness protects QoE

Watch: Latency Management

The SDK evaluates each segment request against playback state, buffer health, and segment deadlines. Peer delivery is attempted only when timing allows; when peer retrieval risks buffer continuity, delivery stays on your CDN or falls back before playback is affected.

In practice the SDK intercepts each segment request, checks eligibility with the Orchestrator, uses peer delivery when conditions support it, and falls back to your CDN if playback deadlines are at risk. Telemetry is emitted throughout for observability, POC validation, and orchestration.

POC validation measures deflection against QoE guardrails such as startup time, rebuffer ratio, playback errors, and fallback behavior.

Technical specifications: Peer SDK core concepts, CDN Fallback, AI Orchestrator.

CDN fallback keeps playback protected

Rilla’s delivery flow is intentionally hybrid. Peer delivery adds eligible capacity when conditions support it, while CDN delivery remains available for fallback throughout playback.

1. Player requests a segment

   Playback remains the source of demand.

2. SDK evaluates the request

   The SDK checks eligibility, configuration, and delivery timing.

3. Orchestrator provides peer context

   Rilla uses telemetry and peer scoring to identify suitable paths.

4. Peer or CDN serves traffic

   Eligible traffic may use peer delivery; ineligible or risky traffic stays on your CDN.

5. Fallback protects playback

   CDN is used when peer delivery cannot meet playback deadlines.

Proving SDK performance in a POC

SDK validation includes integration behavior and playback outcomes. Rollout expands only after the SDK proves it can deliver deflection and telemetry without harming playback guardrails.

Area	What to validate
Player behavior	Startup time, rebuffering, playback errors, and compatibility with the selected player.
Runtime overhead	Package/runtime impact, parsing behavior, and any player-side performance concerns visible in the POC.
Delivery behavior	Peer/CDN routing, fallback rate, request eligibility, and bypass behavior.
Telemetry	Whether SDK telemetry reaches existing observability tools correctly.
Rollout controls	Feature flags, cohort control, region/content enablement, and kill-switch expectations.
Platform coverage	Whether the first platform proves the path for future Web, Android, or iOS rollout.

Technical specifications: Testing and Deployment, Observability and Monitoring.

Related (technical docs)

Peer SDK Platform overview for Rilla SDK documentation.

Peer SDK Web: Getting Started Technical setup for the Web / Browser SDK.

Player Integrations Supported player integration pathways by platform.

POC / Trial Guide Plan a controlled SDK rollout and validation path.

CDN Fallback How fallback protects playback when peer delivery is unsuitable.