Static assets, delivered from the nearest edge.

Caching happens per object rather than per page. Each response is stored under a key derived from its path, its negotiated encoding and any headers the origin marks as varying, then held for the lifetime the origin declares. A revalidation request carries the stored validator upstream, so an unchanged object costs a small conditional exchange instead of a full transfer. Objects that are explicitly marked private or that carry authorisation state are never written to disk and pass straight through.

Origin failover is handled without operator involvement. Upstreams are grouped into an ordered pool, and a node that fails its health probe or returns repeated gateway errors is withdrawn until it recovers. While the whole pool is unreachable, stale but still usable copies keep being served with a warning attached, which is generally preferable to an error page. Purges propagate through the fabric, and a rebuilt node warms itself from neighbours before it starts taking live traffic.