IO River

Observed

www.ioriver.io · United States

IO River coordinates multiple delivery networks through unified configuration, monitoring and DNS traffic steering. Multi-CDN as a Service manages CDN accounts a team already owns, while Virtual CDN combines delivery capacity with the management layer. Its products serve video, publishing, ad tech, gaming and SaaS workloads, with separate purchasing scopes for orchestration, delivery and security.

Multi-CDN managementTraffic steeringVirtual CDNEdge securityEdge compute
Service marketsMultiple regions
BillingPlans / Custom quote
Free trialSupported
Payments
AWS Marketplace
Overall rating
★★★★★★★★★★3.5

On-site interest
3,150index
Observation score
39/ 100

See observation for methodology

Nov 22, 2026
01

Company introduction

About IO River
Founded
Founded in 2022; platform publicly launched in March 2024
Co-founders
Edward Tsinovoi and Michael Hakimi
Headquarters
Boston, Massachusetts, United States
Listing
Privately held; Series A announced in 2026

Built around the operational work of multi-CDN

Edward Tsinovoi and Michael Hakimi founded IO River in 2022 after working on CDN and edge infrastructure at Akamai. They focused on a practical problem: each additional delivery provider brings its own configuration model, console and feature set, making policy changes, routing and incident handling harder to coordinate. IO River puts a shared control layer above those networks so teams can operate them together.

Public launch and subsequent funding

IO River publicly launched its platform on March 13, 2024, announcing a $5.4 million seed round led by S Capital. On January 14, 2026, it announced a $20 million Series A led by Venture Guides and New Era, with S Capital and other investors participating. The funding supports expansion of its multi-edge platform and the separation of delivery infrastructure from security and compute services. The business is built around coordinating existing edge networks rather than requiring every workload to move to a new underlying CDN.

One control layer, several delivery networks

The platform brings configuration, traffic steering and observability into a shared management layer. Connecting existing CDN accounts suits teams that want to keep their current networks and commercial relationships; bundled services such as VCDN offer a different way to buy delivery. Security and edge features depend on the selected product, connected providers and service scope, while the networks actually used determine the relevant delivery footprint.

Company and operating locations

The current service agreement names IO River Ltd. as the service provider, with the subscription scope defined in an order. The company lists Boston as its headquarters and maintains offices in Tel Aviv and Luton in the United Kingdom. Buyers planning regional delivery, failover or shared policy management should evaluate both the control platform and its underlying networks, including responsibility for traffic charges, configuration changes, support escalation and incidents.

One configuration and steering layer across CDNs

IO River uses each CDN’s API to deploy configuration and a DNS CNAME to select a delivery network by location, performance, weight or cost. The selected CDN handles HTTP/HTTPS content directly. A console, REST API and Terraform manage domains, origins, caching rules and certificates. Bringing existing CDN accounts requires appropriate API permissions and retains the contracts and usage charges for those networks.

Setup involves defining a service, domains and origins; uploading a certificate or obtaining a managed certificate through DNS validation; selecting CDNs, monitors and routing policies; and changing the CNAME. Redundancy requires two or more available networks, while VCDN includes multiple providers. Coverage and features depend on the chosen networks, account permissions and locations. Monitoring intervals and DNS caching also affect when routing changes take effect.

02

Who is this provider for?

Engineering teams operating several CDNs

Manage domains, caching and origin settings across several CDNs through one control layer, with traffic policies for performance, availability or cost.

Confirm CDN accounts, agreements and API permissions, then validate how each policy behaves on the selected networks.

Online services planning traffic steering and failover

Publishers, video services and online applications can combine delivery networks and use monitoring to adjust where traffic goes.

Test monitoring, DNS caching and failover with traffic from actual user regions. Check certificates, sessions, origin access and security-policy consistency.

Enterprises consolidating delivery operations and costs

Review network performance, traffic and logs centrally while bringing provider configuration and traffic allocation into a common workflow.

Define control-layer and CDN charges, traffic commitments, monitoring and security modules, rollback procedures and support responsibilities.

Pilot representative domains across the selected CDNs. Validate cache behavior, dynamic requests, certificates and origin access in user regions, then test network failures and control-layer unavailability. Define monitoring criteria, DNS changes, configuration consistency, traffic commitments and escalation paths in the deployment and purchasing plan.

03

Services and products

Core products from official sources

Explore products by use case: what they do, how to use them and whether they are billed separately.

Multi-CDN as a Service (MCaaS)

Delivery orchestration

Connect existing CDN accounts to manage caching, domains, origins, certificates and behavior rules together, with delivery metrics by provider and region. It suits operations teams that already contract with several CDNs and want to reduce repeated configuration and provider-switching work.

Orchestration is a separate charge. Delivery traffic, requests and other CDN usage remain subject to each network’s contract. Request a proposal or use the AWS Marketplace subscription tiered by managed traffic.Official product information

Virtual CDN (VCDN)

Combined network delivery

Buy and manage delivery across multiple upstream CDNs through one entry point, with shared configuration, monitoring and automatic steering. It targets video, gaming and global applications. Edge locations belong to the participating networks; the deployment proposal defines eligible providers, regions and features.

Delivery capacity and orchestration are purchased together under a quote for the required scale and features. Confirm metering, eligible regions, optional services and the SLA before purchase.Official product information

Traffic Steering and failover

DNS traffic management

Set static regional weights, select networks using performance monitors or balance cost priorities against CDN traffic commitments. Automatic failover needs an availability monitor; dynamic performance routing also needs a performance monitor. DNS caches can delay new routing decisions, and a policy change does not migrate established connections.

Included according to the orchestration or delivery plan. Allow for upstream commitments, overages and the agreed monitoring scope when budgeting.Official product information

Unified WAF, rate limiting and bot management

Edge security

Deploy consistent security policies on participating CDNs’ edge compute layers. Options include IO River rulesets, Check Point machine-learning and rule-based engines, custom access rules, rate limiting and bot controls. Account-level security access is required before enabling it on a service. Tune learning and prevention modes to the application’s traffic.

Security modules and upstream edge compute may add charges. Base delivery rates should not be treated as the total cost of a full security configuration.Official product information

Unified Edge Compute

Programmable edge

Write request and response logic against a common API and deploy it to supported platforms such as Cloudflare, CloudFront and Fastly. Adjust headers, routing, authentication, caching and content transformation across a whole service or selected routes. Validate runtime limits and consistent behavior on each target platform before release.

Feature access and upstream function execution charges depend on the selected plan and CDN accounts.Official product information
Sources: IO River official product pages and developer documentationVerified: 2026-11-16
04

Plans and pricing

Official public pricing
Website delivery and security plans · monthly and annual billing shown separatelyUSD

AWS Marketplace Free

Teams starting with a smaller multi-CDN configuration

US$0

1- or 12-month contract

  • Managed delivery tier up to 30TB.
  • Free orchestration entitlement; upstream CDN delivery, requests and other cloud resources are billed separately.
  • Confirm the usage window, treatment of excess volume and included features before activation.

AWS Marketplace 250TB

Teams requiring the managed delivery tier up to 250TB

US$250

1-month contract

  • One-month contract: US$250. Total for a 12-month contract: US$2,250.
  • Managed delivery tier up to 250TB; upstream CDN charges are separate.
  • Confirm the annual entitlement window and excess-volume rules in the subscription terms.

AWS Marketplace 750TB

Teams requiring the managed delivery tier up to 750TB

US$600

1-month contract

  • One-month contract: US$600. Total for a 12-month contract: US$6,600.
  • Managed delivery tier up to 750TB; upstream CDN charges are separate.
  • Confirm the annual entitlement window and excess-volume rules in the subscription terms.

AWS Marketplace 2PB

Teams requiring the managed delivery tier up to 2PB

US$1,000

1-month contract

  • One-month contract: US$1,000. Total for a 12-month contract: US$11,000.
  • Managed delivery tier up to 2PB; upstream CDN charges are separate.
  • Confirm the annual entitlement window and excess-volume rules in the subscription terms.

AWS Marketplace 5PB

Teams requiring the managed delivery tier up to 5PB

US$1,500

1-month contract

  • One-month contract: US$1,500. Total for a 12-month contract: US$16,500.
  • Managed delivery tier up to 5PB; upstream CDN charges are separate.
  • Confirm higher-volume requirements, security and edge-compute resources separately.

Multi-CDN as a Service — direct

Enterprises with existing CDN accounts and contracts

Quote

Contract subscription

  • Manage the configuration, routing and observability of your existing CDNs together.
  • Agree the service scale, term and features in the quote; existing CDN contracts remain separate.

VCDN aggregate delivery

Teams seeking a single service across multiple delivery networks

Quote

Usage / Contract

  • Multiple CDNs operate as one delivery service with automatic traffic steering.
  • Confirm whether delivery pricing includes platform management, plus regions, volume tiers, requests and add-ons.

vEdge secure delivery

Enterprises combining multi-CDN delivery with application protection

Quote

Bundled subscription

  • Combines aggregate delivery with Check Point WAF and related security capabilities.
  • Specify the enabled protections, service scope, upstream resource charges and guarantees in the quote.

How are separate products billed?

ProductAllowance / base feeUsage prices
Managed delivery volumeAWS Marketplace offers 30TB, 250TB, 750TB, 2PB and 5PB tiers, priced separately for one-month and 12-month contracts.See plans
Bring-your-own CDN deliveryTraffic, requests, commitments and excess usage on existing CDNs remain payable under each provider contract.Upstream contract
VCDN aggregate deliveryQuote by delivery scale and purchased scope;agree regions, measurement units and excess-volume pricing.Custom quote
Security and edge computeConfirm which security features, edge-execution resources and upstream services are included in the selected offer.By plan
Additional features and professional servicesMidterm feature or volume additions require an order amendment and are prorated for the remaining term.Additional consulting, training and implementation beyond included support require a separate statement of work.Order / SOW

Budget for IO River orchestration separately from CDN delivery. The Virtual Edge–Orchestration listing on AWS Marketplace offers US-dollar tiers based on managed delivery volume, with one-month and 12-month contracts. These are orchestration entitlements; upstream CDN traffic, requests and other resources remain subject to the relevant provider contracts. VCDN and vEdge aggregate delivery offers require a separate quote covering metering, regions, security and add-ons. The direct MSA defaults to USD, excludes taxes and calls for advance invoicing with payment within 30 days of receipt. Public Marketplace contracts are billed upfront when subscribed.

05

CdnChart Selection Guide

GoodSelection verdict

IO River suits teams that need multiple CDNs and want centralized configuration and traffic policies

Its control layer connects delivery networks so teams can manage trade-offs among performance, availability and cost.

Use casesProductsPricing and termsDocumentationSupport resources

Why we recommend it

  • Centralized configuration reduces the work of maintaining domains, cache settings and origin rules in separate CDN consoles.
  • Performance, availability and cost policies can work with monitoring to support traffic steering and failover.
  • APIs, Terraform and centralized logs help incorporate delivery changes into existing development and operations workflows.

Considerations

Confirm eligibility and charges for the selected CDNs, monitoring and security capabilities. Test DNS caching, failover timing, certificate and security-policy consistency with real traffic, including operation and recovery when the control layer is unavailable. Define IO River and CDN agreements, traffic commitments and support boundaries separately.