Skip to main content

Overview

MeshStream is a P2P media acceleration platform for video, live, and audio workloads. It integrates through an SDK and adds an additional delivery path for reusable media segments without replacing the existing player, origin, or CDN.

Product positioning​

Popular content can generate a large volume of identical media requests within a short period. MeshStream allows eligible viewers to reuse media segments that have already been downloaded, reducing concentrated CDN bandwidth pressure. P2P is a controllable enhancement path; the CDN remains the stable playback path.

MeshStream does not change the ownership or control boundaries of the existing stack: the player continues to handle manifest parsing, ABR, decoding, and rendering; the origin continues to authorize media; and the CDN continues to provide the complete availability path.

Playback session model​

Integration flow

Create an independent session for every playback:

  1. The application passes the original media URL and SDK Key to the SDK.
  2. The SDK creates a playback session and returns the session playback URL.
  3. The application loads that URL in its existing player.
  4. The application releases the session when playback ends, content changes, or the page is destroyed.

The SDK selects an available delivery path based on content identity, network conditions, and service policy. When acceleration is unavailable, the player can continue through the existing CDN path.

Integration boundaries​

  • The player remains in control: The SDK does not take over ABR, decoding, rendering, or DRM.
  • One model across platforms: Web, Android, iOS, and Windows integrations use the same Key, content identity, and reporting model.
  • Media formats: The application player parses HLS and DASH. MP4/MP3 direct-file acceleration depends on platform capabilities, the Web Service Worker, and origin Range support.
  • Authorization stays with the origin: Signed URLs, Cookies, Authorization headers, origin headers, and DRM remain the responsibility of the application's media service. Origin credentials are not sent to other viewers.
  • Failure isolation: Configuration, network, or acceleration errors must not stop the player. Application code should not treat an unavailable acceleration path as a media playback failure.

Usage and observability​

The SDK asynchronously records session state, P2P delivery, CDN delivery, peer counts, and diagnostic reasons. The console aggregates these records by application, Key, platform, and content.

MeshStream quota is charged only for P2P download bytes. When P2P is not selected, playback can continue through the application's CDN; that CDN traffic is used for effectiveness and diagnostics and is not charged against MeshStream P2P quota.

  • Live, on-demand, event, and sports content with repeated viewing;
  • Services that need to reduce CDN peak bandwidth or hot-content origin pressure;
  • Teams that want to introduce P2P gradually while retaining their current player and CDN.
  1. Quickstart: create a Key, integrate one playback, and verify the delivery path.
  2. Choose your SDK: follow Installation and setup → Quick integration → Advanced usage for your platform.
  3. P2P delivery model and Best practices for content identity, lifecycle, and rollout validation.