Media gateway infrastructure
for teams that ship video.
Arcline operates a managed origin and edge layer for streaming platforms, broadcasters and internal video systems. Segment delivery, adaptive manifests and origin shielding, without the operational overhead of running your own fleet.
What the platform does
A single origin endpoint in front of your storage, with the delivery mechanics handled for you.
Adaptive segment delivery
HLS and DASH manifests are rewritten at the edge so players receive the closest available rendition without client-side logic.
Origin shielding
Requests collapse at the gateway tier, so a cache miss storm reaches your storage as a single upstream fetch rather than thousands.
Signed access
Time-bounded URL signing and referrer policies are enforced before a byte leaves the edge, with per-path override rules.
Transparent health
Every node exposes a machine-readable health endpoint, so your own monitoring can poll the gateway directly instead of guessing.
Range-aware caching
Byte-range requests are served from partial objects, which keeps seek-heavy viewing patterns off the origin entirely.
Structured logs
Delivery logs ship in newline-delimited JSON with request identifiers that correlate across the gateway and your own stack.
Deployment tiers
All tiers include the gateway API, health endpoints and structured logging.
| Tier | Included transfer | Origins | Retention | Support |
|---|---|---|---|---|
| Starter | 2 TB / month | 1 | 7 days | |
| Growth | 20 TB / month | 5 | 30 days | Email, 8×5 |
| Broadcast | Committed | Unlimited | 90 days | Dedicated, 24×7 |
Getting started
Point a hostname at the gateway and verify it responds before moving traffic.
$ curl -s https://gateway.example.net/health
{"status":"ok","service":"media-gateway","version":"4.2.1"}
Full request reference, signing parameters and error codes are in the documentation.