Frequently Asked Questions
IO River is a Multi-Edge orchestration platform that unifies delivery, routing, and configuration across multiple CDNs through a single control layer.
Unlike a single CDN, IO River doesn’t sell capacity. It manages and optimizes your existing CDNs to improve performance, cost, and resilience.
A Virtual CDN is a unified delivery platform composed of multiple CDNs operating as one service, optimized automatically for cost, performance, and availability.
IO River connects to your CDNs via API, continuously monitors performance, and steers traffic in real time according to your defined business and technical rules.
24/7 email, Slack, and WhatsApp-based support covering first-level support. Phone support during local working hours (customer's local timelocal to the customer).
Yes, 24/7 email, Slack, and WhatsApp-based support covering first-level support.
IO River provides full certificate management, allowing you to create or import certificates that are automatically deployed and renewed across all CDNs. TLS termination occurs at each CDN provider, not through IO River, since traffic never passes through our platform.
IO River continuously monitors traffic through hundreds of global agents, Catchpoint nodes, and NS1 RUM data to track performance and availability. Our steering algorithms use these live inputs to optimize routing decisions in real time.
We keep a 24x7 NOC acting as the first responder to handle or escalate incidents reported by the field. We have a global, widely spread/deployed monitoring network of servers and clients/ agents combining static and client-based performance and availability monitoring that triggers automatic actions - that can turn/steer/move traffic from one Edge provider to another till the incident is handled/ solved and ok to restore and execute the original delivery policy.
The details are here. See documentation
Yes. IO River’s performance-penalty policy ensures traffic only flows through high-performing CDNs, validated during POC testing.
Of course. See our case studies.
IO River keeps retail sites available during traffic peaks like holidays, preventing slowdowns and revenue loss.
No, both follow the same compliance and data protection standards.
AdTech, OTT, Streaming, and Gaming all benefit from lower delivery costs, better QoE, and uninterrupted availability.
Yes, both are supported. See documentation.
No. IO River doesn’t sit in the delivery path, so even if IO River is offline, your CDNs continue operating normally.
IO River integrates with over 15 CDN providers globally.
Edge functions are deployed via IO River’s unified control plane for consistent behavior across CDNs.
Yes, by steering traffic to the best-performing CDN in each region in real time.
You can deploy code once and manage it across every CDN via IO River’s unified management layer powered by edge compute.
They extend CDN capabilities where vendors lack certain features through IO River’s API and edge compute.
By reducing buffering, improving playback stability, and optimizing delivery during live traffic spikes.
Through active-active infrastructure that continuously distributes and balances traffic.
IO River offer 3-options: 1) Creating a Certificate - IO River will create the certificate for you and will make sure to renew it automatically as needed. 2) Importing a Certificate - You can bring your own certificate, and IO River will make sure to deploy it on all of your CDN accounts. 3) Using external certificates - you can deploy the certificates to the CDNs by yourself, and IO River will use them in your services.
Full control. You define steering based on performance, cost, or availability, and decide which CDNs to include.
IO River provides full visibility across all CDNs (including errors, traffic, hits, and geo distribution), through two dashboards for performance and availability.
IO River instantly detects failures and automatically reroutes traffic to secondary CDNs without manual intervention.
Yes, you can set custom alerts and automate routing based on real-time performance or cost signals. Can I integrate IO River data with my existing observability stack (Datadog, Grafana, etc.) Yes, IO River data can be exported into those platforms.
No, IO River does not store CDN-processed data. We offer a log delivery service from the CDN connected to the user’s cloud storage account.
Yes, data is immediately presented once it is available by the CDN.
Routing decisions follow your configured priorities: performance, cost, availability, or specific CDN requests.
No, IO River works seamlessly with any cloud or origin setup — on-prem, multi-cloud, or hybrid.
Customers typically see up to 30% reduction in delivery costs. Read our case studies.
Yes, IO River automatically steers traffic to the most cost-efficient CDN per region and helps you balance commitments. Learn more on our product page.
No, IO River provides delivery-level independence. You can remove or add CDNs anytime without losing configuration or control.
IO River saves so much on delivery that edge compute costs become nearly irrelevant compared to overall optimization gains. Does IO River comply with major security standards Yes. IO River is certified for SOC 2, compliant with ISO 27001, GDPR, and HIPAA.
IO River offers a POC defined with your account executive, focusing on your KPIs such as availability, performance, and cost. Commercial terms are finalized upfront so there are no surprises.
It combines performance and commitment data to route traffic where pricing and performance align best, ensuring you fully utilize contracts while reducing spend.
Integration takes just a few clicks. Choose one CDN’s configuration and IO River replicates it across your entire CDN stack automatically.
Billing is managed monthly, with transparent reports on traffic, usage, and savings.
Yes, during POC, IO River runs in parallel with your existing setup so you can test performance and reliability without disrupting live traffic.
Yes, IO River’s architecture is built for active-active delivery to keep traffic flowing across all providers simultaneously.
Latency overhead is negligible; IO River’s control plane manages routing logic without sitting in the delivery path.
Yes, IO River supports integration with your current CDN providers without replacing them.
IO River manages its DNS records simultaneously in multiple DNS providers, making it resilient to the failure of a single DNS provider.
IO River uses a Multi-DNS solution to provide smart routing for our customers while ensuring a 99.999% uptime commitment. As part of the onboarding process to IO River, the customer will be asked to update the CNAME of their domain to IO River's provided CNAME.
No. Once our WAF (or any of our add-on services) is used, there is no need to consume your current provider's WAF.
The IO River WAF operates within your CDN provider's Edge Compute layer seamlessly and essentially acts as a substitute for it.
Furthermore, the IO River WAF can easily integrate with any of your CDN providers, enabling you to receive a WAF with consistent behavior across multiple vendors.
No. IO River allows optimization in cost, parallel to an improvement in the reliability and performance of the service.
IO River's WAF is the only WAF that can be deployed on multiple CDN providers and provide consistent behavior, without adding extra tier to your traffic.
IO River supports REST API, Python API, Go API and it allows you to manage the entire configuration through Terraform.
The enormous advantage of using IO River is the ability to manage everything from a single interface.
Through your IO River account, you can manage all your CDNs as if they were created as one. We ensure that your CDN behaves exactly as you have configured it
No. IO River is not in the processing path for DNS queries or HTTP requests.
Missing functionalities are completed using edge computing , in order to line up the functionalities to create the widest common capabilities.
By using your CDN API Token.
Simply update the CNAME of the domain with the provided CNAME from IO River.



