Anycast edge delivery with origin shield and instant purge.LIVE
Cache nodes in Noida, Mumbai, Singapore and the US West coast, on Joy address space, in front of any origin. Visitors are answered by the nearest edge; a single shield protects your origin from repeated misses; a purge clears every edge in seconds; the visitor's real IP reaches your logs.
What happens to one request.
- 01
A visitor asks for your page
The same address is announced from every Joy edge (anycast), so the request lands on the nearest one: Delhi in Noida, Jakarta in Singapore, California in US West.
- 02
Cache hit: answered at the edge
Static content already at that edge is served immediately. Nothing touches your origin.
- 03
Cache miss: one request through the shield
Misses from all edges collapse into a single upstream path, so your origin sees one request, not one per edge.
- 04
Your origin answers once
The response is stored at the shield and the edge, then served to everyone else from there.
- 05
Purge and observe
Purge a URL, a prefix or everything from the console or API; it is gone from every edge in seconds. Hits, misses and bandwidth per site are in the console.
The edge and the origin, one operator.
Anycast delivery
One address, every region. Static content is served from cache; dynamic requests pass through with the visitor IP intact.
Origin shield
A single upstream path, so a cache miss at many edges becomes one request to your origin.
Instant purge
Purge by URL, prefix or everything from the console or the API, with purge tokens for your deploy pipeline.
Certificates handled
TLS terminated at the edge with certificates issued and renewed for you; TLS 1.3 to visitors.
Websites and stores
Serve images, CSS and scripts from the edge; keep checkout dynamic with the real IP passed through.
Software and media
Large files served from the nearest edge; the origin is asked once per file.
Read-heavy APIs
Cache GET responses with short TTLs and purge on change from your deploy pipeline.
Does CDN traffic count against my server transfer?
CDN egress is metered separately per site at regional rates and shown before you enable it. Traffic between a Joy edge and a Joy origin stays on the Joy network.
Does the origin see the real visitor IP?
Yes. Edge nodes pass the visitor address through so your logs, rate limits and geolocation keep working.
Put the edge on the same network as the origin. Then stop worrying about either.