MESHEDFLOW
INITIALIZING CORE...
MeshedFlow logo MESHEDFLOW
// PILOT-READY P2P DELIVERY FOR HLS + SIGNED CMAF

MAKE YOUR CDN THE FALLBACK.

MeshedFlow turns dense audiences into a verified WebRTC delivery mesh. Your player still uses HLS.js, your origin still serves the first safe copy, and your CDN remains the instant fallback. The upside is simple: fewer duplicate segment downloads when viewers are watching together.

[ meshedflow@edge - /bin/mesh ]canary
meshedflow@edge:~$
[ /market - video delivery is still bandwidth-shaped ]

$ cat delivery_pressure.txt

DENSE AUDIENCES SHOULD COST LESS.

Traditional CDN delivery sends the same segment from the edge to every viewer. MeshedFlow adds a second path for the moments where density is on your side: viewers who already hold verified bytes can serve nearby viewers, while the CDN keeps playback safe whenever the mesh is not the fastest path.

80.0%average controlled Chrome offload in the current synthetic validation
100%warm-state offload after the two-segment cold start window
10+viewer pilot density where production offload measurement starts to mean something
[ /route - segment lifecycle ]

$ mesh trace --segment seg_04812.m4s

A HYBRID MESH, NEVER A BET.

  1. 01 INTERCEPT A shared HLS.js loader catches fragment requests and checks fresh buffer maps from connected peers on the same stream and rendition.
  2. 02 MATCH Rust/Tokio signaling edges pair viewers by stream, rendition, topology, and live registry presence, then route SDP/ICE across the edge cluster when needed.
  3. 03 VERIFY Segments and CMAF fragments are accepted only after origin-bound integrity checks; untrusted or unsigned data returns to trusted HTTP.
  4. 04 FALL BACK If a peer is missing, slow, capped, or unreachable, playback completes from your origin CDN without changing the player surface.
[ /system - man meshedflow.engine ]

$ man meshedflow.engine

BUILT LIKE DELIVERY INFRASTRUCTURE.

--shared-loader One mesh per player session, not one socket per fragment

HLS.js creates a loader instance per request, so MeshedFlow uses a SharedLoader pattern: playlists stay on the default loader, fragments share one MeshedFlow core, and ABR stats still flow back to HLS.js.

--rust-edge Rust/Tokio signaling edge

The high-scale data plane speaks the existing SDK JSON protocol while handling WebSocket admission, peer presence, same-stream routing guards, and cross-edge SDP/ICE delivery.

--valkey Shared rendezvous registry

Edges use TTL-backed Valkey/Redis presence so a peer can join one edge and still receive proposals or WebRTC control messages routed from another.

--cmaf Signed CMAF stream-and-forward

Origin-signed fragment manifests let peers advertise and serve verified moof+mdat fragments before a full segment finishes downloading. Rollout starts in advertise-only mode.

--rarest-first Chunk routing with CDN range rescue

Fresh buffer maps, peer throughput, latency, in-flight limits, topology score, and range rescue decide whether a chunk rides the mesh or returns to HTTP.

--policy Remote controls and viewer caps

Remote JSON policy can tune timeouts, peer counts, CMAF mode, upload caps, stream overrides, or kill the mesh for a stream without redeploying the player.

[ /install - hls.js integration ]

$ meshedflow init --player hls.js

DROP IT INTO A PILOT STREAM.

The current integration pattern keeps playlist loading on standard HTTP and routes media fragments through a shared MeshedFlow core. That gives the mesh one stable peer identity, one WebSocket, one cache, and clean HLS.js lifecycle behavior.

~/player.ts[copy]
// HLS.js creates one loader per fragment. Share one mesh core.
import Hls from 'hls.js';
import { MeshedFlowLoader } from '@meshedflow/sdk';

class SharedLoader {
  constructor() {
    if (!SharedLoader.core) {
      SharedLoader.core = new MeshedFlowLoader({
        signalingUrl: 'wss://meshedflow.com/ws',
        originBaseUrl: 'https://meshedflow.com',
        streamId: 'pilot-stream',
        peerId: 'viewer-' + crypto.randomUUID(),
        remoteConfigUrl: '/meshedflow-routing.json',
        enableRarestFirst: true,
        cmafMode: 'advertise-only',
      });
    }
    this.core = SharedLoader.core;
  }

  load(context, config, callbacks) {
    this.currentRequest = this.core.load(context, config, callbacks);
  }

  abort() {
    if (this.currentRequest) this.currentRequest.abort();
  }

  destroy() {}
}

const hls = new Hls({
  loader: SharedLoader,
  pLoader: Hls.DefaultConfig.loader,
});

hls.loadSource('https://your-origin.example/live.m3u8');
hls.attachMedia(videoElement);

MIT licensed SDK - HLS.js 1.5 peer dependency - Chrome 80+ - Firefox 76+ - Safari 14+ - Edge 80+

[ /proof - June 2026 verification snapshot ]

$ meshedflow bench --latest --good-news

THE CANARY HAS TEETH.

Current evidence is strongest where MeshedFlow is supposed to shine: controlled offload validation, signed CMAF fragment flow, and high-density signaling. The public story should lead with those strengths and invite each customer pilot to validate its own traffic shape.

80.0%average synthetic real-Chrome offload, 5/5 validation runs passed
682CMAF P2P hits in a 30-minute 4-peer restart soak
50Kpublic HAProxy L4/TLS WSS peers through one ingress with clean generators
150Kactive direct Rust WS peers across four edges on the 4GiB canary
CMAF SOAKclean integrity checks, 0 full CDN rescues, 4.1 MB heap growth
RUST EDGEp95 join 33 ms on public direct Rust-WSS at 7,500 peers
INGRESSsingle public WSS endpoint on :8445 validated through 50,000 peers
[ /pricing - success-aligned pilots ]

$ meshedflow billing --explain

PAY FOR BANDWIDTH YOU NO LONGER BUY.

Start with a measured pilot on one stream or one event class. The cleanest commercial model is tied to verified offloaded bytes: MeshedFlow earns when your CDN egress falls, and the pilot report shows the math before a wider rollout.

PILOTinstrument one stream, compare CDN-only control vs mesh-enabled treatment
METERbill on verified offloaded GB, not player starts or seats
ROLL OUTexpand by content type after offload, rebuffer, and playback-error gates pass

$ meshedflow deploy --pilot-stream

ROUTE THE FIRST VERIFIED SEGMENT.

Pick a dense stream, enable telemetry, start in advertise-only mode for CMAF, then let the dashboard prove exactly how many bytes the audience can carry for itself.