Anycast delivery from the Joy edge, in front of any origin.
Point a CNAME at the Joy edge and your content is served from the nearest healthy PoP with sub-second failover, an origin shield that collapses thousands of misses into one request, preload before launches, and DDoS filtering in front of every resource.
The Joy CDN runs on the same anycast edge that fronts our own properties and the console. Requests land on the closest healthy point of presence; if a PoP fails, BGP withdraws it and traffic moves to the next one in under a second with no DNS change. Because the edge sits on AS152565, with 394 peers and direct paths to Indian eyeball networks, the last hop to your users is short and predictable rather than routed through a hub abroad.
Between the edge and your origin sits an origin shield — a single regional cache that turns a launch-day spike of edge misses into a handful of origin requests, which is what lets a small VPS survive a product launch. Content can be preloaded from a manifest or a bucket prefix so the first visitor already gets a cache hit, and purged per URL, prefix or tag the moment you deploy. HTTP/2 and HTTP/3, TLS 1.3, automatic certificates, Brotli and on-the-fly image optimisation are on by default.
The CDN is in beta: it is fully operational and pricing is final, but customer resources are provisioned through a ticket while the self-service console flow is finished. The CDN product page has the full feature list and set-up steps.
C1 · C2 · C3
The three things this product line is built around — the same three boxes you see on the tile.
Predictable latency, high throughput
Anycast routing sends every request to the nearest healthy PoP and the backbone carries the rest. Cache-key controls, cookie and header rules and per-hostname TTLs keep the hit ratio high; real-time analytics show requests, bandwidth, hit ratio and top paths per hostname.
Edge locations across regions
Distributed PoPs in Noida, Mumbai, Chennai, Singapore and the US West Coast, each with DDoS scrubbing and bot filtering in front of every resource. A PoP failure is withdrawn by BGP in under a second.
Anycast routing with an origin shield
One regional shield cache collapses edge misses into a single origin request; preload warms the cache before a launch; purge by URL, prefix or tag from the console or API the moment you deploy.
Specification
| Origins | Any HTTP/HTTPS host, a Joy VPS, or a Joy storage bucket |
|---|---|
| Edge | Anycast PoPs in India, Singapore and the US; sub-second failover; latency routing |
| Protocols | HTTP/2, HTTP/3 (QUIC), TLS 1.3, automatic certificates, Brotli and gzip |
| Caching | Per-hostname TTLs, cache-key rules (query strings, headers, cookies), origin shield, preload from a manifest or bucket prefix |
| Purge | By URL, prefix or tag — console or API, effective in seconds |
| Images | On-the-fly resize, WebP/AVIF conversion and quality control by query parameter |
| Security | DDoS and bot filtering on every resource; optional managed WAF ruleset per hostname |
| Analytics | Requests, bandwidth, hit ratio, status codes and top paths per hostname, in real time |
| Pricing | Egress $0.02 / GB (India, Singapore), $0.03 / GB (US); requests, hostnames and certificates free; image optimisation $1 per 10,000 transformations; managed WAF $10 / hostname / month |
Three steps
Tell us the hostname and origin
Open a ticket titled "CDN resource" with the hostname (for example static.example.com) and the origin URL. We create the resource and reply with a CNAME target.
Add the CNAME and set cache rules
Point the hostname at the edge. Defaults are sensible for static assets; adjust TTLs, which query strings matter and which cookies bypass the cache.
Preload, switch, purge on deploy
Optionally preload a list of URLs, then move your site to the new hostname. Purge from the console or API whenever you release.
Where CDN fits.
Questions about CDN.
Do I have to move my site to Joy?
What does it cost?
Can I bring my own certificate or sign URLs?
How do I purge after a deployment?
More answers in the full FAQ — billing, network, DDoS, backups, support and legal.
From $0.02 per GB, no minimums
Egress is the only metered item. Requests, hostnames and certificates are free; the first 100 GB a month is free during beta.
Works with
Build CDN into your stack.
Create an account and deploy in under ninety seconds, or talk to sales about a design for your workload — regions, sizes, timelines and a quote within one business day.