Any service, website or mobile app could leverage the benefits of using PUSHR CDN for media delivery. Depending on the use case, there are two types of CDN service being offered - Push and Pull. They differentiate based on the origin of the delivered content and require different setups to operate. However they do share the same core requirements listed below.

Web or App Server

While PUSHR CDN can pull, store, cache and deliver your media and software to your customers, it can not host your website. PHP and other server-side languages are not supported on our network and your app, service or website needs to be served from a shared hosting, VPS, Dedicated server or a cloud hosting provider of your choice.

Access to website/app code

In it's simplest form, PUSHR provides you with a URL which you then use to replace existing links on your website. Once a link to a file has been replaced, whenever this file is requested for download or streaming, the traffic flows through our network and the file is served from our edge cache servers instead of your own server. As such, in order to use PUSHR, you need to have access to the source code of your app, service or website to replace the existing links with the new ones.

CDN Push requirements

CDN Push mode operational details are covered in the next section

When used in Push mode, PUSHR CDN allows you to store your content directly in the CDN network. As such, there is no requirement for large, secure and high-performant storage solution on your end. Your app or web server is only required to run your frontend/backend/app, and server costs are grealy reduced.

CDN Pull requirements

CDN Pull mode operational details are covered in the next section

CDN Pull allows you to use your own storage backend. This solution requires enough storage on your server(s) since PUSHR will pull uncached content from there. Performance of the storage origin should also be guaranteed else our service may be unable to perform cache fill operations fast enough.