MeshedFlow
Preparing route
MeshedFlow
Live-event delivery infrastructure

MeshedFlow turns live audiences into delivery capacity.

Verified viewer-to-viewer delivery reduces duplicate CDN bandwidth while your CDN remains armed for every miss, fault, or policy decision.

Watch the route

The CDN tax appears when everyone watches together.

Sports, premieres, and watch parties ask your CDN to deliver the same media again and again; MeshedFlow routes eligible repeats through the audience first.

CDN-only model 25 PB
With warm sharing 8 PB

Illustrative dense-event model. Your pilot measures the real value on your traffic.

Your player stays boring. The network gets smarter.

MeshedFlow checks peer eligibility, verifies media, and falls back to CDN immediately whenever sharing is not the right path.

Viewer
MeshedFlow
Policy
Viewers
CDN
REQ
SHARE
CDN
FIND
CHECK
VIEWER FOUND
CDN BACKUP
PLAYING
Waiting to start

Prove the number before you change the rollout.

Run one dense stream as control versus treatment, monitor playback quality, then decide from a report your finance and engineering teams can both trust.

  1. 01Pick the streamChoose one match, premiere, or watch party with concentrated concurrency.
  2. 02Run the treatmentMeasure CDN bytes, peer bytes, fallback rate, and playback health.
  3. 03Read the reportGet before/after economics, risk notes, and rollout guidance.

Two ways in. One measured report.

MeshedFlow detects the stream shape during onboarding, prepares origin validation when eligible, and keeps standard CDN-backed delivery in place when it is not.

Standard HLS offload Fast pilot on the current stream.

Signed-media acceleration Auto-prepared when the stream is eligible.

Metric Standard HLS offload Signed-media acceleration
Measured offload Measured in the pilot before rollout Measured after stream eligibility is confirmed
Playback quality delta Control versus treatment report Control versus treatment report
Safety boundary CDN fallback intact Rights exchange untouched
Production-scale performance Measured in pilot before expansion Requires origin validation and pilot report

The system has already been pushed past demo scale.

Big numbers first: browser rows show real media offload, service rows show scale, and your pilot proves the money on your stream.

256latest real browser observe-vs-score row represented 256 peers with 0 failed media requests and 0 crashes
85.00%observe-mode offload in the latest 256-browser decision row; production remains in observe
77.43%score-mode total offload in the same row; useful canary signal, but not the production default
1024large real browser E2E row represented 1024 peers with 0 failed media requests and 0 telemetry failures
69.37%score-mode offload at 1024 browsers from the high-density offload matrix; historical canary proof only
61.68%observe-mode offload at 1024 browsers; production remains in observe
79.79%score-mode offload at 512 browsers, with 0 failed media requests
32low-density E2E timing proof: score reached 70.01% offload, 0.107s join-after-WSS-open p95, and 0 failed media
300Ksessions passed in the hosted scale test
375K ceiling300K operating row keeps roughly 25% instance headroom
pilot-onlycustomer savings, rollout scope, and production claims wait for the measured pilot report
Real browser tier Observe Score Boundary
256 browser E2E 85.00% 77.43% Latest production confirmation, failed media 0; observe kept for production
512 browser E2E 63.45% 79.79% Score final, observe snapshot
1024 browser E2E 61.68% 69.37% Snapshot evidence, failed media 0
32 timing E2E 59.02% offload 70.01% offload Score canary proof; 0.107s join-after-WSS-open p95

Pricing follows verified bandwidth you stop buying.

Start without an upfront license; expand only when the pilot shows lower CDN spend, acceptable playback health, and a rollback path you control.

Free measured pilot One stream, control versus treatment, full report.

Results-based expansion Commercials tied to verified offloaded %.

Operational control Per-stream policy, upload caps, and remote kill switch.

pricing

The short answers before procurement and architecture review.

The pilot is designed to answer the expensive questions with your own traffic rather than a generic benchmark.

Will viewers notice anything?

No. MeshedFlow runs behind the player. If sharing is unavailable or unsafe, the CDN path is used immediately.

How much can we save?

It depends on concurrency, geography, bitrate, and event shape. The pilot measures real offloaded bytes and playback quality.

What happens if a peer is malicious?

Only verified media is accepted. Anything suspicious is rejected and the request falls back to your CDN.

Does this replace rights management or packaging?

No. Your packaging workflow remains unchanged. MeshedFlow is a delivery layer, not a rights-management layer.

How long does a pilot usually take?

Most pilots are scoped around one event, channel, or replay window. The goal is to compare treatment traffic against a clean CDN baseline without turning the project into a migration.

Who needs to be involved?

Streaming engineer means the technical expert who understands encoding, delivery architecture, and how content reaches viewers. Needed because they can judge whether the pilot is measuring real delivery behavior.

Player release owner means the product lead or developer responsible for updates to the video player users interact with. Needed because MeshedFlow enters through the player release path.

Procurement means the purchasing or finance team responsible for contracts and billing. Needed only after the pilot is complete and the measured offload results are ready, because the commercial model is tied to verified offload percentage rather than a generic seat license.

Can we limit the rollout?

Yes. You can constrain the pilot by stream, geography, device class, traffic percentage, or event window, with a rollback path back to normal CDN delivery.

What do we get at the end?

A measured report that shows eligible traffic, offload percentage, playback quality, fallback volume, and the commercial case for expanding or stopping.

The integration is a Shaka networking decision, not a player rewrite.

The ProofOfConcept demo keeps account access and rights exchange on your normal path, then routes only eligible segment requests through MeshedFlow.

HLS.js Drop in a shared loader core without rebuilding your playback stack.

Policy Start observe-only, then enable sharing stream by stream.

Integrity Verify media and fall back to CDN on misses or risk signals.

Operations Remote config, upload caps, telemetry, and kill switch.