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

IO River is a control layer for teams using multiple CDNs. It coordinates configuration and traffic steering while content delivery remains on the connected networks. The company was founded in 2022 and lists Boston as its current headquarters.

Choose between managing your own CDN accounts and buying bundled delivery. Those products have different commercial terms and operational responsibilities.

Network

Use the networks you connect

IO River does not publish its own cache-city inventory. Coverage comes from the connected CDNs, so their footprints should be evaluated separately. A headquarters or integration list is not a PoP map.

Traffic steering

DNS policies can split traffic by geography, performance, availability or cost commitments. Multi-DNS integrations include Route 53 and NS1. Test DNS behavior, failover and each connected CDN before relying on a policy for production traffic.

Features

FeatureSupported
Web application firewall✓ Supported
Bot protection◐ Partial
DDoS protection◐ Partial
Rate limiting✓ Supported
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 errors◐ Partial
Image optimizationNot listed
On-demand video◐ Partial
Live video◐ Partial
Digital rights managementNot listed
HLS / DASH packagingNot listed
WebSocketsNot listed
Signed URLs◐ Partial
Edge compute◐ Partial
Edge functions◐ Partial
Key-value storageNot listed
Configuration API✓ Supported
Real-time logs◐ Partial
Log export◐ Partial
Terraform provider✓ Supported

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

Shared delivery configuration

Manage origins, certificates, cache policies and purge operations centrally. Action support varies by CDN. Signed URLs and serving stale content on origin errors work on selected backends; origin Cache-Control handling must be configured explicitly.

Application security

Optional WAF services include managed OWASP rules. Cross-CDN rate limits help control application traffic. Bot challenge flows can require frontend code and tokens. For volumetric DDoS protection, check the connected CDNs and the protection included in their contracts.

Logs and visibility

Combine traffic, errors and offload metrics. Access logs can be sampled and sent to S3, compatible storage or Hydrolix on supported networks. Log delivery uses configured triggers and batches; allow for that delay in monitoring. CMCD playback analysis requires the video player to send the data.

Edge code and media

Unified request and response handlers target Cloudflare Workers, CloudFront Lambda@Edge and Fastly Compute, with runtime differences. Live and VOD templates configure media caching; they are not a video transcoder, packager or DRM service.

Pricing

Separate platform and delivery costs

The Multi-CDN product publishes prices by service count with a one-year commitment, but does not clearly label the billing period. Your own CDN agreements may add delivery, request, origin and security charges.

The bundled VCDN product publishes inconsistent per-TB figures between its cards and comparison table. Confirm the rate, volume threshold and included services before budgeting.

Use the calculator with a confirmed USD quote. Enter equivalent monthly platform fees only after confirming the billing period. For a bundle, avoid adding underlying CDN charges already included in the quote.

Developer tools

Use the REST API and Terraform provider to manage supported resources. Prometheus and OpenTelemetry integrations export metrics; access-log export has separate destinations and configuration.

Provider credentials and permissions are required for account orchestration. Bringing your own CloudFront account also requires Kinesis setup for its streaming-log integration. Test resource compatibility and deployment changes on every connected CDN.

When it fits

  • Teams already operating multiple CDNs and wanting shared configuration and traffic policy.
  • Streaming services that can enable player telemetry and evaluate quality across networks.
  • Buyers able to compare platform fees, direct CDN contracts and bundled delivery terms.

Before you choose

  • Confirm the product, commitment, request charges and billing period before using the price.
  • Check required cache, security and edge-code actions on each connected CDN.
  • DNS changes can take time to reach clients and do not move existing connections immediately.
Sources