Register
Name, work email, company. No card, no call, no questionnaire.
Move what you already run
Bring the setup you have today.
You register, we read your stream, and we send you a link to a console that already has your delivery in it.
Four steps
Nothing to export. Nothing to rebuild by hand.
Most of the configuration you would have typed is already readable from the stream itself. We do that part, and only ask about what cannot be read.
Send one playback URL
A public URL, or a token good for ten minutes. That is the whole input.
We read and rebuild
We read what is actually being served and recreate it as services, CDNs and origins in your workspace.
You get a link
A console with your delivery already modelled, and the few questions that could not be answered from the stream.
Read from the stream
What we can tell without asking you.
Which CDNs serve youFrom the response headers your CDNs already send, including the vendor-specific ones.
Whether you are already multi-CDNAnd how the split is being made — DNS weights, a steering vendor, or a list inside your player.
Your bitrate ladderRenditions, resolutions and codecs, straight from the master manifest.
Segment durationWhich sets your latency class, your reaction budget, and whether you run low-latency HLS.
DRM and encryptionWhich scheme is in use, and whether keys survive a CDN switch.
Signed URLsWhether your links are token-protected, and in what shape.
Three questions
What we still have to ask.
The rest is judgment, not data — so we ask instead of guessing.
Quality first, or cost first?
Both are honoured under a floor you set. We need to know which side the floor protects.
Who signs your URLs?
If your links are token-protected, we need the signing arrangement so a switched segment stays valid.
Shadow first, or straight across?
Shadow runs beside your production delivery and changes nothing until the numbers agree with you.
Register, and we send you the link.
You keep serving from the CDNs you have. Nothing moves until you say so.