CDN & Edge Configuration Manager

Part of the worlds-biggest-software-project initiative.

An AI-native, vendor-agnostic control plane for managing cache rules, edge policies, and multi-CDN traffic across providers like Cloudflare, Fastly, Akamai, Gcore, and BunnyCDN.

CDN & Edge Configuration Manager is an open-source platform for platform/SRE engineers, media and OTT teams, and e-commerce operators who need to author, validate, and orchestrate edge configurations across multiple CDN vendors. It addresses the core pain that today's configuration tooling is locked to single vendors, requires hand-written VCL or Workers code, and offers no unified abstraction for cache rules, security policies, or cost optimisation across providers.

Why CDN & Edge Configuration Manager?

Cloudflare, Fastly, and Akamai dashboards are vendor-centric and provide limited multi-CDN orchestration; switching or distributing traffic across providers is a manual exercise.
Akamai configuration propagation is slow and pricing is enterprise-only; Fastly's VCL has a steep learning curve for non-engineers.
Terraform and Pulumi offer declarative, GitOps-friendly infrastructure-as-code but are not CDN-specific and ship no performance analytics or cache-rule intelligence.
IO River pioneers vendor-agnostic multi-CDN orchestration but is a niche, closed, enterprise-contract product with limited public information and no edge compute capabilities of its own.
No mainstream platform auto-generates cache-control rules, detects misconfigured edge policies, or attributes cost across providers — manual rule engineering remains the norm.

Key Features

Multi-CDN Orchestration & Traffic Steering

Vendor-agnostic abstraction over major CDN providers (Cloudflare, Fastly, Akamai, AWS CloudFront, Gcore, BunnyCDN, Section.io)
Automatic failover and rule-based traffic steering across attached networks
Per-network performance visibility by geography, ISP, and content type
Real-time analytics aggregating telemetry from multiple CDN vendors

Cache & Edge Policy Management

TTL configuration with URL-level and surrogate-key cache purging
Cache-Control and Surrogate-Control header compliance (RFC 7234, RFC 5861)
Sub-second cache invalidation propagation as a target where the underlying provider supports it
Declarative ESI (Edge Side Includes) composition for fragment assembly

Security & Certificate Lifecycle

DDoS protection integration at L3/L4 and L7 (WAF) via underlying providers
Automated TLS certificate issuance and renewal via ACME (RFC 8555)
Detection of overly broad cache-bypass rules and missing security headers
Certificate near-expiry alerting

GitOps & Infrastructure-as-Code

Declarative, version-controlled edge configuration
Compatibility with Terraform and Pulumi workflows for CDN resource state
Plan-apply workflow with staged environments before production activation
Drift detection against deployed provider state

Observability & Cost

Real-time analytics on requests, latency, errors, and bandwidth
Streaming logs for export to SIEM and analytics platforms
Per-request cost attribution across multiple CDN providers
Predictive spend forecasting given planned traffic growth and content mix

AI-Native Advantage

AI is applied where incumbents rely on manual rule engineering. A cache-rule recommender analyses origin response headers, URL patterns, and cache-miss rates to auto-generate optimal cache-control rules across attached providers. Reinforcement-learning-driven traffic routing continuously selects the best-performing CDN per region, ISP, and content type from live latency and cost signals. An anomaly detector flags misconfigured policies, over-broad cache-bypass rules, missing security headers, and certificate near-expiry before they reach production. A natural-language interface translates plain-English rules into provider-specific VCL, Workers scripts, or Akamai rules.

Tech Stack & Deployment

The platform is designed around open standards: HTTP/3 / QUIC (RFC 9114, RFC 9000), Cache-Control / Surrogate-Control (RFC 7234, RFC 5861), W3C Edge Side Includes, ACME (RFC 8555), and the W3C Reporting API / Network Error Logging. Configuration integrates with the Terraform CDK and OpenTofu ecosystems for GitOps workflows. Provider integration is API-driven across 15+ CDN vendors, and edge logic runs through each provider's existing runtime (Workers, Compute@Edge, FastEdge, Edge Scripting) rather than introducing a new edge compute layer.

Market Context

The global CDN market is valued at approximately $27–33 billion in 2025, projected to reach $43–165 billion by 2030–2033 at CAGRs of 9–20% (Grand View Research, 2025). Pricing ranges from $0.005/GB at BunnyCDN to $0.02–0.08/GB at enterprise CDNs, with multi-CDN orchestration layers (e.g. IO River, $14M Series A in 2022) sold on enterprise contracts. Primary buyers are platform/SRE engineers, OTT and media streaming teams running five or more CDNs in parallel, e-commerce teams needing fine-grained cache invalidation, and security teams configuring WAF and DDoS rules at the edge.

Project Status

This project is in the research and specification phase.
Contributions, feedback, and domain expertise are welcome.

Contributing

We welcome contributions from developers, domain experts, and potential users. See CONTRIBUTING.md for guidelines.

Important: All contributions must be your own original work or clearly attributed open-source material with a compatible licence. Copyright infringement and licence violations will not be tolerated and will result in immediate removal of the offending contribution. If you are unsure whether a piece of code, text, or other material is safe to contribute, open an issue and ask before submitting.

Licence

Licence to be determined. See discussion for context.