Cloud-native content delivery
on 2k8s.
Traditional CDN software runs as a monolithic stack on dedicated infrastructure, with its own deployment tooling, monitoring, and lifecycle management at every site. 2cdn takes a different approach — it is built natively on the 2k8s platform, running as containerized workloads orchestrated, observed, and managed through the same Kubernetes-based control plane that runs the rest of the distributed footprint. The result is a CDN that inherits the operational model of the platform underneath: centralized configuration, integrated observability, programmable routing, tenant isolation, and consistent software delivery across every node — without a separate management layer for content delivery.
Six capabilities. One delivery platform.
2k8s inside
2cdn runs as a set of containerized workloads on the 2k8s platform. Each CDN node — its caching engine, delivery services, and supporting functions — is packaged and deployed through the same Kubernetes API used for other distributed applications on the platform. New features and updates are packaged once and rolled out everywhere through standard 2k8s orchestration, with staged rollouts and per-node targeting where needed.
Kubernetes provides a uniform orchestration layer at each site, keeping caching and delivery services healthy and manageable across the footprint — restarting failed components, applying updates consistently, and maintaining the desired state over time. The container-based design also makes it straightforward to run 2cdn alongside other edge applications, sharing infrastructure efficiently while keeping the delivery software isolated and portable. 2cdn does not carry its own deployment tooling, configuration distribution, or lifecycle management — it relies on the platform for all of these.
A programmable edge, not just a cache
Content delivery increasingly requires more than caching and serving. Access policies must be enforced, streams must be adapted to device and network conditions, and security and compliance functions must execute in real time at the edge. 2cdn supports this through application enablement directly at the CDN edge — both in-process logic running alongside the delivery engine and Kubernetes-based microservices deployed as companion workloads through 2k8s.
Typical edge applications include token-based content security, dynamic video adaptation, on-the-fly packaging, server-side ad insertion, API protection, bot mitigation, and watermarking. Running these functions at the edge minimizes latency, reduces backhaul traffic, and enables providers to deliver customized services across a distributed footprint. By embedding these capabilities directly into the CDN fabric, 2cdn transforms the delivery layer from a static cache into a programmable delivery platform.
Managed from the cloud, deployed at the edge
All 2cdn management runs through the 2k8s cloud-based control plane. Configurations, delivery policies, and software updates are defined once and automatically synchronized across every CDN node in the footprint. There is no per-site management interface and no need to access individual nodes for routine operations.
Because management is centralized in the platform, the operational model stays consistent as the footprint grows. New nodes are onboarded through 2k8s and receive their full configuration automatically, whether the deployment spans a handful of locations or a globally distributed estate.
CDN observability through the platform
2cdn does not ship its own monitoring stack. Delivery metrics, cache performance data, and application logs flow through the 2k8s observability backend — the same managed, scalable infrastructure used for all platform workloads. CDN-specific telemetry is aggregated, normalized, and accessible through standard API endpoints, with the same tenant-scoped isolation and CRD-based alerting available to any 2k8s application.
This eliminates the need for a parallel CDN monitoring system and ensures that delivery observability stays synchronized with the broader platform view. Operators and tenants can see CDN performance alongside other workload metrics in one operational surface, rather than correlating across separate systems.
Fully programmable, automation-ready
2cdn is API-driven by design. Delivery configuration, deployment, monitoring, scaling, and application enablement are all accessible programmatically. This makes it straightforward to integrate CDN operations into existing CI/CD pipelines and infrastructure-as-code workflows, allowing tenants to manage their delivery configuration with the same tooling and practices they use for application deployment.
The API surface is the primary interface, designed for automation from the start rather than added onto a console-first management model.
Production-tested in multi-CDN delivery
2cdn operates as part of the multi-CDN architectures used by leading streaming providers today. Through open APIs and standardized interfaces, it integrates alongside other CDN providers within unified delivery overlays — supporting coordinated routing, configuration, logging, and content security across the delivery chain.
The platform also connects directly with origin infrastructure, ensuring efficient content flow from source to edge across globally distributed environments. 2cdn is designed to fit within existing delivery ecosystems and complement them, not to require a wholesale replacement of the current architecture.
Ready to see what 2you can do for your infrastructure?
Tell us what you’re working on. We’ll show you how the platform fits.