Low latency that survives the concurrency peak
Any CDN can hit two seconds with a thousand viewers. The question is what happens at a million, on mobile networks, during the only three minutes of the event that anyone remembers. We built the packaging into the edge so the answer stays the same.
One ingest. Every format. No storage fan-out.
Contribution arrives once. Transcoding, packaging, DRM and delivery all happen downstream of that single mezzanine — so adding a format costs you CPU, not another copy of the catalogue.
Latency is easy. Latency and stability is the product.
Chasing the live edge is what breaks players. Our edge holds partial segments in memory and answers blocking playlist requests locally, so a viewer on a congested mobile network steps down a rung instead of stalling and resyncing.
Championship final, Meridian Live, 2026. Illustrative figures for this design.
Per-title encoding
A talking-head interview and a 60 fps action sequence do not deserve the same ladder. We analyse each asset and build the rungs it actually needs — typically 22–38% fewer bits at matched VMAF.
Studio-grade protection
Multi-DRM with a single licence API, forensic session watermarking, concurrent-stream limits and geo/token gating enforced at the edge rather than in your player.
Catalogue at the edge
Thumbnails, sprites, subtitles and trick-play generated on request and cached, so a back-catalogue refresh does not mean re-uploading a petabyte.
What we package, from one mezzanine
| Delivery format | Codecs | DRM | Typical use |
|---|---|---|---|
| LL-HLS (CMAF) | H.264, HEVC, AV1 | FairPlay, Widevine | Live sport, auctions, esports |
| LL-DASH (CMAF) | H.264, HEVC, AV1 | Widevine, PlayReady | Live, Android & smart TV |
| HLS (TS & fMP4) | H.264, HEVC | FairPlay | VOD catalogue, legacy iOS |
| DASH | H.264, HEVC, AV1, VP9 | Widevine, PlayReady | VOD catalogue, web |
| Progressive MP4 | H.264, AV1 | Signed URL | Social clips, downloads, previews |
Point a test stream at us this afternoon
Free ingest endpoint, real PoPs, real numbers. Compare startup time and rebuffer ratio against your current delivery before you commit to anything.