Polyarhub runs origin-shield and segment-caching nodes that sit between your media storage and public CDN edges. Operators offload adaptive HLS and DASH traffic to us and stop paying for repeated origin fetches.
Explore the platform Talk to the NOCThree services, one control plane. Everything is delivered from our own hardware in carrier-neutral facilities — we do not resell public cloud capacity.
Origin shield for adaptive bitrate delivery. Segment requests from public CDN edges are collapsed into a single upstream fetch, so your storage sees one read per segment instead of one per edge.
Regional sync gateway for mobile applications: encrypted profile state, catalogue manifests and asset bundles replicated close to the subscriber.
S3-compatible object storage tuned for large sequential reads, with lifecycle rules for VOD libraries and archive tiers.
A typical adaptive-bitrate session touches four hops. Our nodes own the middle two.
| Hop | Component | Typical latency | Owner |
|---|---|---|---|
| 1 | Player → public CDN edge | 4–18 ms | CDN operator |
| 2 | Edge → Polyarhub origin shield | 6–25 ms | Polyarhub |
| 3 | Shield → customer storage (on miss) | 20–60 ms | Polyarhub |
| 4 | Storage → packager | varies | Customer |
Segment URLs frequently carry session or chunk identifiers. Our shield normalises the cache key per customer policy so that signed URLs do not fragment the cache.
Live manifests and low-latency segments hold connections open. Read timeouts are configured per resource rather than globally, so idle players are not disconnected mid-session.
Byte-range fetches are forwarded untouched, which keeps seek behaviour intact for large VOD assets and progressive downloads.
Every node is provisioned with headroom for the 95th percentile of its region plus one full failover share from a neighbouring PoP.
Live operational summary. Detailed per-node history is available to customers in the control panel.