Company snapshot
| Category | Google Cloud CDN | OnApp CDN |
|---|---|---|
| Status | active | active |
| Founded | — | — |
| Headquarters | — | — |
| Website | — | — |
| Docs | — | — |
Overview
Google Cloud CDN is a content delivery network integrated with Google Cloud. It sits behind Google Cloud Load Balancing to cache and serve HTTP(S) content from edge locations. Typical users are teams already running workloads on Google Cloud that want CDN caching, signed URLs, modern TLS, and consistent operations across the platform. The service emphasizes policy-driven caching, fast invalidation, and security integration through Cloud Armor. Pricing follows a pay-as-you-go model that varies by region and usage.
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
Google Cloud CDN uses Google’s global edge and backbone to terminate HTTP(S) traffic close to end users and fetch from origins over Google’s private network. Coverage spans major regions in North America, Europe, and Asia-Pacific, with additional presence in other geographies. Strengths include integration with Google Cloud Load Balancing, Anycast routing, and private backbone connectivity from edge to origin. Limitations can include fewer CDN-specific knobs than specialist CDNs and feature gaps for advanced video packaging.
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 | Google Cloud CDN | 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
Pay-as-you-go pricing with regional rates for cache egress and request charges. Total cost depends on geography, volume, and cache behavior. See cloud.google.com/cdn/pricing for current 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
Deep integrations include Google Cloud Load Balancing for traffic ingress, Cloud Armor for WAF and DDoS protections, Cloud Storage and Compute Engine for origins, and Cloud Logging and Monitoring for observability. Infrastructure as code is supported via Terraform, and a REST API enables CI/CD automation.
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
- Workloads already hosted on Google Cloud that need an integrated CDN layer.
- Teams standardizing on Cloud Load Balancing, Cloud Armor, and Cloud Logging.
- Organizations that want signed URLs, HTTP/3, fast purge, and policy-driven caching.
- Buyers who prefer Terraform and API-first management across cloud services.
- 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
- Multi-cloud environments seeking provider-neutral or MultiCDN routing.
- Advanced video workflows needing packaging, DRM, or low-lency live features.
- Use cases requiring built-in image optimization pipelines.
- Projects that rely on WebSocket-heavy bidirectional traffic at the edge.
- 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
—
—