The federated CDN for service providers
Put your customers' video, apps and web content right where they need it, close to their audience. OnApp CDN extends your reach and makes it easy to create valuable new CDN services for your customers.
The smart way to do CDN
OnApp CDN a federated content delivery network, designed for service providers. It gives you access to capacity in 170+ locations through our federation marketplace, with many more available if you need them. There are no tie-ins and no commitments: you can choose the exact mix of location, performance and price that your customers need, and create custom CDNs on demand.
A federated CDN for service providers
You build CDNs using your own infrastructure and/or the locations on our federation marketplace, a wholesale market for service providers. We monitor every location in the federation, and broker all transactions on the CDN marketplace as part of a fully managed service.
Different ways to deploy
You can build private CDNs across your own datacenters. You can build a CDN across your own datacenters and expand it with locations from the OnApp federation, on demand. Or just use the federation to create your own custom CDNs. You can use OnApp CDN to extend your OnApp cloud service, or deploy it standalone.
OnApp CDNaaS (CDN as a Service) is the brains behind OnApp CDN. Hosted by OnApp at locations around the world, it's a CDN logic engine and global Anycast DNS service that determines which CDN location is best placed to serve a content request.
CDNaaS combines information about a user's location with the status and location of each server in the CDN, to find the best server to deliver content to a user, and uses DNS routing to reduce the number of network hops required, which is faster than the traditional DNS configurations used by most other CDNs. OnApp CDN also supports Google DNS and Open DNS, and custom CNAME URLs.
Supported protocols & content types
OnApp CDN enables HTTP pull, push and caching for web content. With HTTP pull, content is pulled to an end user's closest CDN location when they request it, and is then available locally to other users that request it. Otherwise it stays on the origin server - the server that 'owns' the content. It's best suited for smaller file sizes, where the time taken to retrieve the original file from the origin server, for the first users in each location, will not be particularly noticeable. Once there's a local copy, local users will be served that copy until it changes.
Web content - push
With HTTP push, content is automatically distributed or 'pushed' to a selection of CDN locations when it is added to the origin server, or when it changes. It's better suited to larger files like software installers and patches, and when files are typically 50MB or larger - files that would take end users longer to download from the origin, if there isn't a local copy of the latest version.
Web content - caching
OnApp CDN also supports static and dynamic HTTP content caching at any CDN location. HTTP caching offloads web content onto the CDN network, and ensures that content is delivered more quickly by storing a copy at each CDN location.
Video on Demand
OnApp CDN allows you to deliver video files on request with YouTube-like control over playback, using features such as fast forward or rewind, and have the video buffer from that point instead of having to wait for video to download as with normal progressive streaming. Playback is up to 1080p. This protocol uses Nginix to serve videos through normal HTTP, supporting...
- FLV (Flash Video - .flv)
- MP4 (QuickTime container - .mp4, .f4v, .mov, .m4v, .mp4a, .3gp, and .3g2)
- H.264/AAC content in MP4 container files can be delivered to any supported player technology
...and the following platforms for video on demand:
- Adobe® Flash®
- Apple® iOS: iPhone®, iPad®, and iPod® touch
- Microsoft® Silverlight®
- Apple QuickTime™
- Android™, Blackberry® and other 3GPP platforms
With live streaming, content providers can broadcast high quality live video to end users, without buffering. OnApp CDN gives you access to a wide range of live streaming locations. OnApp CDN live streaming is enabled by Wowza Media Server 3, the leading high-performance media server. It supports:
- Adobe - RTMP / RTMPE / RTMPT
- Android - RTSP/RTP
- Flash - HTTP Dynamic Streaming (HDS)
- Apple – HTTP Streaming (HLS) for iPhone, iPod, iTouch
- Microsoft – Smooth Streaming for SilverLight
Reporting & analytics
OnApp CDN includes a range of reports that help you and your customers understand how different content and locations are performing. You can display reports as graphs and tables and export as a CSV for further analysis. CDN statistics can be viewed by CDN protocol type (HTTP Pull, Video on Demand etc); data type (cached and non-cached); by specific edge servers and groups of edges; by owner, country and time period; for live streaming and concurrent usage of live video streams; for CPU usage per edge and storage server; and for billing statistics.
OnApp CDN provides a number of features to protect your customers' content and help them to implement their own content delivery policies.
- SSL support (vanity and shared certificates) from the origin to the CDN, and from the CDN to the end user
- Link encryption for Flash (RTMPS, RTMPE, RTMPTE) to protect against content intrusion, unauthorized diversion and stream ripping
- Secure Token support against spoofing/stream interceptors
- Geoblocking support (include/exclude content access for specific locations)
- Anti-leech support for streams
- Hotlink prevention