Like many organizations, you probably use commercial content delivery networks (CDNs) to manage traffic flows, deliver content to your users faster, and ensure uptime. 

Building CDNs isn’t always easy, that’s why people rely on CDN providers to take care of their content delivery. But in terms of control, performance, and cost, it actually makes a lot of sense for some companies to build their own CDN. It can also be easier and cheaper than you think to deploy a multi-CDN setup, make costs more predictable, optimize available hardware and gain control over your content delivery. 


Who better to talk to about multi-CDN strategies than Matt Levine, CTO of CacheFly, a large-scale commercial CDN operator that’s built on top of Varnish Enterprise?


We'll cover:
  • The different possibilities of CDN and multi-CDN
  • When it makes sense to choose a regular As A Service CDN 
  • When you should consider building your own in-house CDN
  • In which scenario a hybrid setup could work

Our Expert Panel


Thijs circle-cropped


Mat Levine Cachefly


Thijs Feryn

Matt Levine

Technical Evangelist | Varnish Software

CTO | CacheFly