Each feature solves a concrete problem: faster delivery, simpler updates, or a safer origin. Below is what each one actually does and why it matters.
When a visitor requests a file, the request lands on the nearest edge server — a point of presence close to the user: Amsterdam for Europe, Tokyo for Japan, São Paulo for Brazil. The distance to the file shrinks from thousands of kilometers to hundreds. Latency drops from 150–300 ms to 10–40 ms.
Within a region, the cache has two tiers: frequently requested files sit in edge RAM and are served in milliseconds, the rest on NVMe storage nearby. On a cache miss, the edge fetches the file from your origin once and serves cached copies afterwards.
The classic CDN pain is updates: "we already fixed it, but users see the old version for two more days". In SRWX Edge, a purge reaches all 14 servers in under 5 seconds — by a single URL, by tag, or across the whole zone.
Tags (surrogate keys) label groups of files. Tag a release v2.4.0, and a single purge by that tag refreshes the entire group — no need to list files one by one.
# purge a single URL
curl -X POST https://api.cdn.srwx.app/v1/purge \
-H "Authorization: Bearer $SRWX_TOKEN" \
-d '{"url":"https://app.example.com/index.html"}'
# purge a whole release by tag
curl -X POST https://api.cdn.srwx.app/v1/purge \
-H "Authorization: Bearer $SRWX_TOKEN" \
-d '{"tags":["v2.4.0"]}'Files can be served from your own domain — say, static.example.com. It takes a single CNAME record (a DNS alias):
static.example.com. CNAME cdn.srwx.app.A Let’s Encrypt certificate is issued automatically within a couple of minutes and renews itself. Nothing to buy or renew manually; HSTS and OCSP stapling are on by default.
HTTP/3 runs over QUIC — a transport that doesn’t stall on packet loss. On mobile data, in an elevator or on a train, that’s the difference between a page that opens and an endless spinner.
Brotli compresses text files 15–20% tighter than gzip — CSS and JS arrive faster over the same link. Range requests make video seek instant: the edge serves just the needed fragment instead of the whole file.
Origin shield is an intermediate tier in front of your server. It collapses concurrent requests for the same file into a single origin fetch. Even if a thousand visitors hit the same file at once, your server sees exactly one request.
In practice this cuts origin load by up to 95%. It’s a single toggle in zone settings (Pro and Business plans).
Everything you can do by hand is scriptable: publishing, purging, domains and stats are all available through the CLI and HTTP API. The typical setup: GitHub Actions publishes the site on every release and triggers a purge by version tag.