The vidNT Brain

The brain that prevents the incident.

Personalized Video Stitching & Predictive Multi-CDN Engine

Others measure the experience. The brain improves it — before anyone opens a dashboard.

Why a decision layer

A weight in a DNS console cannot see a viewer buffering.

That is the whole argument. Everything below follows from it.

It decides per viewer

Two people on the same street, on different networks, can need different CDNs. A regional weight gives them the same answer. vidNT gives each session its own.

How routing works

It listens to real players

CMCD (CTA-5004) carries buffer level, bitrate and stalls up from the player. CMSD (CTA-5006) carries the CDN's own view back down. vidNT routes on those — not on a synthetic probe alone.

About the signals

It cannot take you down

Manifests are served by your CDNs, not by us. vidNT publishes its decisions ahead of time and steps aside. If we fail, delivery carries on with the last good answer.

The architecture
Beyond monitoring

QoE software measures the experience. The brain improves it.

Video QoE measurement tools watch your stream and hand you a report when viewers suffer. vidNT takes the same signals — and acts on them, in the delivery loop, before the suffering starts.

Measurement software

  • Watches every session in real time.
  • Detects and classifies a broad spectrum of errors.
  • Sends you a dashboard, a report, and an alert — then a human fixes it. Tomorrow.
  • Lets you set automatic QoE alerts — so you find out fast that viewers are already suffering.

The vidNT brain

  • Consumes the same signals, live, on the serving path.
  • Scores every CDN per viewer and network, continuously, learning as it goes.
  • Switches the source of the next chunk before the viewer feels anything. No ticket. No war room.
  • Acts before the alert condition ever exists — the threshold never trips, because the routing already moved.

The best alert is the one that never fires. The best incident report is the one that never gets written.

Analytics

The numbers behind every decision.

The brain does not ask you to trust it. Every routing decision it makes is recorded with the signals that produced it, so the same data that drives the switch is the data you read afterwards — per CDN, per region, per access network, down to a single session. These are the shapes you actually work with.

Quality over time, per CDN

CDN A CDN B Routed

The blended line is what your viewers actually got. When one CDN degrades, the routed line does not follow it down.

Where the traffic went

Primary Alternate

Share per CDN across the day, with the reason each shift happened attached to it — quality, capacity or cost.

Per network, not per country

FibreCable Mobile AMobile B
Healthy Needs a different CDN

A national average hides the one access network where viewers are suffering. This resolution is what makes the routing act.

Every number here is the same number the routing used — no separate reporting pipeline, no reconciliation, and no viewer identities anywhere in it. See the parameters we collect →

Analytics at every level.
Privacy at every level.

Prevention does not mean flying blind. Drill from the whole fleet down to a single session — per CDN, per region, per access network, per chunk — with every routing decision accounted for. And the pipeline is built to privacy rules: pseudonymous session IDs only, no viewer identity, location kept at geography level, aggregate views by default.

Right of access, built in

A viewer’s quality history is exportable on request through an authenticated, verified API — JSON or CSV. GDPR access is a feature, not a scramble.

Pseudonymous by design

Session tokens, never identities. No names, no e-mails, no accounts in the delivery pipeline — and location stays at geography level.

Minimised at ingest

Telemetry fields are scrubbed at the door; opaque tokens are hashed before they are ever stored. What we don’t keep can’t leak.

AI training is opt-in only

No model trains on your traffic without a signed data-sharing addendum — scoped, revocable, and audited per request.

Immutable audit trail

Privacy-relevant actions — including our own operators viewing your account — land in an append-only audit log.

The paperwork ships with it

GDPR, CCPA and Thai PDPA data-processing templates come with the product — in legal language and in plain English.