CDN
Push content to the Joy edge — anycast delivery, instant purge, origin shield and preload-ready cache in front of any origin.
How it works
Point a CNAME at the Joy edge, tell us your origin — any HTTP/HTTPS host, a Joy VPS or a Joy storage bucket — and we cache and serve your content from the nearest anycast edge node. Requests land on the closest healthy PoP; if a PoP fails, BGP withdraws it and traffic moves to the next one in under a second without DNS changes. Cache rules, TTLs, purge and real-time statistics are available in the console and through the API.
Between the edge and your origin sits an origin shield: a single regional cache that collapses thousands of edge misses into one origin request, which is what lets a small VPS survive a launch-day spike. Content can be preloaded before a launch so the first visitor already gets a cache hit.
Features
- Anycast edge with sub-second failover — nearest healthy PoP every time; latency routing and automatic failover.
- Preload-ready data supply for large launches: warm the cache from a manifest or a bucket prefix.
- HTTP/2 and HTTP/3 (QUIC), TLS 1.3, automatic certificates for your hostnames, Brotli and gzip.
- Image optimisation — on-the-fly resizing, WebP/AVIF conversion and quality control by query parameter.
- Per-resource purge and cache-key controls — purge by URL, prefix or tag; vary on headers or cookies you choose.
- DDoS and bot filtering in front of every resource, with optional managed WAF rules for HTTP origins.
- Real-time analytics — requests, bandwidth, hit ratio, status codes and top paths, per hostname.
Pricing
| Item | Price (USD) | Notes |
|---|---|---|
| Egress — India & Singapore edges | $0.02 / GB | first 100 GB per month free during beta |
| Egress — US edges | $0.03 / GB | |
| Requests | free | no per-request charge |
| Hostnames & certificates | free | unlimited hostnames per account |
| Image optimisation | $1 per 10,000 transformations | cached results are not re-billed |
| Managed WAF ruleset | $10 / hostname / month | optional |
Usage is metered daily and invoiced monthly in your currency; prepaid wallet balance can be used. There are no minimums and no commitment.
Set-up in four steps
- Open a ticket titled "CDN resource" with the hostname (e.g.
static.example.com) and the origin URL. - We create the resource and reply with a CNAME target such as
xyz.edge.joy.services. Add the CNAME at your DNS provider. - Set cache rules: default TTL, which query strings matter, which cookies bypass the cache. Defaults are sensible for static assets.
- Optionally preload a list of URLs, then switch your site to the new hostname. Purge from the console whenever you deploy.
Good fits
Game & app downloads
Multi-gigabyte patches served from the edge with preload before release day.
WordPress & e-commerce
Static assets and product images cached at the edge, HTML passed through with cookie-aware rules.
Video & media
HLS/DASH segments and thumbnails with high hit ratios and per-prefix purge.
APIs
Cache GET responses by header, shield the origin, and absorb bursts without scaling the backend.
Limits during beta
Custom TLS certificates (bring your own) and signed URLs are available on request; streaming (WebSocket) pass-through is supported but not cached. Log delivery to a bucket is on the roadmap. Open a ticket to join the programme.