AI Log — waiting for first event…
Workspace00000000…000001
Dev mode

Get started

Your in-console path to going live on multi-CDN. Follow the stages — we tick them off as you go. (Deployment + install live in Setup.)

Deployment: Self-managed · Connected
Setup progress — 0%
Each stage below deep-links to the page that completes it.
0 / 6 stages
  1. 1
  2. 2
  3. 3
  4. 4
  5. 5
  6. 6

First configuration

Inside the console, against your live data plane. Work the stages top-to-bottom — done-ticks reflect your real workspace where we can derive them.

Stage 1

Connect your origin

m-cdn doesn't host your video — it needs to know where your manifests + segments already live.

  • Add your origin URL (packager, S3, GCS, Wowza).
  • Let the auto-detect probe read manifest kind, geography + codecs.
  • Run “Verify & create” — reachable, manifest parsed, CORS OK.
Open Origins
Connect your origin
Stage 1 walkthrough — point m-cdn at your source.
Stage 2

Add two or more CDNs

m-cdn routes between CDNs — one gives it nothing to choose between, so the floor is two.

  • Add CDN #1 with your BYOC creds (creds stay in your account).
  • Add CDN #2 on a different network (e.g. CloudFront + Media CDN).
  • Stage ticks the moment the 2nd CDN lands (≥2 rule).
Open CDN providers
Add two or more CDNs
Stage 2 walkthrough — give the router something to choose.
Stage 3

Connect DNS & Steering

DNS + Content Steering is how viewers reach the current best CDN — and how m-cdn steps out of the critical path (ADR-122).

  • Connect DNS — delegated default, or BYO (Route 53 / Cloudflare / GCP / Azure).
  • Paste the NS/CNAME records once at your registrar.
  • Content Steering re-points players to the best pathway on a TTL.
Open DNS & Steering
Connect DNS & Steering
Stage 3 walkthrough — DNS steering, m-cdn out of the path.
Stage 4

Prepare your player

Your player is the last mile — two questions: does it send CMCD, and does it follow Content Steering?

  • Run the wizard — paste a page URL or pick your player manually.
  • If it lacks a remote CMCD toggle, drop in the one-line enabler (#88).
  • verify-flow confirms real CMCD events arriving, then Mark done.
Open player wizard
Prepare your player
Stage 4 walkthrough — make your player talk to m-cdn.
Stage 5

Go live (cutover)

Flip traffic to the v2 architecture — DNS-steered, pre-published manifests, m-cdn out of the path. Reversible.

  • Start at a small v2 traffic %; validate v1 vs v2 side by side.
  • Review the DNS records that change + the impact summary.
  • Flip to 100% v2 — the rollback window stays open.
Open cutover
Go live (cutover)
Stage 5 walkthrough — go live, reversibly.
Stage 6

See it work — live CDN switching

The payoff: watch the real thing. m-cdn moves viewers between CDNs live while the stream keeps playing.

  • Open the live-proof page — stream on the left, engine on the right.
  • Watch “Currently serving via” flip as conditions change.
  • Mark done once you've seen a real switch land.
See it work
See it work — live CDN switching
Stage 6 — the patented mid-stream switch, live.
Finish the stages, then see it switch live

The journey ends with proof: m-cdn moving viewers between CDNs live, the stream never stopping. Open the live-proof page and watch the “serving via” flip.

See it work — live CDN switching