Documentation

Configure delivery, caching, and observability for your edge zones.

Getting started

Point your DNS at the StratoEdge anycast network and add an origin. Requests are served from the nearest of 40+ points of presence, falling back to your origin on a cache miss.

Origins

Each zone forwards cache misses to your origin over TLS 1.3. Configure connect and read timeouts, health checks, and multi-origin failover from the console.

Cache control

By default the edge honors Cache-Control and ETag from your origin. Override TTLs per path with cache rules, or bypass caching for authenticated routes.

Purge API

Invalidate cached objects by path. Purges propagate to all PoPs within seconds.

curl -X POST https://cdn-us.voland-one.ru/api/v1/purge \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"paths": ["/assets/app.js", "/index.html"]}'

Real-time logs

Tail request logs live over a WebSocket stream. Each frame is a JSON log line with timestamp, status, cache result, client region, and serving PoP.

wss://cdn-us.voland-one.ru/api/v1/logs/stream

Keep the connection open to receive events as they are emitted at the edge.

API reference

GET  /api/v1/status   # node metrics        (requires auth)
GET  /api/v1/health   # liveness probe      (public)
GET  /api/v1/nodes    # PoP inventory       (requires auth)
POST /api/v1/purge    # invalidate objects  (requires auth)

Authenticated endpoints require a session cookie from the console or a bearer token.