Polyarhub
Platform

Three services, one control plane.

Every service runs on the same node image and the same routing fabric. You pick which of them terminates a hostname; the rest of the stack stays identical.

StreamCache

Origin shield for HLS and DASH. Deployed in front of your packager or object storage, behind one or more public CDN operators.

Request collapsing

Concurrent misses for the same segment are merged into a single upstream fetch. During a live event this is the difference between one origin read and several thousand.

Per-resource cache policy

Manifests, init segments and media segments get separate TTLs. Dynamic endpoints can be marked no-store so that a stale body is never replayed to a different session.

Origin failover

Two or more upstreams per resource with health checks and automatic demotion. Failover is per-resource, not per-node, so one broken bucket does not move all traffic.

Access control

Signed URL validation, referrer policy and per-resource IP allowlists. Rejections are counted separately from origin errors in the logs.

Typical resource definition:

FieldExampleNotes
Originhttps://origin.example.net:443TLS required, SNI must match
Segment path/media/hls/segment.tsMust match the packager output exactly
Connect timeout10 sApplies to the upstream handshake
Read timeout300 sRaise for low-latency live
Cacheno-store / max-agePer path prefix

EdgeSync

Regional gateway for mobile and desktop clients. Handles the chatty, small-payload part of an application so it never crosses the continent.

Profile state

Encrypted blobs replicated between PoPs with last-writer-wins and per-device conflict logs.

Catalogue manifests

Region-specific listings assembled once and served from memory until the upstream revision changes.

Asset bundles

Versioned static bundles with immutable URLs, pinned to the release channel the client reports.

MediaVault

S3-compatible storage for VOD libraries. Optimised for long sequential reads rather than small random access.

TierRedundancyFirst-byte latencyIntended use
Hot3 replicas, single region< 40 msActive catalogue
Warm2 replicas + parity< 120 msBack catalogue
ArchiveErasure codedminutesMasters, compliance copies

Limits and defaults

  • Maximum object size — 5 TB
  • Maximum concurrent streams per resource — unmetered
  • Default request body limit — unlimited on segment paths
  • Supported protocols — HTTP/1.1, HTTP/2, TLS 1.2 and 1.3
  • Log retention — 30 days hot, 12 months aggregated
  • Certificate management — customer supplied or ACME
  • IPv6 — enabled on all PoPs
  • Change window — Tue and Thu, 04:00–05:00 UTC