Wistia's Multi-CDN Delivery Approach

Using more than one CDN turns delivery infrastructure from a single point of failure into a controllable input on cost and performance. For a video host, that matters because every play depends on moving large files quickly across many geographies, and outages or weak regional coverage show up immediately as buffering, failed starts, and customer pain. Wistia kept its CDN layer generic so it could reroute traffic between Akamai and Fastly, preserve uptime, and keep suppliers competing on price.

• The practical job of a multi CDN setup is traffic steering. If one network has a regional problem, or performs worse in APAC or rural areas, Wistia can shift delivery rather than wait for one vendor to recover. That is especially important in video, where delivery quality is part of the product, not a back office detail.
  1 sacra
• This also reflects where value sits in the stack. Wistia built in house for encoding and customer facing analytics because those directly shape margins and product differentiation, but bought CDN capacity from large providers because CDN delivery had become more standardized and easier to swap across vendors.
  1 sacra 3 sacra
• The contrast with Mux helps show the tradeoff. Mux also emphasizes redundancy and flexibility underneath its platform, but its product goal is to abstract the whole video stack for developers. Wistia instead uses commodity infrastructure underneath a marketing software layer, where the money is made from lead capture, embeds, integrations, and analytics rather than raw delivery itself.
  1 sacra 2 sacra 4 sacra

The direction of travel is that CDN delivery keeps looking more like a utility, while differentiation moves upward into workflow and data. That favors companies that can treat infrastructure as interchangeable plumbing, then package video into higher value software tied to revenue, attribution, and content operations.