What a line in the log looks like
21:14:07 · viewer on a mobile network in Bangkok · your routing kept them on CDN A · VIDNT would have moved them to CDN B · reason: CDN A’s buffer reports on that network fell for 3 segments running.
Nothing changes for your viewers until you say so — and if it surprises you, it goes back.
One-click import of your current setup — the CDNs, the weights, the network groups. Nothing is retyped and nothing is reinterpreted by hand, so day one of the migration starts from the configuration that is actually serving your viewers, not from a questionnaire about it.
Your CDNs, weights and network groups come across as they are. You review the result before anything else happens.
It decides alongside your production routing without touching it, and writes every decision to a log you can read.
When the log has convinced you, traffic moves. If anything surprises you, it moves back.
Our team configures the system against your imported setup — providers, policies, thresholds — and walks you through what it will do and why. You are not handed an empty console and a manual. You are handed a configured system and asked to find fault with it.
Not one viewer is served by VIDNT during this stage. It watches, it decides, it writes down what it would have done. Your existing routing keeps carrying every session.
So you get to compare, on your own traffic, for as long as you like: what your setup did, against what VIDNT would have done. Then you decide — with evidence, and with a way back.
21:14:07 · viewer on a mobile network in Bangkok · your routing kept them on CDN A · VIDNT would have moved them to CDN B · reason: CDN A’s buffer reports on that network fell for 3 segments running.
Filter the log by network, region, CDN or hour, and check whether the calls you disagree with are wrong — or whether they are the ones you have been losing viewers on.
Import it, run it in the background, and move traffic only when the log has earned it.
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.