Your CDNs
The contracts, accounts and edge networks you already have. vidNT adds the decision layer between them, not another vendor under them.
Solutions · Streaming services
Always-on multi-CDN.
Multi-CDN as day-to-day operations.
The habit
Balance cost and quality every hour, not every outage.
Most multi-CDN setups exist for the bad day and idle through the good ones. For an OTT service or a FAST lineup, the routing should work the ordinary weeks: continuously weighing quality and cost per viewer across your CDNs, moving traffic in small, logged adjustments instead of dramatic failovers. The same mechanism that rescues a session on the loud night trims the delivery bill on the quiet ones.
The fit
The CDNs you have. The standards you already speak.
vidNT is not a CDN and does not replace yours. It routes between the ones you are already contracted with, using open standards on both sides of the player: CMCD (CTA-5004) up from hls.js, Shaka, dash.js, native and in-house players; HLS and DASH Content Steering back down. Nothing proprietary ships in your client, so nothing proprietary can hold your client hostage.
Your players
Standards-native: the players you ship today already speak the protocol the routing listens to.
Your DNS
Session-start answers publish through the DNS you already run. No re-delegation of your zone to a routing vendor.
The receipts
Analytics with honest provenance.
Every chart traces to decisions, and every decision to the signals that produced it — drill from the whole fleet down to a single session, per CDN, per region, per access network. Savings appear as an advisory figure next to the routing that produced them, and never as a billed number: the platform fee is flat, so the analytics have no reason to flatter themselves.
Make the quiet weeks cheaper and the loud nights survivable.
Start from the CDNs and players you already run — nothing gets replaced.