Overview
Network
Peers supplement an underlying CDN or in-house streaming system. Viewer participation and concurrency affect the benefit; peer devices are not fixed cache PoPs.
No owned cache-city map is appropriate for this architecture. Test a replacement with the actual audience, player and fallback delivery network.
Past features
The historical player supported live and on-demand HLS/DASH playback and encrypted HLS or DRM-protected DASH streams. For a complete video workflow, check how encoding, packaging and DRM licenses will be supplied.
The 2015 hybrid mode targeted geographically concentrated, highly concurrent live viewing. It was not recommended for ordinary low-concurrency VOD. Measure bandwidth savings in a pilot and check the CDN’s own purge and request-log options.
Service status
History timeline
- October 21, 2015 — Hybrid player mode announced — P2P layer supplements an existing CDN or in-house streaming system.
- 2020–2022 — Later public repository activity — SDK/tool updates do not establish service continuity or closure.
Budgeting for a replacement
The historical hybrid mode required a subscription. Ask about current availability and prices before using it. Compare a replacement’s software fees separately from its underlying CDN bill.
- Estimate concurrency and the actual peer offload rate.
- Include fallback transfer, requests and media processing.
- Confirm supported players, licensing, support and commitments.
A guaranteed offload percentage would make the estimate misleading; use measured workload assumptions.
Historical integrations
The linked public documentation repository covers historical PDN architecture, the customer portal, REST API and Wowza integration. The organization also retains iOS/Android SDKs and HLS/DASH utilities.
Check current endpoint, SDK and browser support before reusing the archived tools. Check dependency support, credentials, media/DRM handling and CDN fallback before reusing them.