Your player keeps working
HLS / DASH, ABR, DRM, decoding, and rendering stay in your existing playback stack.
Media delivery infrastructure
P2P CDN for live and on-demand video
MeshStream adds peer-assisted video delivery so viewers of the same content can share downloaded media segments and reduce repeated CDN downloads. Keep your existing player and CDN, with automatic CDN fallback whenever sharing is unavailable.
Keep your playerAutomatic CDN fallbackWeb + native SDKs
How sharing worksOne download, more viewers
Downloaded segments sharedRepeated CDN downloads reducedPlayback continues
Viewer sharingCDN delivery
Measured by bytesSee peer delivery and CDN fallback separately for every workload.
4 SDKsWeb, Android, Apple, and Windows.
HLS / DASHPlus direct MP4 and MP3 playback paths on the Web.
CDN fallbackPlayback stays on your existing CDN whenever sharing cannot help.
BANDWIDTH EFFICIENCY
Measured from delivery data
Measure peer-delivered and CDN-delivered bytes separately, then calculate the offload achieved by your actual audience, content, and network conditions.
Measure CDN offload and cost →COST ESTIMATOR
Estimate the CDN spend you could reduce
Use your traffic, measured offload rate, and CDN unit price to model a 30-day period.
Estimated monthly CDN spend reduction¥3,000
- CDN spend without P2P
- ¥6,000
- Remaining CDN spend
- ¥3,000
No player changes needed
The SDK handles sessions, segment requests, peer selection, caching, and fallback. Your player continues to own HLS, DASH, ABR, DRM, decoding, and rendering.
Web · TypeScriptTypeScript
import { attach } from "@meshstream/p2p-web";
const session = attach({
key: "your_sdk_key",
url: "https://cdn.example.com/video.m3u8",
video: document.querySelector("video")!,
});
await session.start();
// End of playback
session.dispose();The request layer gets a policy
The SDK chooses segment sources, peers, cache behavior, and fallback inside the playback session.
Roll out by application
Control enablement by key, platform, region, and version, then narrow the rollout quickly when needed.
One policy for Web and native clients.
Each platform keeps its own player and lifecycle, while application, key, region, and analytics conventions stay aligned.
Web
Integrationattach()
PlaybackHLS / DASH
TelemetrySession + diagnostics
Android
Integrationsession.playbackUrl
PlaybackHLS / DASH
TelemetryEvents + statistics
iOS / macOS
Integrationsession.playbackUrl
PlaybackAVPlayer / HLS
TelemetrySession + statistics
Windows
Integrationsession.playbackUrl
PlaybackHLS / DASH
TelemetrySession + fallback
Acceleration may fail. Playback should not.
P2P is an enhancement path with clear boundaries. When it is unavailable, MeshStream converges back to CDN delivery.
Automatic fallback
No peer, timeout, authorization issue, or service interruption should stop the player from using your CDN path.
Credential isolation
Origin headers stay on your controlled origin path and are never forwarded to other devices.
Operational controls
Disable P2P locally, by policy, or at runtime for staged rollouts, drills, and fast mitigation.
Verifiable acceptance
Validate normal playback first, then disable P2P and confirm the player completes through CDN delivery.
Every session has a traceable delivery path.
Use delivery evidence to investigate failures, measure impact, and decide what to change next.
SESSION / example● LIVE
Playback URLvod.example.com / episode-12
Delivery pathP2P → CDN fallback
Available viewers8 sharing this content
Fallback reasonPeer buffer below 2s
SDK platformWeb
By application and keySeparate environments, products, and release batches in usage and hit-rate reports.
By platform and regionFind connection quality issues tied to a device family, network, or geography.
By event and reasonTurn fallback, authorization, tracker, and peer errors into traceable events.
Built for VOD, live, and multi-platform delivery.
Measure video delivery cost
Measure peer and CDN bytes for your actual audience. Evaluate offload alongside playback quality and your billing terms.
Read the cost measurement guide →Stay steady at peak
Use distributed sharing to absorb bursts during events, launches, and live programming while keeping CDN fallback.
Explore live P2P CDN →Operate from one view
Cover four SDKs from one application perspective and compare versions, regions, usage, and failures.
Browse analytics →Start with one playback URL
Validate a delivery path in five minutes.
Integrate the Web SDK, then inspect the first session in the console.
Contact
Questions about integration or capacity? Reach us directly.
Telegram for quick answers, email for integration, quota, and billing.