Each opted in user adds another possible path for approved public chunks.
Flareless browser demo
Route around CDN failure from your phone.
This static demo simulates timeout aware provider routing, HTTP failure handling, route scoped health, chunk scoped health, route policy decisions, peer assisted fallback, and optional origin fallback. Live viewer detection uses the Flareless Worker presence room when configured.
Demo request
Choose a static routing test
/video/show-name/episode-001/v17/720p/chunk-0001.ts
Routing result
IdleResponse headers
Run a scenario to see route explanation headers.
What is happening
Choose a static test above to see what Flareless is proving in that routing path.
Route policy model
Flareless routes are independent provider paths, and each route has an explicit policy. A route policy decides which providers are allowed, whether peer fallback is allowed, whether origin fallback is allowed, and whether a request should stop before origin.
Video routes allow peer fallback and block origin fallback. Private routes block both peer and origin fallback. Origin allowed routes skip peer fallback and allow origin fallback as a controlled last resort.
Peer assisted delivery
Every extra device makes the recovery path stronger.
When CDN routes break, Flareless can recover through a living mesh of approved public content. More users means more possible paths, more reach, and better resilience when the normal edge is having a bad day.
Flareless
Peer mesh
PhoneUser A
LaptopUser B
TabletUser C
DesktopUser D
PhoneUser E
Mini nodeUser F
NASUser G
BrowserUser H
If a CDN fails, traffic can try another CDN, then peer assisted delivery.
Some peers may later opt into a stronger micro CDN mode, where stable devices cache more approved public content and help carry heavier traffic when demand grows.