Polyarhub
Company

We keep origin traffic boring.

Polyarhub was founded in 2019 by a small group of network and video engineers who were tired of watching origin bills scale linearly with audience size. We build the unglamorous layer between storage and the edge.

How we work

Own hardware

Every node is our own equipment in a carrier-neutral facility. We do not resell public cloud capacity, which is why our pricing does not move when someone else changes their egress rates.

Small surface

One node image, one configuration language, one deployment path. Fewer moving parts means fewer ways for a change window to go wrong.

Engineers answer the phone

The NOC rota is staffed by the people who wrote the software. There is no first line whose job is to ask whether you have tried restarting.

Written postmortems

Any incident affecting customer traffic for more than five minutes gets a written analysis within five working days, published to affected customers.

Timeline

YearMilestone
2019Company registered in Vilnius. First StreamCache node in production for a regional broadcaster.
2020Riga and Warsaw PoPs. Request collapsing rewritten after a live sports event exposed a thundering-herd bug.
2021Frankfurt PoP and first DE-CIX sessions. MediaVault enters closed beta.
2023Amsterdam and Stockholm PoPs. EdgeSync released to general availability.
2025Per-resource timeout and cache policy engine replaces global configuration.
2026Capacity doubled in Frankfurt; Helsinki PoP in planning.

Compliance

Data processing

We act as a processor for customer traffic. Access logs are retained for 30 days and are not shared with third parties except where legally required.

Abuse handling

Reports are triaged within one business day. Confirmed abuse of a customer resource results in suspension of that resource, not the whole account.

Subprocessors

Facility operators and transit providers only. A current list is available on request under NDA.

Legal details