Company snapshot
| Category | Google Cloud CDN | IORiver |
|---|---|---|
| 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.
IORiver is a MultiCDN platform that enables businesses to manage multiple CDN局
System: Content Delivery Networks (CDNs) simultaneously, ensuring high availability and performance without the complexity of managing each CDN separately. Founded in 2024 by former Akamai engineers Edward Tsinovoi and Michael Hakimi, IORiver is based in Tel Aviv, Israel, and serves industries like SaaS, online retail, streaming media, and finance. The platform handles over 100 petabytes of traffic monthly, offering a unified interface for configuring edge services like WAF, rate limiting, and edge computing across multiple providers. It integrates with major CDNs such as Cloudflare, Akamai, Fastly, Edgio, and Amazon CloudFront. IORiver focuses on simplifying MultiCDN adoption for businesses needing global content delivery with minimal operational overhead.
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.
IORiver does not operate its own CDN infrastructure but orchestrates traffic across multiple third-party CDNs, including Akamai, Cloudflare, Fastly, Edgio, Amazon CloudFront, G-Core, and Microsoft Azure. Its Virtual Edge solution routes traffic to optimal CDN providers based on geolocation, traffic type, or cost, achieving 99.999% availability. The platform supports global content delivery with no specific POP count disclosed, relying on the combined footprints of integrated CDNs. It uses a Multi-DNS approach for resilient routing, avoiding single points of failure. Regional strengths depend on the chosen CDN providers, with flexibility to include local CDNs for markets like India or China.
Feature comparison
| Feature | Google Cloud CDN | IORiver |
|---|---|---|
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.
IORiver operates on a pay-as-you-go (PAYG) model, with pricing based on traffic volume and bundled services like WAF and analytics. No public per-GB pricing is available, and costs vary depending on the mix of CDN providers used. IORiver negotiates wholesale agreements with CDNs to reduce costs, but specific pricing details are not disclosed on their website. Potential users should contact IORiver directly for quotes. No free tier or trial details are publicly listed.
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.
IORiver supports Terraform for infrastructure-as-code, enabling automated configuration of multi-CDN setups. It offers REST, Python, and Go APIs for programmatic control, integrating seamlessly with CI/CD pipelines. Real-time logs and analytics via GlobalView provide insights into traffic patterns and performance. Migration tools simplify switching CDNs by importing configurations and testing providers with minimal traffic initially. The platform supports integration with major CDNs like Akamai, Cloudflare, and Amazon CloudFront, reducing setup complexity.
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.
When it fits
- Businesses using multiple CDNs to optimize global performance, reliability, or cost, especially in SaaS, retail, or streaming.
- Teams seeking a unified interface to manage complex multi-CDN setups without in-house tools.
- Organizations needing advanced edge services like WAF, DDoS protection, or edge computing across vendors.
When it doesn’t
- Small businesses or startups needing a single, simple CDN with minimal configuration overhead.
- Companies locked into a single CDN provider due to long-term contracts or specific feature dependencies.
- Users requiring transparent per-GB pricing without custom quotes or negotiations.
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.
—
History & Notes
—
—