Website · Documentation · Pricing

Cost calculator

Your traffic

Choose a workload. We’ll estimate traffic and requests for you.

Estimated monthly costs

USD per month, before tax. Load balancing and unpriced extras are excluded.

What’s included?

Estimates cover cacheable content. Origin and optional services are added only when you enter their rates. Plans differ in features and coverage; check their terms before buying.

Advanced settings
Split traffic between regions

Percentages must total 100%. The same split applies to bytes and requests. CloudFront charges by serving edge location; this is an approximation. Shared free allowances are allocated proportionally.

Origin and optional services

Paid tiers start with this workload; estimates do not include other account traffic. Enter your own effective rates after origin allowances. Reads use request misses; egress uses byte fill. Functions assume one invocation per viewer request. Zero leaves an extra out of the estimate; it does not mean your origin is free.

Compare a quote you received

This is your quote, not a published provider price. Use an effective rate for the selected traffic mix; tiers, included usage and commitments need to be reflected in your inputs. Sharing a scenario includes your quote details.

Presets are starting assumptions, not measured traffic. Video assumes one rendition and segment GETs; playlists, retries and extra audio tracks add requests. Fill is a byte ratio, not a request cache-hit rate. GB = 1 billion bytes; Google bills GiB = 1,073,741,824 bytes; CloudFront estimates use binary GB as a billing assumption.

Overview

OnApp CDN is a federated platform aimed at hosting providers. Its CDN product line dates to 2011; Virtuozzo acquired OnApp in 2021. The former OnApp company had its headquarters in London.

  • Stack: run edge software in your cloud.
  • CDNaaS: hosted DNS redirection selects an appropriate location.
  • Federation: subscribe to other hosts’ bandwidth or offer accepted edge capacity.

The current public portal documents the platform, rather than establishing which marketplace locations or commercial options are available to a particular account.

Network

Coverage combines your own edge locations with subscribed federation capacity. Location groups, resource types and account limits determine which nodes can serve a workload.

Ask which marketplace locations are currently available and test them from your audience’s networks. Older PoP counts and example locations in tutorials are not current coverage guarantees. Validate the chosen locations, available streaming resources, throughput and audience performance in the actual account.

Features

FeatureSupported
Web application firewall✓ Supported
Bot protectionNot listed
DDoS protection◐ Partial
Rate limitingNot listed
HTTP/3 (QUIC)Not listed
TLS 1.3Not listed
Tiered cachingNot listed
Origin shieldNot listed
Instant cache purge◐ Partial
Serve stale while refreshingNot listed
Serve stale on origin errorsNot listed
Image optimizationNot listed
On-demand video✓ Supported
Live video✓ Supported
Digital rights managementNot listed
HLS / DASH packaging◐ Partial
WebSocketsNot listed
Signed URLs✓ Supported
Edge computeNot listed
Edge functionsNot listed
Key-value storageNot listed
Configuration API✓ Supported
Real-time logs✓ Supported
Log export✓ Supported
Terraform providerNot listed

✓ Supported · Partial: limited or separate-product support · ✗ Not supported · Not listed: unconfirmed. Some features need a separate product or plan.

HTTP delivery and access

HTTP pull and push resources support cache rules and path or whole-resource purges. Purge APIs apply to HTTP resources; immediate completion remains unconfirmed. Signed access and video token authentication are documented.

WAF controls expose OWASP rule groups, with a maximum of ten enabled rules per resource. Rule-update management is unconfirmed. Limited application-layer DoS rules do not confirm full volumetric scrubbing or security coverage on every plan.

Two media paths

HTTP Pull can restream prepared HLS content. It does not perform transcoding or transmuxing; prepare the stream upstream and configure playlist/segment cache rules.

Separate Wowza-based streaming resources support RTMP sources and HLS restreaming with codec and origin restrictions. They require eligible streaming locations or your own instances. The guide limits white-label HTTPS and requires publishing to both configured primary and backup points for failover. Check the chosen media path’s formats, origins and failover setup before deploying it.

Request logs

Raw logs can be delivered by Syslog or FTP/SFTP. The guide describes immediate Syslog delivery and ten-minute FTP/SFTP batches, using different record formats. This does not guarantee lossless delivery or identical timing on every subscribed location.

Pricing

Marketplace sellers set bandwidth prices and may agree private rates for a particular buyer. Platform licensing, local infrastructure and subscribed locations add separate costs; a single public delivery rate for all sellers is unconfirmed.

The streaming-resource guide lists USD 50 per month per own Wowza instance. Confirm that current charge and any streaming-location subscription before budgeting. It is not a CDN-wide fixed fee.

Use Advanced → Add your quote for confirmed delivery and request rates. Add licensing, hosting, streaming instances and other fixed costs as monthly extras. Confirm minimums, currency and tax independently.

Developer tools

  • Manage resources, caching, purges, reports and raw-log settings through the documented APIs and control panel.
  • Generate application-side access tokens with the documented integrations.
  • Configure a Syslog or SFTP destination according to log format and timing requirements.
  • Evaluate the linked billing integration for your platform version.

Confirm deployment version, permissions and endpoints; documentation examples are not a production credential configuration. Terraform and current SDK runtime coverage are unconfirmed.

When it fits

  • Hosting providers combining owned CDN nodes with contracted federation capacity.
  • Operators comfortable managing edge software, customer billing and subscribed locations.
  • Prepared HTTP/HLS delivery or separately verified Wowza streaming workflows.
  • Teams needing configurable raw-log delivery and application access controls.

Before you choose

  • Prices and coverage depend on the marketplace sellers and locations you subscribe to.
  • HTTP HLS restreaming needs already encoded content; it does not transcode.
  • Limited WAF DoS rules do not confirm volumetric attack protection.
  • Publish to both primary and backup streaming points when configuring failover.
Sources