Route on price without betting quality.
Some multi-CDN products model cost as one filter in an ordered chain: the CDNs that survive the availability filter get sorted by the price tag you typed in, and the cheapest survivor wins. That is lexicographic — cost only speaks after every other filter has finished talking.
Ordered filters: up, cost, availability threshold, select. Easy to explain — and blind to the trade. A CDN sitting one millisecond inside the quality threshold at a fraction of the leader’s rate is treated exactly like one at the edge of failing it. The chain can eliminate; it cannot weigh.
Cost is a scored dimension in a weighted blend, underneath a quality floor. When two CDNs deliver the same experience, the cheaper one carries more traffic. When quality diverges, quality outranks price — continuously, not in stages. Every decision logs which dimension moved it, so you can audit the trade instead of trusting it.
The engine scores with the numbers you actually pay, not list prices — and it respects the shape of your contracts, not just their rates.
Enter each CDN’s contracted rate when you add the provider. From then on, every routing decision prices traffic with your numbers.
Committed volumes are tracked against actual placement, so traffic can be pointed deliberately at a commit you would otherwise miss — instead of discovering the shortfall at true-up.
Per-CDN caps and budget alerts put a ceiling under the routing, so a quiet reweighting never turns into a procurement surprise.
The platform fee is flat. When cost-aware routing saves money, the console shows the saving next to the decisions that produced it — and the invoice ignores it. No counterfactual baseline, no share of a number nobody can audit, no incentive for us to route your traffic toward our margin.
Cost data never changes what you owe us. It only changes where your traffic goes.
Import your CDNs and rates, then read the decision log balancing them against quality.
Leave your details and we open your access. A person comes back to you within one business day.
Open your assistant with a ready prompt — ask it anything about multi-CDN stitching, how vidNT fits your stack, or how to start.
The prompt asks your assistant to read vidnt.com/llms.txt and answer from it.