Frequently asked questions
What is a Multi-CDN Stitcher?
A layer that turns all the CDNs you already pay for into one delivery system: an AI brain scores every CDN for every viewer, continuously, and stitches the stream chunk by chunk from whichever source is best right now — switching mid-stream, while the video keeps playing. The mechanism is patent-protected. The viewer sees one unbroken stream and never knows.
How is stitching different from DNS-based multi-CDN steering?
DNS steering answers one question — “which CDN should this resolver get?” — once, before playback, for everyone behind the same resolver, cached for the TTL. It cannot see a viewer’s buffer and cannot help a viewer who is already connected to a degrading CDN. vidNT decides per viewer, per chunk, during playback. We publish DNS too — it is our first layer — but the decision lives where the session lives.
How is vidNT different from video QoE measurement software?
Measurement software watches your stream and reports when viewers suffer — then a human fixes it. vidNT consumes the same signals on the serving path and acts: the source of the next chunk switches before the alert condition ever exists. You still get analytics at every level; you just stop needing the war room.
Does vidNT work with the CDN providers I already have?
Yes — that is the point. CloudFront, Google Media CDN, Cloudflare, Akamai, Fastly, Azure Front Door, Huawei Cloud, your own private CDN, or any custom endpoint. Your contracts stay exactly as they are; vidNT decides which one serves each chunk.
Do I need to change my player or install a proprietary plugin?
No. vidNT is standards-native: CMCD (CTA-5004) and HLS/DASH Content Steering are already implemented by hls.js, Shaka, dash.js and native players — usually a one-line config. Some vendors require their own client plugin with a private protocol; we deliberately do not.
How fast does vidNT react when a CDN degrades or fails?
Every viewer’s source is re-scored every few seconds. In our live drill against two production CDN networks, an injected degradation moved every session to the healthy CDN mid-stream in about 25 seconds — including the viewers already connected, with zero drops. That last part is the difference: DNS-based tools can only redirect the next viewer.
Can vidNT reduce my CDN costs?
Cost is one of the dimensions the brain scores, so cheaper CDNs win whenever they meet your quality bar — and the savings show up in your analytics. We price honestly: a flat platform fee. We show the savings; we don’t take a cut of them.
Does vidNT introduce a new single point of failure?
No — and we can say it more strongly than anyone in the category: vidNT is architected out of the critical path. Manifests are served by your CDNs, steering is published ahead of the request, and if vidNT itself goes down, playback simply continues on the last-known-good routing. A DNS-based steering stack cannot make that claim — authoritative DNS is in the path by definition.