Quickstart
Create a pull zone, point it at your origin, then send traffic to the hostname we give you. No agent, no sidecar, nothing to install at the origin.
# 1
$ arclight zones create --name assets --origin https://origin.example.com
✓ zone assets created
hostname: assets.sonata.lunarsymphony.store
# 2
CNAME cdn.example.com -> assets.sonata.lunarsymphony.store
# 3
$ curl -sI https://cdn.example.com/logo.svg | grep -i x-cache
x-cache: HIT, AMS
TLS is issued and renewed automatically once the CNAME resolves. HTTP/2 and HTTP/3 are on by default.
Cache rules
By default we honour your origin's Cache-Control. Override it per path when the origin can't be changed.
{
"rules": [
{ "match": "/static/*", "edge_ttl": "365d", "browser_ttl": "7d" },
{ "match": "/api/*", "edge_ttl": "0s", "bypass_cookie": "session" },
{ "match": "*.jpg", "edge_ttl": "30d", "optimize": "auto" }
]
}
Rules evaluate top to bottom; the first match wins. A rule with edge_ttl: 0s still terminates TLS and reuses the origin connection, so dynamic paths get the network without the caching.
Purging
Purges propagate to every PoP in under 150 ms. Purge by URL, by prefix, or by surrogate key.
$ curl -X POST https://api.sonata.lunarsymphony.store/v1/zones/assets/purge \
-H "Authorization: Bearer $TOKEN" \
-d '{"keys": ["product-4192"]}'
202 {"purged": 141, "took_ms": 118}
Tag responses at the origin with Surrogate-Key: product-4192 catalogue and you can invalidate a whole product page, everywhere, with one call.
CLI
The CLI is a single static binary. It reads the same API your dashboard does.
$ arclight zones list
NAME ORIGIN HIT RATIO EGRESS 30d
assets origin.example.com 96.4% 2.1 TB
video s3.eu-central.example.com 91.8% 18.7 TB
$ arclight tail --zone assets --status 5xx
Edge functions
Functions run on the same machine that serves the cache, so a rewrite or an auth check costs microseconds, not a round trip.
export default async function (request, ctx) {
const country = ctx.geo.country;
if (country === "JP")
return ctx.rewrite("/jp" + new URL(request.url).pathname);
return ctx.next();
}
Deploys are atomic across the network. A rollback is the previous version, promoted instantly.
Logs & metrics
Every request produces a structured log line at the edge. Stream them to your own sink, or query the last 30 days in the dashboard.
{"ts":"2026-05-14T08:21:07Z","pop":"FRA","status":200,"cache":"HIT",
"ttfb_ms":6,"bytes":48210,"host":"cdn.example.com","path":"/logo.svg"}
Need something that isn't here? Write to support — a human on the delivery team answers.