Company snapshot
| Category | Google Cloud CDN | Imperva |
|---|---|---|
| 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.
Imperva provides a cloud-based CDN integrated with its Web Application and API Protection (WAAP) platform, focusing on security and performance. The service includes content caching, load balancing, and global Points of Presence (PoPs) to deliver low-latency web experiences. It offers robust DDoS protection, a Web Application Firewall (WAF), and bot mitigation, making it suitable for enterprises prioritizing security. Imperva serves industries like finance, healthcare, and e-commerce, with clients such as Mediolanum and Vodafone. The company, founded in 2002 and headquartered in San Mateo, California, was acquired by Thales in 2019. Its CDN is part of a broader cybersecurity suite, emphasizing secure content delivery.
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.
Imperva operates a global network with PoPs in North America, EMEA, APAC, and LATAM, including data centers in cities like Tokyo, New Delhi, and Miami. The exact number of PoPs is not publicly disclosed, but the network supports traffic rerouting during maintenance to ensure availability. It uses machine learning for dynamic caching and integrates with major peering partners for optimized routing. Regional strengths include North America and EMEA, with ongoing expansions in APAC and LATAM. Maintenance schedules, such as the August 2025 migrations in Hong Kong and Paris, ensure minimal disruption for Cloud WAF customers. Limitations include less transparency on PoP counts compared to competitors like Cloudflare.
Feature comparison
| Feature | Google Cloud CDN | Imperva |
|---|---|---|
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.
Imperva uses a pay-as-you-go (PAYG) model with enterprise-focused pricing, typically requiring custom quotes. No free tier or public per-GB pricing is available, as plans are tailored for high-security use cases. Volume-based discounts are offered for committed contracts. Pricing details are available at https://www.imperva.com/pricing/. The model suits large organizations but may be cost-prohibitive for smaller businesses.
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.
Imperva provides APIs for configuration and management, supporting an API-first approach. Realtime logs and analytics are accessible via the Imperva Management Portal, with log push for integration into external systems. No public documentation confirms Terraform or specific SDK support, limiting Infrastructure-as-Code (IaC) options. Migration tools are not emphasized, but the platform supports standard CDN configurations. Developers may find the API robust but less flexible for CI/CD pipelines compared to Fastly or Akamai.
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.
- Enterprises needing a CDN with strong security features like WAF and DDoS protection.
- Businesses in regulated industries (e.g., finance, healthcare) requiring robust compliance and bot mitigation.
- Organizations with global audiences benefiting from Imperva’s PoP distribution and low-latency delivery.
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 cost-effective, free-tier, or transparent pricing models.
- Developers needing extensive IaC support, such as Terraform or advanced CI/CD integrations.
- Companies focused on edge compute or serverless functions, which Imperva does not currently offer.
History & Notes
—
—