Static CDN accelerates files. DCDN accelerates your entire application — APIs, real-time data, POST requests, WebSocket connections, and all your static assets, simultaneously. One domain configuration handles all traffic types with intelligent routing and caching at the edge.
A standard CDN can only accelerate content that can be cached — files that don't change per user. The moment users log in, submit forms, open WebSocket connections, or call APIs, static CDN steps aside. Your application slows down exactly when engagement is highest.
DCDN extends static CDN with intelligent dynamic routing — keeping cacheable content at the edge while routing uncacheable requests through the fastest available network path to your origin.
DCDN operates transparently between your users and your origin — intercepting every request, making a routing decision in milliseconds, and delivering the optimal response.
DCDN supports every protocol that modern applications require — including protocols that didn't exist when most legacy CDN infrastructure was designed.
DCDN inherits all static CDN features — caching, SSL, access control, monitoring — and adds the dynamic routing and protocol capabilities that modern applications require.
For every dynamic request, DCDN selects the lowest-latency path from the edge node to your origin in real time — using live routing tables maintained across the entire edge network. Avoids congested internet paths and routes through private backbones where available.
Define which URLs, file types, or request patterns are cacheable vs dynamic. DCDN applies your rules automatically — no request-by-request configuration. Override with response headers, or manage TTL per path prefix, extension, or query string.
IP allowlists and blocklists, referer restriction, token authentication — all applied at the edge before requests reach your origin. HTTPS enforcement and custom SSL certificate management included for all acceleration domains.
Live dashboards for bandwidth, request count, cache hit rate, and HTTP status codes — separately for static and dynamic traffic. Request count monitoring distinguishes between static HTTPS, dynamic HTTP/HTTPS, and QUIC requests for accurate cost tracking.
Invalidate cached static content instantly across all edge nodes on deployment. Prefetch new static content to edges before users request it. For dynamic content, back-to-source configuration controls how and when DCDN fetches fresh content from your origin.
Per-edge access logs available for download — including request type, origin, protocol, latency, and status code. Statistical analysis dashboards aggregate across all DCDN domains. Integrate with your existing observability stack via log forwarding.
DCDN is for any application where users interact, not just browse — where a single session mixes static loads, API calls, real-time updates, and uploads.
DCDN billing has a unique dimension not in static CDN — request count. Because dynamic content cannot be cached, the system charges separately for the volume of requests routed through it. All three billing dimensions apply simultaneously.
The clearest way to understand DCDN's impact is to look at what changed — the specific metrics that improved when applications switched from static CDN or no CDN to whole site acceleration.
Static assets from edge cache. API calls via optimal route. WebSocket connections maintained at the edge. QUIC for mobile networks. All on one domain. Zero code changes.