Company snapshot
| Category | BytePlus | OnApp CDN |
|---|---|---|
| Status | active | active |
| Founded | — | — |
| Headquarters | — | — |
| Website | — | — |
| Docs | — | — |
Overview
BytePlus, a division of ByteDance, provides a global Content Delivery Network (CDN) with over 1,300 points of presence (PoPs) and a bandwidth capacity exceeding 120 Tbps. It serves businesses needing low-latency content delivery for web, apps, video streaming, and downloads. Its customer base includes media, e-commerce, and gaming companies, particularly in APAC and China, leveraging ByteDance’s infrastructure expertise. The CDN integrates security features and edge computing capabilities, targeting enterprise clients with high-traffic demands.
OnApp CDN is a federated content delivery network designed for hosting providers, utilizing spare capacity in OnApp Clouds to deliver content globally. It supports HTTP push, pull, and streaming/live streaming, catering to hosting providers and enterprises managing web content delivery. The platform integrates with OnApp Cloud, enabling users to leverage a network of edge servers for improved performance. It is primarily used by service providers and enterprises needing scalable CDN solutions. The service is operational as of August 16, 2025, with recent updates enhancing its reporting capabilities.
Network & Architecture
BytePlus operates over 1,300 PoPs across more than 70 global locations, with a focus on APAC and China, where it holds a China-licensed CDN status. Its network supports over 120 Tbps of bandwidth, optimized for video streaming and large file downloads. The architecture uses SSD-based cache servers and DNS-based load balancing for reliability. Strong peering in APAC ensures low latency, though coverage in Africa and LATAM is less extensive compared to providers like Cloudflare or Akamai.
OnApp CDN operates a global network of Points of Presence (PoPs) by leveraging spare capacity from OnApp Clouds, though specific PoP counts are not publicly detailed. It uses a federated model, combining edge servers from multiple cloud hosts to ensure broad geographic coverage. The platform supports content delivery across regions including North America, EMEA, APAC, and others, with synchronization between CDN and OnApp Cloud occurring every 20 minutes by default. Regional strengths include flexibility for hosting providers, but limitations may arise from reliance on third-party cloud capacity, potentially affecting consistency in less dense regions.
Feature comparison
| Feature | BytePlus | OnApp CDN |
|---|---|---|
waf | ✓ | ✗ |
bot_mitigation | ✓ | ✗ |
ddos | ✓ | ✗ |
rate_limit | ✗ | ✗ |
http3_quic | ✓ | ✗ |
tls13 | ✓ | ✗ |
tiered_cache | ✓ | ✗ |
origin_shield | ✓ | ✗ |
instant_purge | ✓ | ✓ |
stale_while_revalidate | ✗ | ✗ |
stale_if_error | ✗ | ✗ |
image_optimization | ✓ | ✗ |
video_vod | ✓ | ✓ |
video_live | ✓ | ✓ |
drm | ✗ | ✗ |
hls_dash_packaging | ✗ | ✗ |
websockets | ✗ | ✗ |
signed_urls | ✓ | ✗ |
edge_compute | ✓ | ✗ |
functions | ✓ | ✗ |
kv_storage | ✓ | ✗ |
api_first | ✓ | ✓ |
realtime_logs | ✓ | ✓ |
log_push | ✓ | ✗ |
terraform | ✗ | ✗ |
Legend: ✓ = Supported, ✗ = Not supported, — = Not listed
Pricing
BytePlus uses a pay-as-you-go (PAYG) model with enterprise-focused pricing, though specific per-GB rates are not publicly disclosed. No free tier is available, and pricing details require contacting their sales team. The model supports flexible scaling for high-traffic needs, often customized for enterprise clients. No public pricing page is provided; contact sales for details.
OnApp CDN primarily targets enterprise clients, with pricing typically based on committed contracts tailored to hosting providers. No public per-GB pricing is disclosed, and there is no free tier or pay-as-you-go (PAYG) option widely advertised. Pricing details are available through direct inquiry with OnApp sales teams. For more information, visit https://www.virtuozzo.com/onapp-cdn/.[](https://www.virtuozzo.com/onapp-cloud-docs/7.0/release-notes-onapp-6-4/OnApp%2520CDN.pdf)
Integrations & DevEx
BytePlus supports API-driven configuration for automation, with real-time logs and log push for monitoring. It offers SDKs for integration but lacks Terraform support. Migration guides are available, covering DNS updates, SSL/TLS setup, and A/B testing for transitions. The console provides tools for managing domains, certificates, and edge functions, though developer-centric features are less extensive than Fastly or Cloudflare.
OnApp CDN offers API-first integration for managing CDN resources, with documentation available at https://docs.onapp.com/cdn/. Real-time logs support monitoring, but there is no public evidence of Terraform support, SDKs, or specific CI/CD integrations. The platform includes tools for managing CDN resources within the OnApp Control Panel, with recent UI updates enhancing usability. Migration tools or import capabilities are not explicitly documented.
When it fits
- Enterprises needing high-capacity video streaming or large file downloads, especially in APAC and China.
- Businesses requiring China-licensed CDN services with strong regional performance.
- Users leveraging edge compute for custom logic or low-latency key-value storage.
- Hosting providers needing a federated CDN integrated with OnApp Cloud for scalable content delivery.
- Enterprises requiring video VOD and live streaming with global reach through a network of edge servers.
- Users prioritizing API-driven management and real-time logging for CDN operations.
When it doesn’t
- Small businesses or startups seeking free tiers or transparent, low-cost pricing.
- Organizations needing extensive coverage in Africa or LATAM, where PoP density is lower.
- Developers requiring robust Terraform or CI/CD integrations for infrastructure-as-code workflows.
- Small businesses or startups seeking pay-as-you-go pricing or free tiers, which OnApp CDN does not offer.
- Organizations needing advanced security features like WAF, DDoS protection, or bot mitigation, which are not documented.
- Users requiring edge compute, image optimization, or specific protocol support like HTTP/3, which are unsupported.
History & Notes
—
—