We had the opportunity to meet IO River for the 1st time during the recent 68th edition of The IT Press Tour held last week in Boston, MA.

IO River, founded in 2022 by CEO Edward Tsinovoi and CTO Michael Hakimi, both veterans of Akamai’s core platform where they led edge compute development, is backed by S Capital (the former Sequoia Israel branch), Venture Guides, New Era and Pags Group, with a $20 million round closed in early 2026 bringing total funding to roughly $25 million. The company is supported by an industry advisory roster including Ronni Zehavi (Cotendo, HiBob), Aryeh Mergi (XtremIO, M-Systems), Ash Kulkarni (Elastic CEO, ex-Akamai GM), Marty Kagan (Cedexis, Hydrolix), Ofir Ehrlich (CloudEndure, Eon) and Pavel Gurvich (Guardicore). IO River’s thesis is that the CDN/edge-compute industry remains anchored in a 1990s mindset, a single global provider handling all traffic, which collapses under the volume and dynamism of the generative-AI era.

Click to enlarge

Every major edge provider experiences a global outage every 1–3 years and local incidents monthly, with the 99.9% SLA tolerating 6–10 hours of uncompensated downtime annually; recent examples cited include Cloudflare (4h in Feb 2026, 25h in Dec 2025, 6h in Nov 2025), AWS CloudFront (7h Feb 2026, 15h Oct 2025), Akamai (6h Feb 2025), Google Cloud (7h Jun 2024) and Microsoft Front Door (2h Jun 2023). A single 12-hour outage can inflict over $10 billion of customer damage, far exceeding a vendor’s lifetime revenue.

Click to enlarge

The platform is positioned as a “Virtual Edge”, not a new CDN, not a global load balancer, not a multi-CDN switcher, that decouples edge infrastructure from application services across a three-layer architecture. Layer 1 is AI-driven traffic steering over 15+ premium and regional edge providers (Akamai, Cloudflare, Fastly, AWS CloudFront, Google CDN, Azure CDN, etc.), optimizing for reliability, performance and cost via DNS/CNAME manipulation rather than inline traffic interception, meaning that if IO River itself fails, traffic continues to flow on its last-known routing. Layer 2 provides unified configuration, management and monitoring, abstracting vendor-specific intermediate languages such as Fastly VCL or Akamai EdgeWorkers. Layer 3 virtualizes application services on top of edge compute, WAF, bot management, API security and serverless edge code, through partnerships with Check Point, Google and others, rather than the legacy “build everything in-house, settle for good-enough” model of the incumbents. IO River claims it routinely detects and reroutes around Cloudflare or CloudFront outages before the providers themselves acknowledge them, and that splitting volume across vendors no longer destroys negotiated discounts.

Commercial traction stands at approximately 50 customers after one year of selling, with zero attrition. Initial verticals were OTT/media, publishers, gaming and edtech (e.g., Minute Media, Nexon, Plarium), expanding into e-commerce, travel/hospitality (Accor Hotels) and SaaS.

Pricing combines a tiered platform fee, optional traffic resold through IO River, and metered application-service usage (WAF, requests). Go-to-market is direct in the US, partner-led in Europe through system integrators (GNN in Germany, Equativ in France) and increasingly through the CDN vendors themselves, Fastly and others now pull IO River into deals because its multi-vendor visibility highlights each provider’s strengths. The team is roughly 50/50 split between R&D in Tel Aviv and US-based go-to-market, with several patents filed in the US. With cash runway of about two years and an AI-ready edge as the strategic horizon, IO River frames itself as the operating platform of the multi-cloud, multi-edge era, an “easy button” giving non-giant online businesses the resiliency, performance and vendor independence that only PayPal-scale incumbents could previously afford to engineer in-house.

Click to enlarge